NASLite Network Attached Storage

Hi all,

I 've been getting these error messages in the syslog every minute precisely from one of my disks. Has anyone seen something similar?

I suspect that the disk may be going bad. Any bets?

Have you considered posting the actual text of the error message?

OOPS!

Nov 5 21:02:02 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Nov 5 21:02:02 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Nov 5 21:02:02 user.err kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Nov 5 21:02:02 user.warn kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Nov 5 21:02:02 user.warn kernel: ata1: error=0x04 { DriveStatusError }
Nov 5 21:03:02 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Nov 5 21:03:02 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Nov 5 21:03:02 user.err kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Nov 5 21:03:02 user.warn kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Nov 5 21:03:02 user.warn kernel: ata1: error=0x04 { DriveStatusError }

I assume this is a SATA drive? Regardless, this error can be generated by a drive that does not support or respond properly to a given SMART command. Disable SMART for that drive and see if the problem disapears.

Tony, it's actually a PATA drive, a Maxtor, as Drive-1.

MODEL: Maxtor 6Y080P0, SN# Y34Q7G3E, v.YAR41BW0
INTERFACE: IDE, HOST-0, BUS-0, TARGET-1, LUN-0

What's strange is that I have an identical model drive as Drive-0 on which Smart works very well.

On this one it just shows Smart Enabled.

Any clues on how to get this working properly other than disabling smart?

Try the simplest thing first, replace the cable to the drive/s.

Mike

This would mean that I would have to shut the server down.....

Unscheduled maintenance was not in the program

Welcome to the wonderful world of servers.

Mike

I wonder how long it would take for a NASlite server to die, ie stop serving files alltogether, if one ignored all error messages and kept it running no matter what.....

I think it would be several months....

This thing is just so reliable....

Couple of things:

1. In the system BIOS, turn SMART on. If SMART is set to OFF, many BIOS will disable drive SMART on boot, causing some drives to generate such errors when NASLite probes.

2. Check if the firmware in the bad drive is the same as the firmware in the good drive and upgrade/downgrade if possible.

I'd take a look at the cable also as mikeiver1 suggested. Other than that, the only bad thing that you will eventually see is a large syslog filled with the same drive errors. NASLite-2 will continue to do it's job as far as the hardware cooperates.

Hi,

From what I have read and seen myself it means that a command is being set that the drive does not understand hence the error message,
But you have a identical model and this does not produce this error. Can you confirm they both have the same firmware.

Check this out http://www.captain.at/howto-linux-drive ... serror.php

They have the same firmware and disabling SMART has no effect. I may retire the drive alltogether. It's only 80Gb anyway.