Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CivBase

Members
  • Joined

  • Last visited

Everything posted by CivBase

  1. Label: none uuid: 3fa64220-8898-416c-aefd-dce48cf77463 Total devices 1 FS bytes used 3.20TiB devid 1 size 3.64TiB used 3.20TiB path /dev/md1p1 Label: none uuid: 6da1f5e7-6324-4e3c-8daf-6c2cc7ebec52 Total devices 1 FS bytes used 2.84TiB devid 1 size 3.64TiB used 2.87TiB path /dev/md2p1 Label: none uuid: b3bdaa5e-3196-40da-a3b0-4c05f70f9c64 Total devices 1 FS bytes used 100.24MiB devid 1 size 3.64TiB used 3.07GiB path /dev/md4p1 Label: none uuid: 5d82a858-c631-49c0-b038-75c5784f1c09 Total devices 1 FS bytes used 21.00GiB devid 1 size 238.47GiB used 24.06GiB path /dev/sdd1 I do not see disk3 in the output.
  2. Actually, yes. Disk3 and disk4 were previously part of my home server as part of a RAID0 array. I think disk3 was the original disk and I added disk4 to the array later. I was getting close to capacity and decided adding more drives to a RAID0 array was probably foolish, so I picked up 3 more drives for a NAS and migrated the data onto there. After that, I didn't need those disks in their original home so I pulled them from my server and added them to the NAS array. lsblk shows all the devices I'd expect, except for sdb. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 63.4M 1 loop /lib loop1 7:1 0 339M 1 loop /usr sda 8:0 1 29.5G 0 disk └─sda1 8:1 1 29.5G 0 part /boot sdb 8:16 0 3.6T 0 disk sdc 8:32 0 3.6T 0 disk sdd 8:48 0 238.5G 0 disk └─sdd1 8:49 0 238.5G 0 part /mnt/cache sde 8:64 0 3.6T 0 disk └─sde1 8:65 0 3.6T 0 part sdf 8:80 0 3.6T 0 disk └─sdf1 8:81 0 3.6T 0 part sdg 8:96 0 3.6T 0 disk └─sdg1 8:97 0 3.6T 0 part md1p1 9:1 0 3.6T 0 md /mnt/disk1 md2p1 9:2 0 3.6T 0 md /mnt/disk2 md3p1 9:3 0 3.6T 0 md md4p1 9:4 0 3.6T 0 md /mnt/disk4
  3. Here you go. natasha-diagnostics-20240229-1949.zip
  4. I have an array of 5 disks, all 4 TB HDDs. One is Parity, the other 4 are for storage. But one of those 4 (dev/sdb) is reporting as "Umountable: Unsupported or no file system" even after triggering a format. All 4 storage disks are configured to use btrfs with compression enabled. The other 3 are working fine. Is this a configuration issue on my end or a bug? I get this in the log: Feb 29 19:20:59 NAtaSha emhttpd: /mnt/disk3: no btrfs or device /dev/md3p1 is not single Feb 29 19:20:59 NAtaSha emhttpd: /mnt/disk3 mount error: Unsupported or no file system Here's the rest of the log: Feb 29 19:20:55 NAtaSha kernel: mdcmd (38): nocheck pause Feb 29 19:20:57 NAtaSha emhttpd: creating volume: disk3 (btrfs) Feb 29 19:20:57 NAtaSha emhttpd: shcmd (3926): /sbin/wipefs -af /dev/md3p1 Feb 29 19:20:57 NAtaSha emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Feb 29 19:20:57 NAtaSha emhttpd: shcmd (3927): sgdisk -Z /dev/sdb Feb 29 19:20:58 NAtaSha root: Creating new GPT entries in memory. Feb 29 19:20:58 NAtaSha root: GPT data structures destroyed! You may now partition the disk using fdisk or Feb 29 19:20:58 NAtaSha root: other utilities. Feb 29 19:20:58 NAtaSha emhttpd: shcmd (3928): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Feb 29 19:20:59 NAtaSha root: Creating new GPT entries in memory. Feb 29 19:20:59 NAtaSha root: The operation has completed successfully. Feb 29 19:20:59 NAtaSha emhttpd: re-reading (sdb) partition table Feb 29 19:20:59 NAtaSha emhttpd: shcmd (3929): udevadm settle Feb 29 19:20:59 NAtaSha emhttpd: mounting /mnt/disk3 Feb 29 19:20:59 NAtaSha emhttpd: shcmd (3930): mkdir -p /mnt/disk3 Feb 29 19:20:59 NAtaSha emhttpd: /mnt/disk3: no btrfs or device /dev/md3p1 is not single Feb 29 19:20:59 NAtaSha emhttpd: /mnt/disk3 mount error: Unsupported or no file system Feb 29 19:20:59 NAtaSha emhttpd: shcmd (3931): rmdir /mnt/disk3 Feb 29 19:21:00 NAtaSha emhttpd: Starting services... Feb 29 19:21:00 NAtaSha emhttpd: shcmd (3933): /etc/rc.d/rc.samba restart Feb 29 19:21:00 NAtaSha wsdd2[5731]: 'Terminated' signal received. Feb 29 19:21:00 NAtaSha winbindd[5736]: [2024/02/29 19:21:00.123325, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) Feb 29 19:21:00 NAtaSha winbindd[5736]: Got sig[15] terminate (is_parent=0) Feb 29 19:21:00 NAtaSha winbindd[5734]: [2024/02/29 19:21:00.123375, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) Feb 29 19:21:00 NAtaSha winbindd[5734]: Got sig[15] terminate (is_parent=1) Feb 29 19:21:00 NAtaSha wsdd2[5731]: terminating. Feb 29 19:21:02 NAtaSha root: Starting Samba: /usr/sbin/smbd -D Feb 29 19:21:02 NAtaSha smbd[6821]: [2024/02/29 19:21:02.341182, 0] ../../source3/smbd/server.c:1741(main) Feb 29 19:21:02 NAtaSha smbd[6821]: smbd version 4.17.12 started. Feb 29 19:21:02 NAtaSha smbd[6821]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 29 19:21:02 NAtaSha root: /usr/sbin/wsdd2 -d -4 Feb 29 19:21:02 NAtaSha wsdd2[6835]: starting. Feb 29 19:21:02 NAtaSha root: /usr/sbin/winbindd -D Feb 29 19:21:02 NAtaSha winbindd[6836]: [2024/02/29 19:21:02.495402, 0] ../../source3/winbindd/winbindd.c:1440(main) Feb 29 19:21:02 NAtaSha winbindd[6836]: winbindd version 4.17.12 started. Feb 29 19:21:02 NAtaSha winbindd[6836]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 29 19:21:02 NAtaSha winbindd[6838]: [2024/02/29 19:21:02.502525, 0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache) Feb 29 19:21:02 NAtaSha winbindd[6838]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Feb 29 19:21:02 NAtaSha emhttpd: shcmd (3937): /etc/rc.d/rc.avahidaemon restart Feb 29 19:21:02 NAtaSha root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Feb 29 19:21:02 NAtaSha avahi-daemon[5775]: Got SIGTERM, quitting. Feb 29 19:21:02 NAtaSha avahi-dnsconfd[5784]: read(): EOF Feb 29 19:21:02 NAtaSha avahi-daemon[5775]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.26. Feb 29 19:21:02 NAtaSha avahi-daemon[5775]: avahi-daemon 0.8 exiting. Feb 29 19:21:02 NAtaSha root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Successfully dropped root privileges. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: avahi-daemon 0.8 starting up. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Successfully called chroot(). Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Successfully dropped remaining capabilities. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Loading service file /services/sftp-ssh.service. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Loading service file /services/smb.service. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Loading service file /services/ssh.service. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.26. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: New relevant interface br0.IPv4 for mDNS. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Network interface enumeration completed. Feb 29 19:21:02 NAtaSha avahi-daemon[6881]: Registering new address record for 192.168.1.26 on br0.IPv4. Feb 29 19:21:02 NAtaSha emhttpd: shcmd (3938): /etc/rc.d/rc.avahidnsconfd restart Feb 29 19:21:02 NAtaSha root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Feb 29 19:21:02 NAtaSha root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Feb 29 19:21:02 NAtaSha avahi-dnsconfd[6890]: Successfully connected to Avahi daemon. Feb 29 19:21:02 NAtaSha kernel: mdcmd (39): check resume Feb 29 19:21:03 NAtaSha avahi-daemon[6881]: Server startup complete. Host name is NAtaSha.local. Local service cookie is 1646419024. Feb 29 19:21:04 NAtaSha avahi-daemon[6881]: Service "NAtaSha" (/services/ssh.service) successfully established. Feb 29 19:21:04 NAtaSha avahi-daemon[6881]: Service "NAtaSha" (/services/smb.service) successfully established. Feb 29 19:21:04 NAtaSha avahi-daemon[6881]: Service "NAtaSha" (/services/sftp-ssh.service) successfully established.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.