[Solved] First Red Balled Drive, does it need replaced?

[mostlydave]

I got my first drive error today, attached is my diagnostics and smart report (which didn't really run)

 

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.5-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /14:0:0:
Product:              0
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
Physical block size:  3166222336 bytes
Lowest aligned LBA:   12346
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

zelda-diagnostics-20150916-1651.zip

[redlaws]

[600 PB] that might be a reiserfsck error

rebuild-tree might be required.

do you have a spare drive the same size you can add if required, if not get one.

[Squid]

[600 PB] that might be a reiserfsck error

Definitely nothing to do with the file system on the drive

[SSD]

I got my first drive error today, attached is my diagnostics and smart report (which didn't really run)

 

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.5-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /14:0:0:
Product:              0
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
Physical block size:  3166222336 bytes
Lowest aligned LBA:   12346
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

This is the kind of result I'd expect if the smartctl program is called with the wrong parameters. It could also be signs of a seriously broken disk or a very poor connection.

 

I have an issue with my Areca drives, which require a very specific syntax to pull smart reports. I have noticed that the smart report is totally hosed (similar to what you are seeing) when I call it when the drive is spun down. If I run it a second time (now the drive is spun up), it works fine. Not suggesting this is your issue (the WebGUI is not able to pull smart reports for Areca connected drives) but you could have something controller specific going on.

[tdallen]

What kind of disk controller do you have that disk on?

 

Also, do you get a better smart report after rebooting?

[mostlydave]

I ended up just replacing it, everything's good now, thanks for the replies!