hi, im getting these errors after installing two new 2TB disks, a samsung and a hitachi.

 

May 18 02:22:03 HAL kernel: ata1: error=0x04 { DriveStatusError }

May 18 02:22:03 HAL kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00

May 18 02:22:03 HAL kernel: ata1: status=0x51 { DriveReady SeekComplete Error }

May 18 02:22:03 HAL kernel: ata1: error=0x04 { DriveStatusError }

 

is one of them two a bad disk ?

 

pls advise.

 

attached is the complete syslog.

syslog-2010-05-18.zip

wow .. this is a duplicate report of

 

New HD203WI, AOC-SASLP-MV8 and SMART

 

there's definitely something going on with the Samsung 2TB and the AOC-SASLP-MV8 ...

 

i have on Samsung 1TB attached to this card and i'm having no problem ...

 

i'm currently preclearing both the hitachi and the samsung, i'll see how it ends up when it's done

As per the other thread

 

I had similar issues with this drive and the AOC-SASLP-MV8 but managed to solve it by removing my Adatec 1210SA card.

 

http://lime-technology.com/forum/index.php?topic=6191.0

 

What other cards have you got in the machine. Do you see a correct bios init for the card when booting up?

In my case its a brand new reccomended build server.  My preclear runs would either never start (stuck at 0%) or would freeze shortly thereafter.  I have 8 drives installed now with no other issues.  Also no more of the 2TB sammys. 

 

 

 

Antec 1200

Antec CP-850

SUPERMICRO X7SBE

Intel Celeron 430 1.80GHz

Kingston Ddr2 800Mhz Ecc Kvr800D2E5

Supermicro Add-on Card AOC-SIM1U+

Supermicro Add-on Card AOC-SASLP-MV8 (X2)

Supermicro CSE-M35T-1B Mobile Rack (Black) (X4)

 

What other cards have you got in the machine. Do you see a correct bios init for the card when booting up?

Just 2 AOC-SASLP-MV8. BIOS init is fine.

 

On my system all error messages and problems with the 2TB sammys stopped after enabling SMART reporting on them. They are now active and working perfectly. One of them is my parity drive.

I added a second one and it was not reporting smart until the preclear completed . I will check it reporting smart and add it to my array tonight. One of the thing I did do on the first one was smartctl --smart=on /dev/sd?

 

Good to hear you are up and running OK.

What other cards have you got in the machine. Do you see a correct bios init for the card when booting up?

Just 2 AOC-SASLP-MV8. BIOS init is fine.

 

On my system all error messages and problems with the 2TB sammys stopped after enabling SMART reporting on them. They are now active and working perfectly. One of them is my parity drive.

 

greybeard, how did you enable smart reporting on the 2TB Samsung ?

For one drive I issued command "smartctl -s on /dev/sdb" from a telnet session. Be sure to change /sdb to your device.

 

For another drive it was turnd on automatically by connecting the drive to a motherboard port and running a smart status display. Not sure if it was just connecting the drive to the mobo port or actually running the smart status that actually enabled SMART reporting, since I did both.

 

I understand there is a command in the preclear script to enable smart reporting but for some reason it failed to enable it on these drives in my system. I ran preclear on all three drives but still had to explicitly enable SMART reproting after the preclear was done on all three of them.

For one drive I issued command "smartctl -s on /dev/sdb" from a telnet session. Be sure to change /sdb to your device.

 

(courtesy of The Matrix, via Neo aka Keanu Reeves) ... woa !

 

that DID it !!! i was __this__ close to throwing it to the dust bin

 

thanks a lot greybeard.

I had the issue reappear today with a 1 yr old 1.5TB sammy as I was moving it from a windows pc to Unraid.  I too got it to work by enabling SMART reporting with the smartctl -s command.  All was fine then.  In hindsite, the 2TB I had would have probably been fine had I known this then.  

 

footnote..  I did have to stop unraid and reboot before I could get the command to enable SMART. (This time it did preclear first).

In my case the errors all showed up when using various functions of unMenu or running the preclear script. I am guessing that in a pure unRAID system there would have been no errors but have not tested that theory. I am not suggesting there is anything wrong with either unMenu or the preclear script, they are great tools that do things unRAID doesn't. Ultimately I supsect something at a lower level, like the MV8 driver or something in the SAS support module.

