NASLite Network Attached Storage

Hi,

I just finished mounting all my old drives in my NL box and started backing up my files.

When I have a look in the syslog, I saw the following lines and I have several of them with different sector numbers...

Do I have to worry about something and/or do something to check the drive?

TIA


# Jun 24 12:23:38 user.warn kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
# Jun 24 12:23:38 user.warn kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3669408, sector=3653224
# Jun 24 12:23:38 user.warn kernel: end_request: I/O error, dev 16:01 (hdc), sector 3653224
# Jun 24 12:23:41 user.warn kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
# Jun 24 12:23:41 user.warn kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3669408, sector=3653232
# Jun 24 12:23:41 user.warn kernel: end_request: I/O error, dev 16:01 (hdc), sector 3653232
# Jun 24 12:23:44 user.warn kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
# Jun 24 12:23:44 user.warn kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3669408, sector=3653240

robrub:

Generally not a very healthy sign. Yes, you have potential data loss to worry about. What I have found, however, is it may not necessarily be the HDD, it could be the cabling and/or the motherboard's (or PCI) IDE controller. Many times (too many) I have been surprised recently where a new IDE cable fixed some issues similar to this. The "UncorrectableError" error however does point to the drive showing its age.

I would not trust any important data to these drives until you can eliminate these errors. Try to isolate the drive by itself with a new IDE cable on different IDE controllers (Primary/Secondary) and try writing data again. You can do a file system check (including scan for bad blocks). And/or run the manufacturer's (downloadable) diagnostic routines.

Georg

To add to the post from Georg, you can potentially get that error if you try to read or write to an area of the drive that is not usable. Doing a filesystem scan while checking for bad blocks may fix that problem since the bad areas will be marked and not used.

If the errors in the syslog are generated consistently every minute or so, then the problem is smart and can be corrected by disabling smart for that drive.