May 10, 20251 yr I messed up. I updated from 7.0.1 to 7.1.1, my 4x drives (1 parity, 3 data) connected to an HBA (H310) showed "device is disabled, contents emulated" for 2 of my data drives. I don't know what I was thinking, I ended up doing a "New Config" for the Array Slots. Now, 2 of the data drives show "Unmountable: unsupported or no file system", and I'll have to format them to mount it. All I care about now is to salvage the data on all my drives, if possible. There's nothing too important, but I might have some photos on there that I have not created an offline backup of. unraid-tower-diagnostics-20250509-1700.zip
May 10, 20251 yr Community Expert 3 hours ago, Nads said: and I'll have to format them to mount it Whatever you do, do NOT format unless you want to loose the data on those drives. Doing a New Config was not the correct way to proceed but things should sntill be recoverable. i have not yet reviewed the diagnostics to give informed advice on the best next steps.
May 10, 20251 yr Community Expert Post the output from: lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL
May 10, 20251 yr Author 14 hours ago, JorgeB said: Post the output from: lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL root@Unraid-Tower:~# lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL TYPE PARTN NAME START SIZE PTTYPE PARTTYPE FSTYPE LABEL SERIAL loop loop0 579.6M squashfs loop loop1 169.8M squashfs loop loop2 20G btrfs loop loop3 1G btrfs disk sda 14.4G dos F46D0461E280F1A0A94D0187 part 1 sda1 2048 14.4G dos 0xc vfat UNRAID disk sdb 3.6T gpt WD-WCC7K5TY8K0Y part 1 sdb1 64 3.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs disk sdc 10.9T gpt ZRT1HFF4 part 1 sdc1 2048 10.9T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 disk sdd 14.6T gpt ZR59J2JK part 1 sdd1 64 14.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 disk sde 12.7T gpt ZTM0ME8H part 1 sde1 2048 12.7T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 disk sdf 931.5G gpt S59VNJ0NA00987F part 1 sdf1 2048 100M gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat part 2 sdf2 206848 16M gpt e3c9e316-0b5c-4db8-817d-f92df00215ae part 3 sdf3 239616 930.6G gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs part 4 sdf4 1951932416 775M gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs md md1p1 12.7T md md2p1 10.9T md md3p1 3.6T disk nvme0n1 931.5G dos 2325E6E73C78 part 1 nvme0n1p1 2048 931.5G dos 0x83 btrfs root@Unraid-Tower:~#
May 10, 20251 yr Author 17 hours ago, itimpi said: Whatever you do, do NOT format unless you want to loose the data on those drives. Doing a New Config was not the correct way to proceed but things should sntill be recoverable. i have not yet reviewed the diagnostics to give informed advice on the best next steps. I haven't formatted any drives yet. I have 16 TB parity, 14 TB data, 12 TB data, and 4 TB data. The 4 TB wasn't affected, and I can still extract the contents from the browse icon beside the green circle. The 14 TB and 12 TB don't have the browse icon next to them, due to them being unmountable, and the file system is now "auto". I'm not sure how to extract/recover the contents. I tried to load into my Windows 11 VM (1TB SSD) and tried to use a program like FTK Imager to read those 2 drives, but no luck.
May 11, 20251 yr Community Expert Those disks are not indicating the filesystem, post output from: wipefs /dev/sde1 wipefs /dev/sdc1 Note that despite the name, it won't wipe anything as written.
May 11, 20251 yr Author 12 hours ago, JorgeB said: Those disks are not indicating the filesystem, post output from: wipefs /dev/sde1 wipefs /dev/sdc1 Note that despite the name, it won't wipe anything as written. root@Unraid-Tower:~# wipefs /dev/sde1 DEVICE OFFSET TYPE UUID LABEL sde1 0x52 vfat 0844-22BA sde1 0x0 vfat 0844-22BA sde1 0x1fe vfat 0844-22BA root@Unraid-Tower:~# wipefs /dev/sdc1 wipefs: error: /dev/sdc1: probing initialization failed: No such file or directory root@Unraid-Tower:~#
May 11, 20251 yr Author root@Unraid-Tower:~# lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL TYPE PARTN NAME START SIZE PTTYPE PARTTYPE FSTYPE LABEL SERIAL loop loop0 579.7M squashfs loop loop1 169.8M squashfs loop loop2 20G btrfs loop loop3 1G btrfs disk sda 14.4G dos F46D0461E280F1A0A94D0187 part 1 sda1 2048 14.4G dos 0xc vfat UNRAID disk sdb 3.6T gpt WD-WCC7K5TY8K0Y part 1 sdb1 64 3.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs disk sdc 10.9T gpt ZRT1HFF4 part 1 sdc1 2048 10.9T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 disk sdd 14.6T gpt ZR59J2JK part 1 sdd1 64 14.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 disk sde 931.5G gpt S59VNJ0NA00987F part 1 sde1 2048 100M gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat part 2 sde2 206848 16M gpt e3c9e316-0b5c-4db8-817d-f92df00215ae part 3 sde3 239616 930.6G gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs part 4 sde4 1951932416 775M gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs disk sdf 12.7T gpt ZTM0ME8H part 1 sdf1 2048 12.7T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 md md1p1 12.7T md md2p1 10.9T md md3p1 3.6T disk nvme0n1 931.5G dos 2325E6E73C78 part 1 nvme0n1p1 2048 931.5G dos 0x83 btrfs root@Unraid-Tower:~# wipefs /dev/sdc1 wipefs: error: /dev/sdc1: probing initialization failed: No such file or directory root@Unraid-Tower:~# wipefs /dev/sdf1 wipefs: error: /dev/sdf1: probing initialization failed: No such file or directory root@Unraid-Tower:~# wipefs /dev/sdc DEVICE OFFSET TYPE UUID LABEL sdc 0x200 gpt sdc 0xae9fffffe00 gpt sdc 0x1fe PMBR root@Unraid-Tower:~# wipefs /dev/sdf DEVICE OFFSET TYPE UUID LABEL sdf 0x200 gpt sdf 0xcbbbffffe00 gpt sdf 0x1fe PMBR root@Unraid-Tower:~# Sorry, this should be more accurate. SDC1 is 12 TB, SDF1 is 14 TB.
May 12, 20251 yr Community Expert Sorry, sde is the wrong disk, but the array must be stopped first, then post the output from: wipefs /dev/sdf1 wipefs /dev/sdc1
May 12, 20251 yr Author 20 minutes ago, JorgeB said: Sorry, sde is the wrong disk, but the array must be stopped first, then post the output from: wipefs /dev/sdf1 wipefs /dev/sdc1 I just did it. Stopped the array, entered the command one by one, but no output was generated.
May 12, 20251 yr Author 7 hours ago, JorgeB said: There should be, and fdisk -l /dev/sdf fdisk -l /dev/sdc root@Unraid-Tower:~# fdisk -l /dev/sdf Disk /dev/sdf: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors Disk model: ST14000NM001G-2K Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: E7BE130F-2699-49F7-866F-587D5C058DC6 Device Start End Sectors Size Type /dev/sdf1 2048 27344762879 27344760832 12.7T Microsoft basic data root@Unraid-Tower:~# fdisk -l /dev/sdc Disk /dev/sdc: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors Disk model: ST12000NM000J-2T Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 16773120 bytes Disklabel type: gpt Disk identifier: 29218FE3-6CB2-4F70-AB68-D7FED1605C55 Device Start End Sectors Size Type /dev/sdc1 2048 23437768703 23437766656 10.9T Microsoft basic data root@Unraid-Tower:~#
May 12, 20251 yr Community Expert Those are Windows formatted disks, they won't mount in the array or pools, only with UD.
May 12, 20251 yr Author 2 hours ago, JorgeB said: Those are Windows formatted disks, they won't mount in the array or pools, only with UD. Understood. Just a side note, I have a 7.0.1 (back when everything worked normally) flash backup zip file. If I were to restore using that, would it restore my original device config, as I already did a "new config" mentioned above, and be able to access my files in the 12 & 14 TB normally? I'm just having trouble mounting; it's greyed out. I've looked into other forum posts for solutions. Edited May 12, 20251 yr by Nads
May 13, 20251 yr Community Expert Do you mean you were using the Windows formatted disks in the array? Also, the wipefs output should still show something, with the array stopped post a screenshot of wipefs /dev/sdf1
May 13, 20251 yr Author 16 hours ago, JorgeB said: Do you mean you were using the Windows formatted disks in the array? Also, the wipefs output should still show something, with the array stopped post a screenshot of wipefs /dev/sdf1 With the array stopped, I entered the commands, and this is what I got (see screenshot). I tried that command for my 4 TB drive to test, it worked fine. I do see a single line output, but not the case for the 14 TB & 12 TB. The 14 TB drive (sdf) is in XFS, but the partition format is "custom" vs the 4 TB drive is "4KiB-aligned". Not sure if that matters. Also, when I set up this Unraid server a couple of months ago, I formatted the drives in XFS in Unraid. I'm not sure how or why it says 'Windows formatted disk.' Maybe it was formatted in Windows once before? Would restoring 7.0.1 using the zip file put the drives' config back or would it not matter cause it's now a Windows formatted disk?
May 14, 20251 yr Community Expert Not sure how you ended up with those partitions, and why they don't indicate which filesystem they are using, but if they are really formatted xfs and were working with 7.0, they should work again if you downgrade, but first post the output from: xfs_repair -n /dev/sdf1
May 15, 20251 yr Author 18 hours ago, JorgeB said: Not sure how you ended up with those partitions, and why they don't indicate which filesystem they are using, but if they are really formatted xfs and were working with 7.0, they should work again if you downgrade, but first post the output from: xfs_repair -n /dev/sdf1 It's still running...
May 15, 20251 yr Community Expert I don't see how that disk could be working with 7.0, but downgrade and retest.
May 17, 20251 yr Community Expert Solution @Nadsdid you downgrade to 7.0 to retest? If it works there, I think I may know what's going on with the partitions. Note that you would likely need to do another new config to get them working there.
June 17, 20251 yr Author On 5/17/2025 at 9:35 AM, JorgeB said:@Nadsdid you downgrade to 7.0 to retest? If it works there, I think I may know what's going on with the partitions. Note that you would likely need to do another new config to get them working there. @JorgeB Sorry for the delayed response, I was out of town for a while. Great news! As of a few minutes ago, the backup I had made back in March 2025 of 7.0.1 worked! I restored to 7.0.1, and nothing else was needed in terms of a new config. All photos and videos are present, and Plex is up and running. I'm gonna stick to 7.0.1 for a while and not get trigger-happy updating to the latest stable build. Thank you for your help and dedication; it helped me get here. I'm not sure why or how things broke in 7.1.2, but hopefully this won't happen again if/when I update down the road. Edited June 17, 20251 yr by Nads
June 18, 20251 yr Community Expert If it's what I think, you will see the issue again after updating to any 7.1.x release, but there's also a way to fix it, post new diags from 7.0
June 18, 20251 yr Author 12 minutes ago, JorgeB said:If it's what I think, you will see the issue again after updating to any 7.1.x release, but there's also a way to fix it, post new diags from 7.0Here's the diagnostics. I hope you're able to determine the cause so I won't have to deal with this issue again. Cheers! unraid-tower-diagnostics-20250618-0000.zip
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.