NASLite Network Attached Storage

Hi

One of the drives has gone offline

On requesting a check and repair drive I get

....

Warning illegal block 1073741824 found in bad block inode. Cleared.
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Group 32's block bitmap (1048576) is bad. Relocate? yes

Bad block 0 used as bad block indirect block?!?

This inconsistency can not be fixed with e2fsck; to fix it, use
dumpe2fs -b to dump out the bad block list and e2fsck -L filename
to read it back in again.
Continue? yes


and it just sits there

How do I follow the instructions outlined above on the NasLite machine?

Any ideas on how the problem occurred, what I can do to avoid it in the future and most importantly how do I get the drive back up with the data intact?

any ideas appreciated

Thanks

There are some portions of the drive that can make it useless when bad blocks develop in that area. Places like where the partition table goes for example can make for a bad day.

Sounds like you may have to boot a live CD like knoppix or something like that to do a more indepth analysis of the filesystem. Personally, I'd recommend that you mount the drive RO using knoppix and move the contents to another drive before messing with fixing things. When your data is safe, then you can reformat the drive in naslite followed by a complete check and repair with bad block checking enabled.

That should put you back in business, but I'd keep a close watch on that drive and make sure there are no seek errors showing in the syslog.

I have taken it out and I am letting SpinRite v6 have a go at it, see how that does.

At the moment it is predicting a fix within 533 hours

We shall see

But thanks for the response.

Just more incentive to get the backup NAS on line

Cheers

Mike