I just installed a Supermicro AOC-SASLP-MV8 into my UNRAID v4.5.6 server. The MB is a Supermicro C2SEA.

BIOS sees the new controller, and the controller BIOS sees the single drive I have installed - 2TB WD EADS.

However, UNRAID does not see the drive. I have 6 other drives currently running via the MB SATA ports.

 

I am guessing that I have to low-level format the drive via the controller BIOS before UNRAID can see it. Before I go to that lengthy process, would some please verify my guess?

 

I've attached my latest syslog.

 

Thanks!

 

Scott

syslog.txt

I just installed a Supermicro AOC-SASLP-MV8 into my UNRAID v4.5.6 server. The MB is a Supermicro C2SEA.

BIOS sees the new controller, and the controller BIOS sees the single drive I have installed - 2TB WD EADS.

However, UNRAID does not see the drive. I have 6 other drives currently running via the MB SATA ports.

 

I am guessing that I have to low-level format the drive via the controller BIOS before UNRAID can see it. Before I go to that lengthy process, would some please verify my guess?

 

I've attached my latest syslog.

 

Thanks!

 

Scott

You are wrong.  There is no need to low-level-format ANY drive EVER.  That whole concept ended about 20 or 30 years ago when the last of the MFM and RLL drives were manufactured.  There is no provision in any modern drive to "low-level-format" it. (Well, there probably is, but the manufacturers don't provide access to it through the SATA interface)  See here: http://en.wikipedia.org/wiki/Disk_formatting

 

The closest we get today is to write zeros to the entire drive erasing it, but that has absolutely nothing to do with the OS seeing it, for to erase it it already has to be able to see it.

 

You might have a bad disk, a bad cable, a bad connection, a bad disk controller, the wrong option set in the BIOS, or even the wrong BIOS for your disk controller card, but the first step would be to get the BIOS to see the drive before you even attempt to boot unRAID.  Then, if it does not see the drive it could be a missing driver for your disk controller.  

 

Joe L.

Thanks for your input. The BIOS on the AOC-SASLP-MV8 DOES give an option to low-level format, that is what threw me. Seeing as how the BIOS of the card sees the drive, I can't imagine this being a cabling problem. Might it be that the version of UNRAID I have (4.5.6) does not have support for this controller?

 

Scott

I upgraded to v4.7, and added UNMENU. Interestingly, the added drive DOES show up in UNMENU:

 

********************************

Array Status  STARTED, 6 disks in array.    Parity is Valid:.  Last parity check < 1 day ago .  Parity updated  15 times to address sync errors. 

Array Disk Status

Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free

OK parity /dev/sdc 32S_WD-WCAVY4592856 * 1728787 8565

OK /dev/md1 /mnt/disk1 /dev/sdd 32S_WD-WCAVY4582724 * 1730943 5 2.00T 1.97T 99% 31.22G

OK /dev/md2 /mnt/disk2 /dev/sde 32S_WD-WCAVY4595776 * 2469714 142 2.00T 1.97T 99% 30.51G

OK /dev/md3 /mnt/disk3 /dev/sdf 22R_WD-WCAVY4860951 * 1900850 5 2.00T 1.97T 99% 31.13G

OK /dev/md4 /mnt/disk4 /dev/sdg 32S_WD-WCAVY4540375 * 2108077 5 2.00T 1.97T 99% 30.98G

OK /dev/md5 /mnt/disk5 /dev/sdh 22R_WD-WCAVY4424817 * 1641713 8295 2.00T 1.96T 99% 35.58G

Total: 10.00T 9.84T 98% 159.42G

UNRAID Drive

Device Model/Serial Mounted File System Size Used %Used Free

/dev/sda1 usb-Lexar_JD_FireFly_3PM5C9THE5XPJW6SR41B-0:0 /boot vfat 2.00G 67.86M 4% 1.94G

Drive Partitions - Not In Protected Array

Device Model/Serial Mounted File System Temp Size Used %Used Free

/dev/sdb WDC_WD20EADS-00R6B0_WD-WCAVY5160916 30°C 2.00T

********************************************

 

It is /dev/sdb. Notice that it is not part of the array. Can anybody explain that to me? How do I get it added to the array?

 

Thanks!

 

Solved - user error, as usual. I had not added a drive in so long that I forgot that I had to take the array off-line, and then add the drive manually to the array.

 

Thanks for your time!