Hard Disk Not Visible

[spawn27]

hello,
excuse me for my english and for my low acknowledge on this kind of systems.

I was an old good user of SUN Solaris but in the last 15 years I have forget more or less all.

the problem.

I am bought HP miniserver N36L and easily installed Freenas 8.0 RELEASE amd64 on 8gb kingston pen drive.

After consulting forums I've understood that the bundled 1Gb Ram was not sufficient and upgraded to 4Gb; I've understood also that bundled HP (seagate) 250Gb HDD was unusable due to AHCI protocol (that I have disabled also in N36L bios) so I'm bought 2 brand new 2Tb seagate HDD (type ST2000DL003) and also mounted as mirrored volume UFS.

it was my intention also create in the 2 empty slot a stripe volume using 2 Seagate 1Tb I already have (type ST31000528AS) ... coming from my 1year-old ICY BOX NAS that suddenly dead.... :(
but
as soon as I empty them and tried to use they was not available as mountable device even if I see them during the boot phase of the server as ada0 and ada1 dsck.

so I read in this forum that I should clear completely the disk and I provide using BSD command (see this thread http://forums.freenas.org/showthread.php?1360-Howto-remove-partitions&highlight=disk+volume )

although this the disk is not mountable .... but if I use usb adaptor and connect the HDD to the server I can see and create a volume!!!!

Why it is possible via USB and not via SATA ?

thanx in advance for your answer.

Mimmo

 

[Milhouse]

Before trying anything else, upgrade to 8.0.1-RC1 as RELEASE had a whole host of problems.

I would also suggest you re-enable AHCI in the BIOS. FreeNAS 8 originally had trouble accessing the HP 160GB/250GB disk that came with the N36L due to HP installing unusual disk firmware but that is hopefully fixed now, I'm not aware of problems with non-HP disks.

 

[spawn27]

Hi Milhouse, thanx a lot for your answer. I've note you was an expert on N36L but I was afraid to disturb you directly... :)
I'll follow your suggestion and inform about the results.

best regards
Mimmo

 

[FatIdiot]

I am actually in the same scenario. I tried moving back to FreeNas 7 with no luck and later read that the drive issues were resolved in a nightly release in early August so I moved up to the most recent to see. Still no drives detected.

 

[spawn27]

so, it means there is no new good results if I upgrade to last version!!!!

anyway I still can't understand the difference between the HDD. they are all seagate ... why It is not possible to see the old ones!?

any hint?

 

[spawn27]

Hello :)
following the suggestion of Milhouse I reboot N36L using last available versione of FreeNAS (8.0.1.RC1) and finally I can see as moutable my old 1T seagate HDD.

unfortunately I have now a NEW problem.

before all I have to explain that 1 of the 2 HDD was today replaced with a new-one brand brand new.

I try to mound the two 1T HDD as UFS STRIPED volumes but I receive this message:

Code:

Sep 15 01:48:21 Freenas freenas[1719]: Executing: geom stripe load
Sep 15 01:48:21 Freenas freenas: geom: Command 'load' not available.
Sep 15 01:48:21 Freenas freenas[1719]: Popen()ing: geom stripe label STOREstripe  /dev/ada2 /dev/ada3
Sep 15 01:49:59 Freenas freenas[1719]: Popen()ing: sysctl -b kern.geom.confxml

I repeat 3 times with the same bad result.

so I try to create UFS volume individually for each HDD but the message was for both

Code:

Sep 15 01:50:15 Freenas freenas[1719]: Executing: dd if=/dev/zero of=/dev/ada2 bs=1m count=1
Sep 15 01:50:15 Freenas freenas: dd: /dev/ada2: Operation not permitted
Sep 15 01:50:15 Freenas freenas[1719]: Executing: dd if=/dev/zero of=/dev/ada2 bs=1m oseek=`diskinfo ada2 | awk '{print int($3 / (1024*1024)) - 4;}'`
Sep 15 01:50:15 Freenas freenas: dd: /dev/ada2: Operation not permitted
Sep 15 01:50:15 Freenas freenas[1719]: Popen()ing: gpart create -s gpt /dev/ada2

what's happen now???

 

[spawn27]

any hint?
Thanks

 

[ProtoSD]

From the error messages you posted, it looks like it's failing to wipe your disks because the GUI is not executing them with the correct privileges. You can try and execute the following command from the console #9 on the menu.

1) su (enter the admin/root password)
2) dd if=/dev/zero of=/dev/ada2 bs=1m count=1
3) dd if=/dev/zero of=/dev/ada2 bs=1m oseek=`diskinfo ada2 | awk '{print int($3 / (1024*1024)) - 4;}'`

Keep all of the punctuation marks in #3

Repeat the steps for your other disks and change the 'ada2' to the device names of your other disks. Find those either in the GUI or using 'dmesg' from the command line and looking for them.

The appears to be a possible bug with the GUI.

 

[spawn27]

