Hey,

 

Using unraid 6.8.0.

 

I was testing out using the trial for the past week or so, and purchased a license. I had to stop the array to register the key, and when I started it again, the 2 most recent disks I'd added show as unmountable. While there wasn't much data on them, I'd like to understand what happened as I'd hate to have the same thing happen in the future. If possible I'd like to recover the data.

 

Config:

 

1 parity 3TB drives

3 data 3TB drives, disk1 (sdd), 2 (sdg), and 3 (sdj).

1 cache 500gb ssd drive

 

When I start the array, disk2 and disk3 show as unmountable: unsupported partition layout. I am able to mount both disks from and the command line and see the data on them. 

 

SFDisk from the affected drives:

 

root@unraid:/var/log# sfdisk /dev/sdg

Welcome to sfdisk (util-linux 2.34).
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/sdg: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: HUS723030ALS640
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DF4CDD53-D0F9-449E-BC37-E441CF8C860A

Old situation:

Device     Start        End    Sectors  Size Type
/dev/sdg1     64 5860533134 5860533071  2.7T Linux filesystem

Type 'help' to get more information.

>>>
 

 

root@unraid:/var/log# sfdisk /dev/sdj

Welcome to sfdisk (util-linux 2.34).
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/sdj: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: HUS723030ALS640
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D61A55FA-160C-4DD3-A586-564B764EEA88

Old situation:

Device     Start        End    Sectors  Size Type
/dev/sdj1     64 5860533134 5860533071  2.7T Linux filesystem

Type 'help' to get more information.

>>>

 

System info:

 

Model: Custom

M/B: Supermicro X9DRi-LN4+/X9DR3-LN4+ Version REV:1.20A - s/n: NM138S000912

BIOS: American Megatrends Inc. Version 3.0. Dated: 07/05/2013

CPU: Intel® Xeon® CPU E5-2620 0 @ 2.00GHz

HVM: Enabled

IOMMU: Enabled

Cache: 384 KiB, 1536 KiB, 15360 KiB, 384 KiB, 1536 KiB, 15360 KiB

Memory: 128 GiB DDR3 Multi-bit ECC (max. installable capacity 384 GiB)

Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: interface down
 eth1: interface down
 eth2: 1000 Mbps, full duplex, mtu 1500
 eth3: 1000 Mbps, full duplex, mtu 1500
 eth4: interface down
 eth5: interface down
 eth6: interface down
 eth7: interface down

Kernel: Linux 4.19.88-Unraid x86_64

OpenSSL: 1.1.1d

Uptime: 

 

 

These are both connected to a SAS backplane in a supermicro SC847. I've attached the diagnostic report.

 

Thanks,

KS

 

unraid-diagnostics-20191219-0912.zip

Edited December 19, 20196 yr by ksagle

You are likely using SAS multipath, Unraid is seeing each disk twice:

Dec 19 06:09:07 unraid emhttpd: device /dev/sdj problem getting id
Dec 19 06:09:07 unraid emhttpd: device /dev/sdk problem getting id
Dec 19 06:09:07 unraid emhttpd: Device inventory:
Dec 19 06:09:07 unraid emhttpd: HUS723030ALS640_YVJNKHNK_35000cca03e962090 (sdh) 512 5860533168
Dec 19 06:09:07 unraid emhttpd: HUS723030ALS640_YVJNKX4K_35000cca03e96269c (sdg) 512 5860533168
Dec 19 06:09:07 unraid emhttpd: HUS723030ALS640_YVJP3ERK_35000cca03e971ee4 (sdd) 512 5860533168
Dec 19 06:09:07 unraid emhttpd: device /dev/sde problem getting id
Dec 19 06:09:07 unraid emhttpd: Kingston_DataTraveler_3.0_60A44C3FACC9E1B109990049-0:0 (sdb) 512 60632064
Dec 19 06:09:07 unraid emhttpd: HUS723030ALS640_YVJNZXLK_35000cca03e96ea08 (sdf) 512 5860533168
Dec 19 06:09:07 unraid emhttpd: CT500BX100SSD1_1511F00431A3 (sdc) 512 976773168
Dec 19 06:09:07 unraid emhttpd: device /dev/sdi problem getting id

You need to disabled that as it's not supported by Unraid.

Hey Johnnie,

 

Interesting, I didn't think my mobo supported multipath. I disabled it and rebooted and the drives mounted successfully.

 

Thanks for the help.

 

It's not the mobo, it's the backplane, it should be the dual expander model and you have one cable connected to each, like so:

 

 

Correct way is a single cable to expander A (single link) or both cables to expander A (dual link)