In my case the errors all showed up when using various functions of unMenu or running the preclear script. I am guessing that in a pure unRAID system there would have been no errors but have not tested that theory. I am not suggesting there is anything wrong with either unMenu or the preclear script, they are great tools that do things unRAID doesn't. Ultimately I supsect something at a lower level, like the MV8 driver or something in the SAS support module.

Both unMENU and the pre-clear script use the "smartctl" command to get disk drive status and temperature.  It is highly likely the smartctl command is attempting to get information from the drive that the driver is not coded to supply since it is a general purpose utility program. 

 

A stock unRAID system does not use the "smartctl" command.  It queries the disks using the same type of low level IO requests as smartctl, but probably does not issue all that smartctl uses.

 

A stock unRAID system does not use the "smartctl" command.  It queries the disks using the same type of low level IO requests as smartctl, but probably does not issue all that smartctl uses.

 

 

With this the case, It's possible then that if the Sammy was added then just let stock unraid clear and format the drive.. it probably would have worked ok, albiet no SMART data (temp, etc).

Hello,

 

Please understand that I am Linux illiterate.

 

I am figuring it is okay to run this command from the server console?  I've never used Telnet with the uNRaid.  Also, how do I identify what "sdb" is?  It's just a bit greek to me.

 

 

For one drive I issued command "smartctl -s on /dev/sdb" from a telnet session. Be sure to change /sdb to your device.

 

 

Thanks.

I have a HD203WI drive.  I enabled SMART using "smartctl -s on /dev/sdb" command.  I then ran the preclear script.  Preclear failed on this drive.  With this drive connected unRAID won't boot.  The last post in this thread has a link to sceenshots that show what happens when unRAID is trying to boot.

http://lime-technology.com/forum/index.php?topic=8426.0

   

As soon as I remove the SATA cable from this drive, unRAID will boot.

 

Can anyone lend a hand?

thanks in advance,

sean

I have a HD203WI drive.  I enabled SMART using "smartctl -s on /dev/sdb" command.  I then ran the preclear script.  Preclear failed on this drive.  With this drive connected unRAID won't boot.  The last post in this thread has a link to sceenshots that show what happens when unRAID is trying to boot.

http://lime-technology.com/forum/index.php?topic=8426.0

     

As soon as I remove the SATA cable from this drive, unRAID will boot.

 

Can anyone lend a hand?

thanks in advance,

sean

 

Yeah, it looks like the boot device is getting shuffled around when you add that drive.

 

Just select the JD Firefly drive and unRAID should boot.

 

Also, check the BIOS settings for your motherboard to see if you can make it ALWAYS boot from the JD Firefly and ignore other drives.

In my motherboard I could of sworn I was able to deselect all possible drives and only allowed my USB. Then from that menu I said boot from USB since it was the only available disk to make it even more idiot proof for myself.

Those pictures do not show a loop, although it looks like one.

 

They show a series of media errors (translation ... un-readable sectors)

 

It is just that the drive has 2930277168 sectors... and apparently more that a few are un-readable.

 

Get a full smart report on that drive and you'll probably see the sectors pending re-allocation. (or already re-allocated)

 

smartctl -d ata -a /dev/sdb

 

as far as the boot device... some motherboards try to help you by assigning any new disk as the boot device.  (overriding your setting until you re-set the flash drive as the boot device)

I checked BIOS and ensured that my boot device was my usb flash drive.  unRAID still won't boot.  during the boot screen I get a "failed command: READ FPDMA QUEUED"

 

If I unplug the SATA cable for this drive during the boot screen, unRAID will finish loading and I can log in.  Since the drive is not attached, I attached it and can see it under 'disk management' 

 

partition (1,953,514,584 blocks): /dev/sdf

partition (1,953,514,583 blocks): /dev/sdf1

 

If I run "smartctl -d ata -a /dev/sdf"

it returns "smartctl open device:  dev/sdf/ failed:  no such device"

if anyone could shed some knowledge i would be really grateful... this drive was working OK for ~2 years in a external drive (samsung story)

unRAID is NOT hot-plug capable.  It sounds as if you are connecting and disconnecting drives with power applied.

 

The fact that the drive is not readable by the smartctl program is the first hint that it will not work when accessed.

 

You can try

hdparm -I /dev/sdf

 

Some of the drives in USB cases have custom firmware.  They might not be usable when used with a different controller.

 

Joe L.

As you mentioned, Joe, the image I posted earlier does not show a loop.  With the drive connected unRAID eventually booted.  I was then able to clear and format the disk within unMENU. 

 

thanks again