CivBase Posted March 1 Share Posted March 1 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. Quote Link to comment
trurl Posted March 1 Share Posted March 1 Attach Diagnostics to your NEXT post in this thread. Quote Link to comment
CivBase Posted March 1 Author Share Posted March 1 Here you go. natasha-diagnostics-20240229-1949.zip Quote Link to comment
trurl Posted March 1 Share Posted March 1 Was disk3 previously used? What do you get from command line with this? lsblk Quote Link to comment
CivBase Posted March 1 Author Share Posted March 1 (edited) 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 Edited March 1 by CivBase clarification Quote Link to comment
CivBase Posted March 3 Author Share Posted March 3 On 3/1/2024 at 3:12 AM, JorgeB said: Post the output of btrfs fi show 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. Quote Link to comment
JorgeB Posted March 3 Share Posted March 3 Reboot, try to format disk3 again and post new diags if t still fails. Quote Link to comment
CivBase Posted March 6 Author Share Posted March 6 (edited) disk2 is now listed as "unmountable" upon reboot. Consequently, many files are now missing from the shares which use that array. I tried a full shutdown after that, but disk2 is still listed as "umountable" after starting it back up. 😬 I have not initiated a format since disk2 is now impacted and that disk has data on it. disk2 was one of the new disks I purchased for the NAS. It was never used prior to installation. New diagnostics are attached. This appears in the system logs: Mar 6 16:55:44 NAtaSha emhttpd: mounting /mnt/disk2 Mar 6 16:55:44 NAtaSha emhttpd: shcmd (38): mkdir -p /mnt/disk2 Mar 6 16:55:44 NAtaSha emhttpd: /mnt/disk2 mount error: Unsupported partition layout Mar 6 16:55:44 NAtaSha emhttpd: shcmd (39): rmdir /mnt/disk2 disk2 is now missing from lsblk. 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 238.5G 0 disk └─sdb1 8:17 0 238.5G 0 part /mnt/cache sdc 8:32 0 3.6T 0 disk └─sdc1 8:33 0 3.6T 0 part sdd 8:48 0 3.6T 0 disk sde 8:64 0 3.6T 0 disk └─sde1 8:65 0 3.6T 0 part sdf 8:80 0 3.6T 0 disk sdg 8:96 0 3.6T 0 disk md1p1 9:1 0 3.6T 0 md /mnt/disk1 md2p1 9:2 0 3.6T 0 md md3p1 9:3 0 3.6T 0 md md4p1 9:4 0 3.6T 0 md /mnt/disk4 But /dev/md2p1 still shows up in btrfs fi show. That's the device that was being used by the /mnt/disk2 mount. 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: b3bdaa5e-3196-40da-a3b0-4c05f70f9c64 Total devices 1 FS bytes used 174.07MiB 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/sdb1 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 natasha-diagnostics-20240306-1657.zip Edited March 6 by CivBase Clarification for where disk2 came from Quote Link to comment
JorgeB Posted March 7 Share Posted March 7 Invalid partition layout usually means the disk's MBR changed, but before anything else, I just noticed that the SATA controller is using IDE for two ports, this is a known issue with those chipsets and likely the reason for the problems formatting disk3, it won't fix the disk2 issue, but go into that board BIOS and change those ports to SATA/AHCI, then post new diags after array start. Quote Link to comment
CivBase Posted March 8 Author Share Posted March 8 (edited) You were spot on with the IDE thing. I've updated the BIOS (see attached pics for confirmation) and attached new diagnostics. Still getting "umountable" for both disk2 and disk3. Is it possible/advisable for me to just rebuild disk2 at this point? Will disk3's issue be a problem for a rebuild of disk2? natasha-diagnostics-20240308-1156.zip Edited March 8 by CivBase Quote Link to comment
JorgeB Posted March 8 Share Posted March 8 I would first see if the disks mount with UD, stop the array, unassign one or both and see if they mount read-only with UD. Quote Link to comment
CivBase Posted March 8 Author Share Posted March 8 Does "UD" refer to the "Unassigned Devices" plugin? Quote Link to comment
trurl Posted March 8 Share Posted March 8 1 hour ago, CivBase said: Does "UD" refer to the "Unassigned Devices" plugin? yes Quote Link to comment
CivBase Posted March 8 Author Share Posted March 8 I've installed the Unassigned Devices plugin, but I'm having trouble with the instructions. If I set disk3 to "no device" in the array, it shows up in the "Unassigned Disks" section. But from there I'm not sure how to "see if the disks mount with UD". The only option presented by the UI is "format". Is this necessary to mount it with UD? Will formatting disk3 at this point impact my ability to re-build disk2 if that ends up being necessary? No data has been stored on disk3, but it was part of the array (as "unmountable") during the last parity check and I did not zero it out before adding it to the array. Quote Link to comment
trurl Posted March 9 Share Posted March 9 59 minutes ago, CivBase said: "see if the disks mount with UD". The only option presented by the UI is "format" This means the disk won't mount with UD, so that is the answer to that question. DO NOT FORMAT. Quote Link to comment
CivBase Posted March 9 Author Share Posted March 9 In that case, its the same for disk2 as well. Seems I am not able to mount either with UD. I did not format either disk. Quote Link to comment
JorgeB Posted March 9 Share Posted March 9 That suggests the partitions are damaged, possibly even missing, if parity was valid Unraid should be able to recreate them correctly, unassign on of the unmountable data disks, start the array, see if the emulated disk mounts, if yes and contents look correct, re-assign the disk to rebuild on top, when done repeat for the other one. Quote Link to comment
CivBase Posted March 9 Author Share Posted March 9 I unassigned disk2 and started the array. When I hover over the device status icon, the popup says "device is missing (disabled), contents emulated". Is that all I need to confirm the emulated disk mounts? Quote Link to comment
trurl Posted March 9 Share Posted March 9 As you can see from your screenshot, emulated disk2 is still unmountable. Quote Link to comment
CivBase Posted March 9 Author Share Posted March 9 So it's emulating an unmountable disk? That's odd. The last parity check was March 5th and it still shows as valid, but disk2 didn't start showing as unmountable until after I rebooted on March 6th. I get this in the logs now. Mar 9 09:50:22 NAtaSha emhttpd: mounting /mnt/disk2 Mar 9 09:50:22 NAtaSha emhttpd: shcmd (73215): mkdir -p /mnt/disk2 Mar 9 09:50:22 NAtaSha emhttpd: /mnt/disk2: no btrfs or device /dev/md2p1 is not single Mar 9 09:50:22 NAtaSha emhttpd: /mnt/disk2 mount error: Unsupported or no file system Mar 9 09:50:22 NAtaSha emhttpd: shcmd (73216): rmdir /mnt/disk2 Quote Link to comment
JorgeB Posted March 10 Share Posted March 10 With the array started post new diags and the output of: blkid and fdisk -l /dev/sdf Quote Link to comment
CivBase Posted March 10 Author Share Posted March 10 (edited) Started the array with disk2 still unassigned, contents emulated. disk2 shows "Unmountable: Unsupported or no file system". disk3 is still assigned and shows "Unmountable: Unsupported partition layout". root@NAtaSha:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="5B78-7F6A" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdb1: UUID="5d82a858-c631-49c0-b038-75c5784f1c09" UUID_SUB="07d9f78c-d288-4641-a480-5533e5f8fac5" BLOCK_SIZE="4096" TYPE="btrfs" /dev/loop0: TYPE="squashfs" /dev/sde1: UUID="b3bdaa5e-3196-40da-a3b0-4c05f70f9c64" UUID_SUB="8bae425a-2517-4164-9e01-2dee44d51215" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="d16f52fe-52bb-4ecd-ab36-0ab8dffced60" /dev/sdc1: UUID="3fa64220-8898-416c-aefd-dce48cf77463" UUID_SUB="7d5cf850-2512-4d45-b3a8-5cd16e0a4310" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="70ef2bed-0fd0-4891-806b-e07dde350a5d" /dev/md1p1: UUID="3fa64220-8898-416c-aefd-dce48cf77463" UUID_SUB="7d5cf850-2512-4d45-b3a8-5cd16e0a4310" BLOCK_SIZE="4096" TYPE="btrfs" /dev/md4p1: UUID="b3bdaa5e-3196-40da-a3b0-4c05f70f9c64" UUID_SUB="8bae425a-2517-4164-9e01-2dee44d51215" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdd: PTUUID="65a6b1a2-b94d-4eb8-8c2b-942a5de3ab7d" PTTYPE="gpt" root@NAtaSha:~# fdisk -l /dev/sdf Disk /dev/sdf: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4002FYYZ-0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes natasha-diagnostics-20240310-1043.zip Edited March 10 by CivBase added additional info about the state of the array Quote Link to comment
JorgeB Posted March 11 Share Posted March 11 No valid filesystem is being detected, which suggests parity isn't valid. Also, and as suspected the actual disks don't even have a partition, at list disk4, assume disk3 is the same. Type sfdisk /dev/sdf then type 64 and hit enter, then hit CTRL+C to abort and post the output/screenshot of the result. Quote Link to comment
CivBase Posted March 12 Author Share Posted March 12 (edited) If the file system ends up not being recoverable, do you have any recommendations for software to recover data from btrfs? root@NAtaSha:~# sfdisk /dev/sdf Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdf: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4002FYYZ-0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 The size of this disk is 3.6 TiB (4000787030016 bytes). DOS partition table format cannot be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT). Created a new DOS disklabel with disk identifier 0x4a979c96. Created a new partition 1 of type 'Linux' and of size 2 TiB. /dev/sdf1 : 64 4294967295 (2T) Linux /dev/sdf2: ^C Edited March 12 by CivBase Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.