Second HDD Not Showing in Console

[MartinCorby]

Setting up FreeNAS for the first time on an older machine.

Installation has gone swimmingly - booted from CD onto USB Flash drive all OK.

System is set up with x2 1TB HDD :

1. WESTERN DIGITAL Green WD10EADS 1TB SATA II 32MB
2. Seagate 1TB 3.5" SATA Desktop Hard Drive

The USB Flash drive and both HDD's show up in the BIOS and during boot, BUT only the Western digital HDD and USB Flash drive are present within the FreeNAS Console.

I have double checked to make sure FreeNAS is loaded onto the USB Flash drive and boots from there (I disconnected the HDD's during installation)

I'm looking for a steer as to how I can get FreeNAS to recognise the second (Seagate) HDD

Output from dmesg :

da0: 3864MB (7913472 512 byte sectors: 255H 63S/T 492C)
da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
SATA 3.x device
ada0: Serial Number Z4Y4NY6X
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad10
ada1 at ahcich3 bus 0 scbus4 target 0 lun 0
ada1: <WDC WD10EADS-00M2B0 01.00A01> ATA-8 SATA 2.x device
ada1: Serial Number WD-WCAV5J490135
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad12
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1200986158 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/default []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
wbwd0: DevID 0xa0 DevRev 0x23, will not attach, please report this.
vboxdrv: fAsync=0 offMin=0x3f0 offMax=0x84c
pid 1514 (syslog-ng), uid 0: exited on signal 6 (core dumped)
[root@freenas ~]#

Attached is the Debug dowmload

Hope all that helps

 

[joeschmuck]

Have you tried a different SATA port or SATA cable? Also, looks like ada1 was previously used, did you not wipe them slick before trying to use them again or did you still want that data?

 

[MartinCorby]

Blimey - thats a speedy response !
Yes, I have tried both the options of different cables and different ports with no change in status.
Yes, the WD HDD has been used before - I thought it had been formatted and emptied, is this wrong and if so, should it be attended to ?
The Seagate drive is brand new.

 

[MartinCorby]

Not sure if this helps, but looking in the "Reporting" > "Disc" tab, both ada0 and ada1 are reporting their status

 

[joeschmuck]

Tell me more about the Seagate drive, model and have you tried it in any other computer? You may have a failed hard drive even thought the BIOS recognizes it. I'm grasping at straws here, normally if it reports in the BIOS I would expect it to show up.

 

[MartinCorby]

OK, the new Seagate drive is as follows :

• Seagate Desktop HDD
• S/N - Z4Y4NY6X
• Model - ST 1000DM003

I will try it in another box and report back

 

[MartinCorby]

OK, so I moved the Seagate HDD to another box (Windows based machine) - booted up and it can be seen in the BIOS (as previous) but when exploring via My Computer, only the original "C" drive is showing which does point ptowards there being a problem with the drive ?

 

[Redcoat]

In Windows, try looking under Computer Management:

1. Open Computer Management by clicking the Start button
   
   , clicking Control Panel, clicking System and Security, clicking Administrative Tools, and then double-clicking Computer Management.‌
   
   If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
   
   
2. In the left pane, under Storage, click Disk Management, and then look for the new drive.

If it's there, it's likely OK (but not partitioned for Windows).

If that's the case I would check the drive controller in your NAS machine by installing the new drive in place of the WD ada1.

 

[MartinCorby]

Redcoat - thanks for your advise.
New drive back into Windows machine and probably as you would predict, the new drive is there, albeit not with a drive letter (I assume as it is not partitioned for windows)
So back to FreeNAS machine with it and the result is just the USB Flash drive shows up in the FreeNAS Console :(

 

[Redcoat]

Can you put the drive back in your windows machine (take out the Windows HDD(s)) and boot it up with your FreeNAS stick?

 

[joeschmuck]

I agree with Redcoat, since you have another machine, this would at least eliminate or confirm the hard drive completely. If it works then there is something up with your FreeNAS computer. Tell use again what the MB model is please, and do you have the latest BIOS update for it.

 

[MartinCorby]

Booted the Windows machine with the original HDD unplugged, the Seagate HDD and FreeNAS USB Flash drive plugged in. After boot up it does not give me an IP address to log in to to check drives - is there another way of checking using a cmd prompt ?

 

[SweetAndLow]

From the console you can select shell and type can camcontrol devlist.

Edit: fixing typo from phones auto correct.

 

[joeschmuck]

type can control devlist.

That would be a mild typo, try "camcontrol devlist"

 

[MartinCorby]

Output from camcontrol devlist :

<HDD Ref> at scbus5 target 0 lun 0 (pass0, ada0)
<USB Ref> at scbus7 target 0 lun 0 (pass0,ada0)

 

[joeschmuck]

It kind of bothers me that both drives are being reported as "ada0", are you sure you didn't hit a typo there and the USB line isn't "da0"?

 

[MartinCorby]

Typo - Sorry !
Second line should be :
<USB Ref> at scbus7 target 0 lun 0 (pass1,da0)

 

[joeschmuck]

So it looks like your FreeNAS motherboard is not recognizing the hard drive properly. For the hell of it, on your FreeNAS system, toss in that Seagate hard drive and do the same thing you just did before, "camcontrol devlist" and what does it output? If it has a similar output where ada0 is the HDD, then add the WD hard drive and try again. You should have listed two HDD and the USB drive. If all three show up then let us know. Also, what MB is in your FreeNAS system?

 

[joeschmuck]

Update: So I decided to look at your debug data. You do realize you do not have a system capable of running FreeNAS, right? You cannot run FreeNAS on 1.5 GB of RAM, you need 8GB minimum. Also according to the data you provided both drives were recognized and it likely crapped out on you because of insufficient memory. This was a waste of my time and others time. Please read the system requirements before jumping in and trying some software like this.

Sep 5 13:27:09 freenas ada0: <ST1000DM003-1ER162 CC45> ATA-9da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
Sep 5 13:27:09 freenas da0: <SMI USB DISK 1100> Removable Direct Access SCSI-4 device
Sep 5 13:27:09 freenas da0: Serial Number AA77ZXOS758S1TJ5
Sep 5 13:27:09 freenas cd0 at ata2 bus 0 scbus2 target 0 lun 0
Sep 5 13:27:09 freenas cd0: <Optiarc DVD RW AD-5170A 1.11> Removable CD-ROM SCSI-0 device
Sep 5 13:27:09 freenas cd0: 66.700MB/s transfers (UDMA4, ATAPI 12bytes, PIO 65534bytes)
Sep 5 13:27:09 freenas cd0: Attempt to query device size failed: NOT READY, Medium not present
Sep 5 13:27:09 freenas da0: 40.000MB/s transfers
Sep 5 13:27:09 freenas da0: 3864MB (7913472 512 byte sectors: 255H 63S/T 492C)
Sep 5 13:27:09 freenas da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
Sep 5 13:27:09 freenas SATA 3.x device
Sep 5 13:27:09 freenas ada0: Serial Number Z4Y4NY6X
Sep 5 13:27:09 freenas ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Sep 5 13:27:09 freenas ada0: Command Queueing enabled
Sep 5 13:27:09 freenas ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
Sep 5 13:27:09 freenas ada0: quirks=0x1<4K>
Sep 5 13:27:09 freenas ada0: Previously was known as ad10
Sep 5 13:27:09 freenas ada1 at ahcich3 bus 0 scbus4 target 0 lun 0
Sep 5 13:27:09 freenas ada1: <WDC WD10EADS-00M2B0 01.00A01> ATA-8 SATA 2.x device
Sep 5 13:27:09 freenas ada1: Serial Number WD-WCAV5J490135
Sep 5 13:27:09 freenas ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)

 

[MartinCorby]

I sincerely apologise (and thanks for yours and others time and effort)
I will upgrade the RAM tomorrow after which time I will let you know what a shmuk I've been.
(And for my own education purposes, how does the additional RAM make the difference - what is happening to allow the system to recognise the second drive ?)
.....for info, what doesn't help FreeNAS are articles on the internet that show up when you search for "Build home server from old PC"