NASLite Network Attached Storage

So my disk 4 needs to have fsck without the -a or -p options run according the the boot screens... And yes I have a ton of data on that drive. Any ideas on how to fix this?


Mike

Was your Disk-4 originally formatted by NASLite?

Yes, I had NASLite configure the disk and check for bad blocks originally. The box has been up and running and since it's been running it's had a few issues causing it to dump wierd errors to the screen and lock the system up. Typically a reboot has been able to return it to normal operations after NASLite checked the disks. This time however it says there are inconsistancies in the drive and that I need to manually fsck. Now that disk is unavailable...
Here is what the web interface is reporting.

Disk-4 Initialization Messages

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

Disk-4 Hardware

* ST320413A, ATA DISK drive
* attached ide-disk driver.
* host protected area => 1
* 39102336 sectors (20020 MB) w/512KiB Cache, CHS=38792/16/63

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




Mike

Do you remember what the messages were? The filesystem corruption is obviously caused by a problem with your hardware, so it will more than likely happen again. When you get errors, refer to the syslog tab in the web interface and react accordingly. Rebooting isn't always the proper solution

Unfortunately, it isn't possible fo run e2fschk manually using NASLite, so i'd recommend taking the drive out and running e2fschk on another machine.

I'll think about how to provide a native solution for this problem in later releases. It may not be a bad idea.

Let me know how it goes.

I was hoping you had a virtual terminal setup in the F* keys, so I could get to a shell prompt for something like this. You pretty much answered my question, I was planning on putting the drive in another box and running fsck. Will let you know how it goes.


Mike

So i put the drive in another machine and it says it's not an ext2 filesystem, OR there is a bad superblock. It gives the optoin to specify another superblock IE e2fsck -b <block ID> <drive>. Any thoughts????? Or am I SOL with what was on that drive....

It's difficult to say what the extent of the damage may be. IDE is processor-driven, so hardware flaws can cause a havoc of not addressed.

Take a look at http://freshmeat.net/projects/e2retrieve/