thanx a lot for reply.
now in Italy is 2:16 and I'm really tired after long day work... so I'll try tomorrow morning and will post the results :)
I'm only asking myself how/what i s the difference between >'< and ... .... how have you written > ` < (now I used copy and past) ...

regards

 

[Milhouse]

thanx a lot for reply.
now in Italy is 2:16 and I'm really tired after long day work... so I'll try tomorrow morning and will post the results :)
I'm only asking myself how/what i s the difference between >'< and ... .... how have you written > ` < (now I used copy and past) ...

regards

The ` (backtick) in Unix/Linux will execute the enclosed command, often passing the results (as in this case) to the enclosing command, so

Code:

dd if=/dev/zero of=/dev/ada2 bs=1m oseek=`diskinfo ada2 | awk '{print int($3 / (1024*1024)) - 4;}'`

runs the dd command in order to overwrite the end of the disk with zeroes, using 1MB blocks. It calculates the seek position (oseek) in terms of block size, using the command "diskinfo ada2 | awk '{print int($3 / (1024*1024)) - 4;}'" which converts the disk size from bytes to megabytes and then subtracts 4 blocks/megabytes. The calculated value is used as the oseek argument, so in effect the last 4 megabytes/blocks of the disk are cleared as dd will keep writing until it gets a write error.

 

[ProtoSD]

Gcooper offers some possible insight to this problem with this ticket (following the ticket I opened for this problem):
https://support.freenas.org/ticket/794

 

[spawn27]

Tanx Milhouse for the detailed explanation of what this row of command does and how to work.

I supposed it works as special character.... like | (pipe) that redirect an output of a command in another...
My question now is how to find it on my keyboard ...
general keyboards have ' , " , and as back*** only \ (backslash) ... I suppose I have to use the copy&past :) but how have you digit it (couriosity).

:)


OPS.... I searching with google and I found how to digit backtick on keyboard :)

Alt Gr + ' = `
Alt Gr + ì = ~

or

ALT+0096 = `
ALT+0126 = ~

unfortunately not freenas console neither putty emulator accept these combinations of keys :(

 

[spawn27]

I'll became crazy!!!

I follow the suggestion of Protosd
reboot the N36L and this is the dmesg (extract):

Code:

ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <ST31000528AS CC38> ATA-8 SATA 2.x device
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)
da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <Kingston DT 100 G2 1.00> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST31000524AS JC4B> ATA-8 SATA 3.x device
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)
SMP: AP CPU #1 Launched!
GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
Trying to mount root from ufs:/dev/ufs/FreeNASs1a

looking in the GUI to create the volume this is what I see:

fig.1

but the strange is if I exchange the disks in the bay of the server:

fig.2

and the scenario in fig. 2 is the same if I use only one HDD!!! (I made several test using SATA2 HDD or SATA3 HDD [because this is the only difference I see between the two disks] moving them in each bay of the server)

... why this behavior ??
I'm serious think to sell this 2 disk and to buy 2 new 2 tera HDD egual to the other 2 that I use in mirror on N36L (momentary disconneccted to make these tests)

regards

 

[ProtoSD]

spawn27,

That is a very frustrating problem, but it does appear that your thought that it is because the disk is SATA-3 could be true. Do you have another SATA-2 disk to verify this?

 

[spawn27]

Yes, I have, but I don't think the problem is SATA-2 or 3.

as I wrote I try to mount alternatively SATA-2 alone in each bay of the server and SATA-3 also and never never I have seen it. only when I put them together (in bay 0 and bay1) I can see, but only one of them.

just to show this is the actual dmesg of N36L where I connect 2x2Tera SATA3, 2x1Tera SATA2 and SATA3 (the fomous HDD) and an external 120G IDE via USB (via USB I alway see every kind of HDDs :D )

Code:

ada0 at ahcich0 bus 0 scbus0 target 0 lun 0da0 at umass-sim0 bus 0 scbus6 target                                 0 lun 0
da0: <Maxtor 6 Y120P0 > Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 117246MB (240121728 512 byte sectors: 255H 63S/T 14946C)

ada0: <ST31000524AS JC4B> ATA-8 SATA 3.x device
da1 at umass-sim1 bus 1 scbus7 target 0 lun 0
da1: <Kingston DT 100 G2 1.00> Removable Direct Access SCSI-0 device
da1: 40.000MB/s transfers
da1: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C)
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)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST31000528AS CC38> ATA-8 SATA 2.x device
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)
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <ST2000DL003-9VT166 CC32> ATA-8 SATA 3.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <ST2000DL003-9VT166 CC32> ATA-8 SATA 3.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
SMP: AP CPU #1 Launched!
GEOM_MIRROR: Device mirror/PIAZZAmirror launched (2/2).
GEOM: da1s1: geometry does not match label (16h,63s != 255h,63s).
Trying to mount root from ufs:/dev/ufs/FreeNASs1a
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 4
ZFS storage pool version 15

:(