NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon May 05, 2025 9:05 am

View unanswered posts | View active topics


Board index » v2.x NASLite Products » NASLite-2

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 2
  [ 20 posts ]  Go to page 1, 2  Next
  Previous topic | Next topic 
Author Message
t_indra
PostPosted: Thu Aug 10, 2006 5:19 pm 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
Hi,
one of my drives reports the filesystem state as "not clean" (in the sever status pages). I have tried reformatting it, I have run the extended SMART test, and have done the check and repair.
7 other disks (of similar or equal brand and build) are reporting "clean" in NL-2.
What do I need to do about this message and how can this be fixed?
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Thu Aug 10, 2006 8:33 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
If you deleate the "lost+found" foldet, the fs state will be set to "not clean". If that is the case, then t's not a reason for worry sunce the folder will be recreated next scheduled check.

ext2/3 requires the "lost+found" folder to be in place for a clean filesystem.
Top
 Profile  
 
t_indra
 Post subject:
PostPosted: Fri Aug 11, 2006 4:11 am 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
Tony wrote:
If you deleate the "lost+found" foldet, the fs state will be set to "not clean".


Tony, I have a lost+found folder, and have never deleted it either (since I can't even access it, from a Windows network (not the right permissions/ access denied).
As mentioned even after reformatting the fs still reports as not clean.
Any other ideas?
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Fri Aug 11, 2006 9:09 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Can you post the "Filesystem Details:" from the "Server Storage Disk-N" page?

Another thing you can try is to park the drive (Opt-1) in the "Disk-N Configuration Menu" and reboot. Disk-N should not be mounted at this time and "Check and Repair Disk-N Filesystem" (Opt-6) should now be available. Use it to fix the filesystem. If all goes well, reset the drive back to (RW) (Opt-1) and reboot to remount. Check the Status page again to verify.

Hope that helps...
Top
 Profile  
 
t_indra
 Post subject:
PostPosted: Fri Aug 11, 2006 9:16 am 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
Hi Tony, here they are.
I have tried the procedure you described in the past, but that did not seem to make a change. I will try it again, once my server is not tied up anymore.

Code:
Filesystem Details:

    tune2fs 1.27 (8-Mar-2002)
Filesystem volume name:   NASLite-SE000131
Last mounted on:         
Filesystem UUID:          ec1a2db8-6f4d-4b79-87f6-8270f3407395
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      filetype sparse_super
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              30539776
Block count:              61049008
Reserved block count:     0
Free blocks:              60061193
Free inodes:              30539738
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Last mount time:          Thu Aug 10 14:40:28 2006
Last write time:          Thu Aug 10 21:06:53 2006
Mount count:              2
Maximum mount count:      29
Last checked:             Thu Aug 10 07:54:27 2006
Check interval:           15552000 (6 months)
Next check after:         Tue Feb  6 07:54:27 2007
Reserved blocks uid:      0 (user admin)
Reserved blocks gid:      0 (group admin)
First inode:              11
Inode size:        128
 
Top
 Profile  
 
jmt77
 Post subject:
PostPosted: Sun Aug 13, 2006 11:07 am 
Offline

Joined: Sun Aug 13, 2006 3:20 am
Posts: 1
I just setup my NASLite 2 box last night. If I look at my filesystem details page, I too see my Filesystem state as "not clean" (shows this for both of the 2 hard drives in the box).

These are both identical, brand new drives and were just formatted last night. I checked and do have a "Lost+Found" folder. I also ran the "Check and Repair Disk-N Filesystem (Option 6)" which did not help.

Does anyone have any thoughts as to why the filesystem is showing as "not clean"?

Thanks.
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Mon Aug 14, 2006 11:51 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Apply a journal to the filesystem...
Top
 Profile  
 
t_indra
 Post subject:
PostPosted: Tue Aug 15, 2006 9:00 am 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
Tony wrote:
Another thing you can try is to park the drive (Opt-1) in the "Disk-N Configuration Menu" and reboot. Disk-N should not be mounted at this time and "Check and Repair Disk-N Filesystem" (Opt-6) should now be available. Use it to fix the filesystem. If all goes well, reset the drive back to (RW) (Opt-1) and reboot to remount. Check the Status page again to verify.


Hi Tony,
I have now reformatted the drive, then ran the SMART check, then even ran the check and repair option - but the Filesystem state remains: not clean.

Another odd thing is, that this drive (as well as some others) does not have "has_journal" listed under FS features. But when I format the drive with NL-2, a journal is/ should be automatically applied, if I remember correctly.

Any other ideas? Is this something to be concerned with? Could corruption be a result of such state?
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Tue Aug 15, 2006 10:07 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
By default NASLite-2 formats as Ext2 and not Ext3. In order to apply a journal, you need to use the Apply Journal to Disk-N Filesystem (Option 7) in the Disk-N Configuration Menu screen.

Try applying the journal and see if the filesystem “cleans up” ;-)

