NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon Dec 10, 2018 8:43 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: File system error
PostPosted: Wed Aug 26, 2009 7:24 pm 
Offline

Joined: Wed Aug 26, 2009 7:09 pm
Posts: 1
Two days ago I returned from vacation and restarted my NanoNAS server.
Today I realized that a big chunk of data was missing: I can access the drive, but an entire large folder is invisible from XP. However, disk usage statistics suggest that the data are still present.

OS version: v2.01 06-2008

Filesystem state: "clean with errors"

The Syslog includes numerous entries like:

"- Aug 24 04:24:50 [6] EXT3-fs error (device ide0(3,1)): ext3_get_inode_loc: unable to read inode block - inode=11337729, block=22675474"

The read-only filesystem check produces the following:

"e2fsck 1.27 (8-Mar-2002)
Warning! /dev/discs/disc0/part1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 142098 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 65545. Ignore error? no

Error while iterating over blocks in inode 65545: Attempt to read block from filesystem resulted in short read
Segmentation fault"

"Check and repair filesystem" is unavailable (*).

How to recover my data?

Thanks,

Lee


Top
 Profile  
 
 Post subject: Re: File system error
PostPosted: Thu Aug 27, 2009 5:52 pm 
Offline

Joined: Tue Aug 10, 2004 1:50 pm
Posts: 604
Location: Texas, USA
With errors like that, i'd be looking at my drive and drive connections.


Top
 Profile  
 
 Post subject: Re: File system error
PostPosted: Thu Aug 27, 2009 9:25 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1680
Location: Up State NY in the USA!!!!
How much memory is in the box and how large is the drive. If you are using a large drive with little memory in the PC a file system check will likely fail. Besides what dimension has said, very good advice, I would boot it from a live Linux CD or DVD and run an file system check on the offending drive. You may end up adding memory to the machine or moving the drive temporally to another machine with the requisite attributes to allow you to attempt a file system check and repair.

That said, if this works, get your data off of that drive and move it to a new drive or drives. You may also consider upgrading to the full blown version of NL2.x as it also supports a type of mirror scheme that will help to prevent this sort of issue in the future.

Mike


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group