NightMan Posted November 5, 2022 Share Posted November 5, 2022 Forgive me, it's been a while since I've used Unraid, but I'm giving it a go again. I have a brand new setup, I have two brand new 4 TB drives installed. They are formattable via terminal commands, and unraid can see them. But even after formatting them through Unraid they continue to say "Unmountable: Unsupported Partition Format" I have searched for several hours and can't find a solution. Both disks show as healthy. Is there any diagnostic data I can include to help solve the issue? Quote Link to comment
trurl Posted November 5, 2022 Share Posted November 5, 2022 10 minutes ago, NightMan said: formattable via terminal commands You must let Unraid format the disks from the webUI after adding them to the array. attach diagnostics to your NEXT post in this thread Quote Link to comment
NightMan Posted November 5, 2022 Author Share Posted November 5, 2022 (edited) I added them to the array, and then format them from the Unraid WebUI, and it formats them, but they remain unmountable. I only tried to format them via terminal as a test, because they're brand new, I was curious if they could be formatted without error. I included the diagnostics and pasted the disk log information that seems to be showing it formatting them in GPT. In the WebUI it shows the filesystem as "auto" Nov 5 16:33:16 mediaserver kernel: ata1: SATA max UDMA/133 abar m1024@0xffb6e000 port 0xffb6e100 irq 41 Nov 5 16:33:16 mediaserver kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 5 16:33:16 mediaserver kernel: ata1.00: ATA-10: ST4000DM004-2CV104, 0001, max UDMA/133 Nov 5 16:33:16 mediaserver kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA Nov 5 16:33:16 mediaserver kernel: ata1.00: configured for UDMA/133 Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes Nov 5 16:33:16 mediaserver kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 5 16:33:32 mediaserver emhttpd: ST4000DM004-2CV104_ZTT4GJQ8 (sdb) 512 7814037168 Nov 5 16:33:32 mediaserver kernel: mdcmd (2): import 1 sdb 64 3907018532 0 ST4000DM004-2CV104_ZTT4GJQ8 Nov 5 16:33:32 mediaserver kernel: md: import disk1: (sdb) ST4000DM004-2CV104_ZTT4GJQ8 size: 3907018532 Nov 5 16:33:33 mediaserver emhttpd: read SMART /dev/sdb Nov 5 16:48:41 mediaserver emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Nov 5 16:48:41 mediaserver emhttpd: shcmd (944): sgdisk -Z /dev/sdb Nov 5 16:48:41 mediaserver emhttpd: shcmd (945): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Nov 5 16:49:20 mediaserver emhttpd: read SMART /dev/sdb Nov 5 16:49:37 mediaserver emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Nov 5 16:49:37 mediaserver emhttpd: shcmd (1052): sgdisk -Z /dev/sdb Nov 5 16:49:37 mediaserver emhttpd: shcmd (1053): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Nov 5 16:33:16 mediaserver kernel: ata2: SATA max UDMA/133 abar m1024@0xffb6e000 port 0xffb6e180 irq 41 Nov 5 16:33:16 mediaserver kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 5 16:33:16 mediaserver kernel: ata2.00: ATA-10: ST4000DM004-2CV104, 0001, max UDMA/133 Nov 5 16:33:16 mediaserver kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA Nov 5 16:33:16 mediaserver kernel: ata2.00: configured for UDMA/133 Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] Write Protect is off Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes Nov 5 16:33:16 mediaserver kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Nov 5 16:33:32 mediaserver emhttpd: ST4000DM004-2CV104_ZTT4MASZ (sdc) 512 7814037168 Nov 5 16:33:32 mediaserver kernel: mdcmd (3): import 2 sdc 64 3907018532 0 ST4000DM004-2CV104_ZTT4MASZ Nov 5 16:33:32 mediaserver kernel: md: import disk2: (sdc) ST4000DM004-2CV104_ZTT4MASZ size: 3907018532 Nov 5 16:33:33 mediaserver emhttpd: read SMART /dev/sdc Nov 5 16:48:41 mediaserver emhttpd: writing GPT on disk (sdc), with partition 1 byte offset 32KiB, erased: 0 Nov 5 16:48:41 mediaserver emhttpd: shcmd (950): sgdisk -Z /dev/sdc Nov 5 16:48:41 mediaserver emhttpd: shcmd (951): sgdisk -o -a 8 -n 1:32K:0 /dev/sdc Nov 5 16:49:20 mediaserver emhttpd: read SMART /dev/sdc Nov 5 16:49:37 mediaserver emhttpd: writing GPT on disk (sdc), with partition 1 byte offset 32KiB, erased: 0 Nov 5 16:49:37 mediaserver emhttpd: shcmd (1058): sgdisk -Z /dev/sdc Nov 5 16:49:37 mediaserver emhttpd: shcmd (1059): sgdisk -o -a 8 -n 1:32K:0 /dev/sdc mediaserver-diagnostics-20221105-1625.zip Edited November 6, 2022 by NightMan Quote Link to comment
NightMan Posted November 6, 2022 Author Share Posted November 6, 2022 (edited) I popped in one of my old 2 TB HDDs. It formatted and mounted no problem. I cannot figure out what the issue is here. It seems unlikely, although possible, that both of these drives have the same defect out of the box. Edited November 6, 2022 by NightMan Quote Link to comment
Solution JorgeB Posted November 6, 2022 Solution Share Posted November 6, 2022 It's a bug with the latest release, for now suggest downgrading to v6.11.1 to format the disks, you can then upgrade back if you want. 1 Quote Link to comment
NightMan Posted November 6, 2022 Author Share Posted November 6, 2022 (edited) 10 hours ago, JorgeB said: It's a bug with the latest release, for now suggest downgrading to v6.11.1 to format the disks, you can then upgrade back if you want. Oh that's actually great news, easy fix then. Thank you. Edit: And it worked! Thank you. Edited November 6, 2022 by NightMan 1 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.