I don’t think you have to worry about it much, but I think we’ll both feel better if all was proper and the filesystem reported clean.

Let me know if applying the journal does the trick.

I’ll play on my end and see if I can replicate the problem. Haven’t noticed that before...
Top
 Profile  
 
t_indra
 Post subject:
PostPosted: Wed Aug 16, 2006 10:23 am 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
Ok, a case of human error, I suppose. Once the journal was applied, the error message went away ;-).
I must have overlooked journaling this drive - have been dealing with some 16 drives altogether lately, and loads of system changes...

But one odd thing remains:
Code:
Filesystem features:      has_journal filetype needs_recovery sparse_super
Filesystem state:         clean


What does "needs_recovery" mean? Should I run the check and repair option?
And what does "sparse" mean - I have also seen that as some switch for the rsync command.
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Wed Aug 16, 2006 11:03 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
The explanations are as follows:

needs_recovery :arrow: That flag is always set when the file system is mounted. When cleanly unmounted, the flag is unset. If the unmount is not clean and the flag is not unset, then on reboot the file system will be checked automatically. With has_journal, the check is much faster than an ext2 check.

sparse_super :arrow: This flag indicates that the file system will keep fewer superblock backup copies. With large file systems, that approach saves considerable amount of space. Since the storage drives in NASLite are strictly data, then the sparse_super flag is most appropriate.

Hope that helps ;-)
Top
 Profile  
 
t_indra
 Post subject:
PostPosted: Wed Aug 16, 2006 5:37 pm 
Offline

Joined: Tue Sep 14, 2004 11:18 am
Posts: 70
Location: Giessen, Germany
That does help, thanks very much. And thanks for keeping the forum very well moderated! :D
Top
 Profile  
 
georg
 Post subject:
PostPosted: Mon Nov 26, 2007 5:13 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Ok ... so I understand the "needs_recovery" flag. But how about if the disk does NOT have a journal ? Is it normal to see the following (NOTE: I have this on two disks that were formatted without a journal and BOTH are MIRRORs of disks from a system with all journaled disks, and both disks have a "lost+found" folder (as do the source disks for the MIRROR) ):

Filesystem features: filetype sparse_super large_file
Filesystem state: not clean

T.I.A.

:) Georg
Top
 Profile  
 
Tony
 Post subject:
PostPosted: Wed Nov 28, 2007 10:20 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
I'd apply a journal to both, but with that aside, when the filesystem is live it's always unclean. When it's properly unmounted, then the flag is set to clean, That way, if the system crashes, the unclean flag will force a check at boot.
Top
 Profile  
 
georg
 Post subject:
PostPosted: Wed Nov 28, 2007 10:36 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Thanks, Tony. Your explanation is how I had understood the "needs_recovery" flag. It's just strange that -- as a mirror -- the copy (without the journal) shows this behaviour, in contrast to the source disk. But I'll go ahead and apply a journal to the destination disk.
:) Georg
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 2
  [ 20 posts ]  Go to page 1, 2  Next

Board index » v2.x NASLite Products » NASLite-2

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 5 guests

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