NASLite Network Attached Storage

I am a new NASLite+ user ...... everything has been going pretty well, however I have now received the following error on two occasions:

Smartctl: Hard Drive Read Identity Failed

A mandatory SMART command has failed: exiting. To continue, turn on the -P option

When this occurs the NASLite+ server becomes unresponsive and the following appears under the DISK Tab:

Disk-3 Hardware
• drive not ready for command
• status timeout: status=0xd0 { Busy }
• drive not ready for command
• status timeout: status=0xd0 { Busy }
• drive not ready for command
...... repeated over and over.

When I shutdown the server using TELNET and Restart that disk shows up as follows:

Disk-3 Initialization Messages

1. Checking for Disk-3
2. Found Disk-3 partition
3. Attempting to fix Disk-3 filesystem
4. Disk-3 filesystem is not mountable

Disk-3 Hardware

* ST3300831A, ATA DISK drive
* attached ide-disk driver.
* host protected area => 1
* 586072368 sectors (300069 MB) w/8192KiB Cache, CHS=36481/255/63, (U)DMA

NOTE: Disk-3 is installed and can be configured for use with NASLite+.

Obviously the disk and its data contents are no longer accessable at this time.

I have looked up smartctl at the Home page found at http://smartmontools.sourceforge.net/ and it would appear that the -P denotes a Preset=TYPE. It specifies whether smartctl should use any preset option that are available for this drive. By default, if the drive is recognized in the smartmontools database, then the presets are used.

Am I on the right track? How could I make this -p setting?

The drive is a brand new Seagate 7200.8 300GB drive, Model ST3300831A and my guess is that it is not yet defined to the smartctl database. Any suggestions would be welcomed, especially as I do not want to reconfigure the drive again and again when this occurs.

No takers on this one?

An IDE reset can be caused by a number of reasons. Here are some things that you may have already looked at, but it's a start:

- Make sure that the drive is properly set as a master or slave and not CS.
- Make sure the only thing on the same cable with the drive is a similar drive or nothing (No CD-ROM on that chain).
- Make sure the IDE cable is good and the connectors are well seated
- Try disabling APM and ACPI in the BIOS
- Make sure the power supply is good and does not fluctuate under load.

There can also be incompatibilities with the board/drive, etc - but I’d bet it’s most likely one of the above.