NASLite Network Attached Storage

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

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 8 posts ] 
Author Message
PostPosted: Wed Dec 12, 2007 6:29 pm 
Offline

Joined: Sat Mar 03, 2007 9:01 pm
Posts: 12
I went to copy some files off my Naslite2 server and I couldn't. I couldn't get any files off the server. I checked the syslog and found a bunch of new entries (log is below). I also noticed under the drive details that Filesystem state says 'not clean with errors'.

NL has been working perfectly for me ever since I set it up almost 11 months ago. Hopefully these issues can easily be fixed, I don't want to lose the data.

How do I get this fixed? Let me know if I need to post any more info and I will asap.

# Dec 12 17:36:13 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=1940404498, rec_len=23979, name_len=17
# Dec 12 17:36:13 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379399: directory entry across blocks - offset=0, inode=3120627712, rec_len=29252, name_len=29
# Dec 12 17:41:12 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=1706053175, rec_len=26685, name_len=75
# Dec 12 17:46:15 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=3120627712, rec_len=52549, name_len=63
# Dec 12 17:51:05 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=272020002, rec_len=62529, name_len=81
# Dec 12 18:00:00 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:00 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:00 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:00 user.info kernel: 08:01: rw=0, want=1520829268, limit=586067265
# Dec 12 18:00:00 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:00 user.info kernel: 08:01: rw=0, want=1223726932, limit=586067265
# Dec 12 18:00:00 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:00 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:00 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:00 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:25 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:25 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:25 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:25 user.info kernel: 08:01: rw=0, want=1520829268, limit=586067265
# Dec 12 18:00:25 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:25 user.info kernel: 08:01: rw=0, want=1223726932, limit=586067265
# Dec 12 18:00:25 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:25 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:25 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:25 user.info kernel: 08:01: rw=0, want=1079022744, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=914996292, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=2107048228, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1194737636, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1591450516, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=2021130252, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=658112620, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=2088514484, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1539613088, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1433919716, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1912609988, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1732367108, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=701104932, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1561102552, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1161596472, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=2052855828, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1080245540, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1723557400, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=817285348, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=2051231876, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=1934173904, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:00:39 user.info kernel: attempt to access beyond end of device
# Dec 12 18:00:39 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:01:31 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:31 user.info kernel: 08:01: rw=0, want=844110364, limit=586067265
# Dec 12 18:01:31 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:31 user.info kernel: 08:01: rw=0, want=881366456, limit=586067265
# Dec 12 18:01:31 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:31 user.info kernel: 08:01: rw=0, want=1041279016, limit=586067265
# Dec 12 18:01:31 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:31 user.info kernel: 08:01: rw=0, want=844110364, limit=586067265
# Dec 12 18:01:31 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:31 user.info kernel: 08:01: rw=0, want=844110364, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=914996292, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=2107048228, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=1194737636, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=1591450516, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=2021130252, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=658112620, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=2088514484, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=1539613088, limit=586067265
# Dec 12 18:01:35 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:35 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=771844384, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1370281060, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=852525652, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1648991624, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1815370344, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1772127564, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=2015297636, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1489508376, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=2097179828, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1346301160, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1026461868, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1134957848, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1079184336, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1231397208, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1370281060, limit=586067265
# Dec 12 18:01:36 user.info kernel: attempt to access beyond end of device
# Dec 12 18:01:36 user.info kernel: 08:01: rw=0, want=1370281060, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1689345320, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1258319748, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=831238144, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=855672844, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1212063428, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1073773444, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1308422364, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1223378472, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1631987096, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1732895224, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=627893500, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1176517956, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=789658364, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=957904812, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=974431576, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1140690820, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1740063836, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1080034416, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1343541812, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=980708228, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1354893576, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1413231620, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=646598796, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1804275804, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1209991692, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=2020283176, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1192891292, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=2038965208, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1689345320, limit=586067265
# Dec 12 18:15:13 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:13 user.info kernel: 08:01: rw=0, want=1689345320, limit=586067265
# Dec 12 18:15:15 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:15 user.info kernel: 08:01: rw=0, want=1088784648, limit=586067265
# Dec 12 18:15:15 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:15 user.info kernel: 08:01: rw=0, want=1088784648, limit=586067265
# Dec 12 18:15:15 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:15 user.info kernel: 08:01: rw=0, want=1088784648, limit=586067265
# Dec 12 18:15:41 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:41 user.info kernel: 08:01: rw=0, want=2038965208, limit=586067265
# Dec 12 18:15:41 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:41 user.info kernel: 08:01: rw=0, want=1689345320, limit=586067265
# Dec 12 18:15:41 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:41 user.info kernel: 08:01: rw=0, want=1689345320, limit=586067265
# Dec 12 18:15:43 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:43 user.info kernel: 08:01: rw=0, want=1088784648, limit=586067265
# Dec 12 18:15:43 user.info kernel: attempt to access beyond end of device
# Dec 12 18:15:43 user.info kernel: 08:01: rw=0, want=1088784648, limit=586067265


Top
 Profile  
 
 Post subject:
PostPosted: Wed Dec 12, 2007 7:10 pm 
Offline

Joined: Sat Mar 03, 2007 9:01 pm
Posts: 12
I rebooted, it took NL a while before it was ready, but I can now access my files again.

Filesystem state is now saying 'not clean'

I looked over the syslog and saw 'EXT2-fs warning: checktime reached, running e2fsck is recommended'. Do I need to run e2fsck? If so how?

I also noticed this line 'user.notice kernel: 126MB LOWMEM available'
Does this mean I need more memory? I am running on a P3 667mhz, 128mb PC100, with 4x200GB RAID5 on an LSI Megaraid card.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Dec 13, 2007 11:55 am 
Offline

Joined: Sat Jun 02, 2007 2:45 am
Posts: 485
Location: France
Hi Oats,

Don't worry about Filesystem state is now saying 'not clean' This is just a flag set when NL starts running and is "cleared" when NL shuts down normally. If you have a problem and NL doesn't close normally (cleanly ;) ) then this flag stays "on" and at next boot, NL sees the flag and does a "check disk". This is just for max security.

As for 'user.notice kernel: 126MB LOWMEM available', 128 is a bit low on the memory side (especially if you have big disks (and you do!) and many files. In another post, I recall Tony speaking of 256Mb being better. I'd say, if you add mem, add the max you can. It always speeds up things as NL uses memory for "aggressive" caching.

And the answer where I'm not so sure concerns 'EXT2-fs warning: checktime reached, running e2fsck is recommended'.. Normally, every x mounts (boots), NL does a disk check. You can see the actual number and the max on the disk status pages. If a disk check is needed, NL will do it automatically. Maybe some will give you a fuller answer.

Regards.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 14, 2007 12:41 am 
Offline

Joined: Sat Mar 03, 2007 9:01 pm
Posts: 12
robrub wrote:
Hi Oats,

Don't worry about Filesystem state is now saying 'not clean' This is just a flag set when NL starts running and is "cleared" when NL shuts down normally. If you have a problem and NL doesn't close normally (cleanly ;) ) then this flag stays "on" and at next boot, NL sees the flag and does a "check disk". This is just for max security.

As for 'user.notice kernel: 126MB LOWMEM available', 128 is a bit low on the memory side (especially if you have big disks (and you do!) and many files. In another post, I recall Tony speaking of 256Mb being better. I'd say, if you add mem, add the max you can. It always speeds up things as NL uses memory for "aggressive" caching.

And the answer where I'm not so sure concerns 'EXT2-fs warning: checktime reached, running e2fsck is recommended'.. Normally, every x mounts (boots), NL does a disk check. You can see the actual number and the max on the disk status pages. If a disk check is needed, NL will do it automatically. Maybe some will give you a fuller answer.

Regards.


I read about that not clean thing after posting. If I continue to use naslite I will pick up some more ram, I might be building a server, if I do I will end up just putting moving the raid array to it.

I don't reboot the server, before yesterday it hadn't been powered off in over 4 months. I'll do some searching for e2fsck and see what I find.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 14, 2007 2:18 am 
Offline

Joined: Sat Mar 03, 2007 9:01 pm
Posts: 12
Well I thought it was working again, but I was wrong. I can read files off it fine, but I can't write files. The files appear to copy over fine but they don't, if I open a picture it only has the top few lines of the pic and the rest is blank. So I can't write files to disk.

Here are the new syslog details:

# ec 12 18:52:33 syslog.info syslogd started: BusyBox v1.01 (2007.01.20-18:39+0000)
# Dec 12 18:52:33 daemon.info init: ^MStarting pid 2005, console /dev/null: '/sbin/klogd'
# Dec 12 18:52:33 user.notice kernel: klogd started: BusyBox v1.01 (2007.01.20-18:39+0000)
# Dec 12 18:52:33 user.warn kernel: Linux version 2.4.33.NASLite (root@TZT) (gcc version 3.3.6) #1 Tue Aug 15 01:08:13 UTC 2006
# Dec 12 18:52:33 user.info kernel: BIOS-provided physical RAM map:
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 00000000000e8800 - 0000000000100000 (reserved)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 0000000000100000 - 0000000007ef0000 (usable)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 0000000007ef0000 - 0000000007effc00 (ACPI data)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 0000000007effc00 - 0000000007f00000 (ACPI NVS)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 0000000007f00000 - 0000000008000000 (reserved)
# Dec 12 18:52:33 user.warn kernel: BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
# Dec 12 18:52:33 user.notice kernel: 126MB LOWMEM available.
# Dec 12 18:52:33 user.warn kernel: On node 0 totalpages: 32496
# Dec 12 18:52:33 user.warn kernel: zone(0): 4096 pages.
# Dec 12 18:52:33 user.warn kernel: zone(1): 28400 pages.
# Dec 12 18:52:33 user.warn kernel: zone(2): 0 pages.
# Dec 12 18:52:33 user.info kernel: DMI not present.
# Dec 12 18:52:33 user.info kernel: ACPI: RSDP (v000 PTLTD ) @ 0x000f76a0
# Dec 12 18:52:33 user.info kernel: ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x07efce7f
# Dec 12 18:52:33 user.info kernel: ACPI: FADT (v001 HP Hawk 0x06040000 PTL 0x000f4240) @ 0x07effb65
# Dec 12 18:52:33 user.info kernel: ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x07effbd9
# Dec 12 18:52:33 user.info kernel: ACPI: DSDT (v001 INTEL Whitney 0x06040000 MSFT 0x01000007) @ 0x00000000
# Dec 12 18:52:33 user.warn kernel: Kernel command line: root=/dev/ram0 rw
# Dec 12 18:52:33 user.info kernel: Initializing CPU#0
# Dec 12 18:52:33 user.warn kernel: Detected 669.526 MHz processor.
# Dec 12 18:52:33 user.warn kernel: Console: colour VGA+ 80x25
# Dec 12 18:52:33 user.warn kernel: Calibrating delay loop. 1336.93 BogoMIPS
# Dec 12 18:52:33 user.info kernel: Memory: 122848k/129984k available (2198k kernel code, 6748k reserved, 734k data, 536k init, 0k highmem)
# Dec 12 18:52:33 user.info kernel: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
# Dec 12 18:52:33 user.info kernel: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
# Dec 12 18:52:33 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
# Dec 12 18:52:33 user.info kernel: Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
# Dec 12 18:52:33 user.warn kernel: Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
# Dec 12 18:52:33 user.info kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
# Dec 12 18:52:33 user.info kernel: CPU: L2 cache: 256K
# Dec 12 18:52:33 user.debug kernel: CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
# Dec 12 18:52:33 user.debug kernel: CPU: Common caps: 0383f9ff 00000000 00000000 00000000
# Dec 12 18:52:33 user.warn kernel: CPU: Intel Pentium III (Coppermine) stepping 03
# Dec 12 18:52:33 user.info kernel: Enabling fast FPU save and restore. done.
# Dec 12 18:52:33 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
# Dec 12 18:52:33 user.info kernel: Checking 'hlt' instruction. OK.
# Dec 12 18:52:33 user.info kernel: Checking for popad bug. OK.
# Dec 12 18:52:33 user.warn kernel: ACPI: IRQ9 SCI: Level Trigger.
# Dec 12 18:52:33 user.warn kernel: POSIX conformance testing by UNIFIX
# Dec 12 18:52:33 user.info kernel: ACPI: Subsystem revision 20040326
# Dec 12 18:52:33 user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd99e, last bus=1
# Dec 12 18:52:33 user.info kernel: PCI: Using configuration type 1
# Dec 12 18:52:33 user.info kernel: ACPI: Interpreter enabled
# Dec 12 18:52:33 user.info kernel: ACPI: Using PIC for interrupt routing
# Dec 12 18:52:33 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S5)
# Dec 12 18:52:33 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
# Dec 12 18:52:33 user.warn kernel: PCI: Probing PCI hardware (bus 00)
# Dec 12 18:52:33 user.warn kernel: Transparent bridge - PCI device 8086:2418
# Dec 12 18:52:33 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 14 15)
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 14 15)
# Dec 12 18:52:33 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SLOT._PRT]
# Dec 12 18:52:33 user.info kernel: PCI: Probing PCI hardware
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
# Dec 12 18:52:33 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
# Dec 12 18:52:33 user.info kernel: PCI: Using ACPI for IRQ routing
# Dec 12 18:52:33 user.info kernel: Linux NET4.0 for Linux 2.4
# Dec 12 18:52:33 user.info kernel: Based upon Swansea University Computer Society NET3.039
# Dec 12 18:52:33 user.warn kernel: Initializing RT netlink socket
# Dec 12 18:52:33 user.warn kernel: Starting kswapd
# Dec 12 18:52:33 user.info kernel: Journalled Block Device driver loaded
# Dec 12 18:52:33 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
# Dec 12 18:52:33 user.info kernel: devfs: boot_options: 0x1
# Dec 12 18:52:33 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
# Dec 12 18:52:33 user.info kernel: ACPI: Power Button (FF) [PWRF]
# Dec 12 18:52:33 user.info kernel: ACPI: Processor [CPU0] (supports C1)
# Dec 12 18:52:33 user.warn kernel: pty: 256 Unix98 ptys configured
# Dec 12 18:52:33 user.info kernel: Real Time Clock Driver v1.10f
# Dec 12 18:52:33 user.info kernel: Floppy drive(s): fd0 is 1.44M
# Dec 12 18:52:33 user.warn kernel: keyboard: Timeout - AT keyboard not present?(ed)
# Dec 12 18:52:33 user.warn kernel: keyboard: Timeout - AT keyboard not present?(f4)
# Dec 12 18:52:33 user.info kernel: FDC 0 is a post-1991 82077
# Dec 12 18:52:33 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
# Dec 12 18:52:33 user.info kernel: loop: loaded (max 8 devices)
# Dec 12 18:52:33 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
# Dec 12 18:52:33 user.info kernel:
# Dec 12 18:52:33 user.info kernel: dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96 03:45:15
# Dec 12 18:52:33 user.warn kernel: FW Version=$Version$
# Dec 12 18:52:33 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
# Dec 12 18:52:33 user.info kernel: ThunderLAN driver v1.15
# Dec 12 18:52:33 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
# Dec 12 18:52:33 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
# Dec 12 18:52:33 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
# Dec 12 18:52:33 user.warn kernel: sk98lin: No adapter found.
# Dec 12 18:52:33 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
# Dec 12 18:52:33 user.info kernel: r8169 Gigabit Ethernet driver 1.2 loaded
# Dec 12 18:52:33 user.debug kernel: eth0: Identified chip type is 'RTL8169s/8110s'.
# Dec 12 18:52:33 user.info kernel: eth0: RTL8169 at 0xc8807000, 00:18:4d:79:77:d4, IRQ 9
# Dec 12 18:52:33 user.info kernel: eth0: Auto-negotiation Enabled.
# Dec 12 18:52:33 user.info kernel: eth0: 1000Mbps Full-duplex operation.
# Dec 12 18:52:33 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
# Dec 12 18:52:33 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
# Dec 12 18:52:33 user.info kernel: ICH: IDE controller at PCI slot 00:1f.1
# Dec 12 18:52:33 user.info kernel: ICH: chipset revision 2
# Dec 12 18:52:33 user.info kernel: ICH: not 100% native mode: will probe irqs later
# Dec 12 18:52:33 user.info kernel: ide0: BM-DMA at 0x10a0-0x10a7, BIOS settings: hda:pio, hdb:pio
# Dec 12 18:52:33 user.info kernel: ide1: BM-DMA at 0x10a8-0x10af, BIOS settings: hdc:pio, hdd:pio
# Dec 12 18:52:33 user.info kernel: SCSI subsystem driver Revision: 1.00
# Dec 12 18:52:33 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
# Dec 12 18:52:33 user.info kernel: Detecting Adaptec I2O RAID controllers.
# Dec 12 18:52:33 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 15 2006 01:22:52)
# Dec 12 18:52:33 user.warn kernel: scsi: Detection failed (no card)
# Dec 12 18:52:33 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
# Dec 12 18:52:33 user.notice kernel: megaraid: found 0x101e:0x1960:bus 1:slot 11:func 0
# Dec 12 18:52:33 user.notice kernel: scsi1:Found MegaRAID controller at 0xc8809000, IRQ:11
# Dec 12 18:52:33 user.notice kernel: megaraid: [N661:1.01] detected 1 logical drives.
# Dec 12 18:52:33 user.notice kernel: megaraid: supports extended CDBs.
# Dec 12 18:52:33 user.info kernel: megaraid: channel[0] is raid.
# Dec 12 18:52:33 user.info kernel: megaraid: channel[1] is raid.
# Dec 12 18:52:33 user.info kernel: megaraid: channel[2] is raid.
# Dec 12 18:52:33 user.info kernel: megaraid: channel[3] is raid.
# Dec 12 18:52:33 user.info kernel: scsi1 : LSI Logic MegaRAID N661 254 commands 16 targs 7 chans 7 luns
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 0 for logical drives.
# Dec 12 18:52:33 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 572G Rev: N661
# Dec 12 18:52:33 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 1 for logical drives.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 2 for logical drives.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 3 for logical drives.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 4 [P0] for physical devices.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 5 [P1] for physical devices.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 6 [P2] for physical devices.
# Dec 12 18:52:33 user.notice kernel: scsi1: scanning scsi channel 7 [P3] for physical devices.
# Dec 12 18:52:33 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
# Dec 12 18:52:33 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
# Dec 12 18:52:33 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
# Dec 12 18:52:33 user.warn kernel: 3w-xxxx: No cards found.
# Dec 12 18:52:33 user.debug kernel: libata version 1.20 loaded.
# Dec 12 18:52:33 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
# Dec 12 18:52:33 user.warn kernel: SCSI device sda: 1172152320 512-byte hdwr sectors (600142 MB)
# Dec 12 18:52:33 user.info kernel: Partition check:
# Dec 12 18:52:33 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
# Dec 12 18:52:33 user.info kernel: raw1394: /dev/raw1394 device initialized
# Dec 12 18:52:33 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
# Dec 12 18:52:33 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
# Dec 12 18:52:33 user.info kernel: usb.c: registered new driver usbdevfs
# Dec 12 18:52:33 user.info kernel: usb.c: registered new driver hub
# Dec 12 18:52:33 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
# Dec 12 18:52:33 user.debug kernel: PCI: Setting latency timer of device 00:1f.2 to 64
# Dec 12 18:52:33 user.info kernel: host/uhci.c: USB UHCI at I/O 0x1080, IRQ 11
# Dec 12 18:52:33 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
# Dec 12 18:52:33 user.info kernel: hub.c: USB hub found
# Dec 12 18:52:33 user.info kernel: hub.c: 2 ports detected
# Dec 12 18:52:33 user.info kernel: Initializing USB Mass Storage driver.
# Dec 12 18:52:33 user.info kernel: usb.c: registered new driver usb-storage
# Dec 12 18:52:33 user.info kernel: USB Mass Storage support registered.
# Dec 12 18:52:33 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
# Dec 12 18:52:33 user.info kernel: IP Protocols: ICMP, UDP, TCP
# Dec 12 18:52:33 user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
# Dec 12 18:52:33 user.info kernel: TCP: Hash tables configured (established 8192 bind 16384)
# Dec 12 18:52:33 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
# Dec 12 18:52:33 user.notice kernel: RAMDISK: NASLite file system found at block 0
# Dec 12 18:52:33 user.warn kernel: .<6>hub.c: new USB device 00:1f.2-2, assigned address 2
# Dec 12 18:52:33 user.warn kernel: r USB Mass Storage devices
# Dec 12 18:52:33 user.warn kernel: Vendor: Kingston Model: DataTraveler 2.0 Rev: 4.10
# Dec 12 18:52:33 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
# Dec 12 18:52:33 user.warn kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
# Dec 12 18:52:33 user.warn kernel: .SCSI device sdb: 251904 512-byte hdwr sectors (129 MB)
# Dec 12 18:52:33 user.warn kernel: sdb: Write Protect is off
# Dec 12 18:52:33 user.info kernel: /dev/scsi/host2/bus0/target0/lun0: unknown partition table
# Dec 12 18:52:33 user.debug kernel: WARNING: USB Mass Storage data integrity not assured
# Dec 12 18:52:33 user.debug kernel: USB Mass Storage device found at 2
# Dec 12 18:52:33 user.warn kernel: <6>Freeing initrd memory: 1619k freed
# Dec 12 18:52:33 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
# Dec 12 18:52:33 user.warn kernel: VFS: Mounted root (ext2 filesystem).
# Dec 12 18:52:33 user.info kernel: Mounted devfs on /dev
# Dec 12 18:52:33 user.info kernel: Freeing unused kernel memory: 536k freed
# Dec 12 18:52:33 user.err kernel: ext3: No journal on filesystem on sd(8,1)
# Dec 12 19:05:44 auth.info login[11109]: root login on `pts/0'
# Dec 13 18:51:22 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=1637137504, rec_len=42805, name_len=153
# Dec 13 20:11:22 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
# Dec 13 20:16:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=2349559660, rec_len=33494, name_len=158
# Dec 13 20:21:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=1021354054, rec_len=2082, name_len=43
# Dec 13 20:26:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: directory entry across blocks - offset=0, inode=634460303, rec_len=15008, name_len=152
# Dec 13 20:31:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: directory entry across blocks - offset=0, inode=3111508871, rec_len=23496, name_len=129
# Dec 13 20:36:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #24379398: unaligned directory entry - offset=0, inode=884386813, rec_len=24985, name_len=198
# Dec 13 23:36:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #31686660: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
# Dec 13 23:36:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #31686662: unaligned directory entry - offset=0, inode=4158129392, rec_len=1962, name_len=54
# Dec 13 23:36:17 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #31817734: unaligned directory entry - offset=0, inode=2786657414, rec_len=22731, name_len=130
# Dec 13 23:36:18 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #32292869: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
# Dec 13 23:36:19 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #7258114: unaligned directory entry - offset=0, inode=2730007290, rec_len=56493, name_len=124
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=2074901428, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=2073709652, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1319881240, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=731668668, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1537715892, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1415993744, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1241526844, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1473763172, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=637896172, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1691038764, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=909129312, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1061033224, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1238545920, limit=586067265
# Dec 13 23:36:25 user.info kernel: attempt to access beyond end of device
# Dec 13 23:36:25 user.info kernel: 08:01: rw=0, want=1204646252, limit=586067265
# Dec 13 23:36:25 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_check_page: bad entry in directory #7946241: rec_len is smaller than minimal - offset=724, inode=7946277, rec_len=0, name_len=0
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1673513166, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1816795768, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2120852996, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3926595651, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4023225516, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2707727987, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1995396055, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4088176103, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2862262854, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4051285811, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4192524878, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1639577771, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3235328538, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1386096436, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3064692026, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1804560028, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2373599041, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3706279573, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 171892688, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3370341999, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3662224909, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3795307615, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1211649637, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2277580718, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 866583062, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4181235705, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1922777629, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4206256093, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1389273032, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 266328598, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2708804109, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1418605792, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3036922195, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3005008258, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3961006366, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1009582171, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3147660706, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 367278948, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2752471575, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1428647127, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1111850513, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 635427849, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 942614359, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 379330998, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 968929008, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 186893039, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3679746300, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1267140764, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3368888446, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1130712531, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3284934184, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3870641952, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2226317120, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2044355006, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 925120296, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2027623630, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 426086267, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 610169860, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4036081418, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2635478609, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2670206581, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 1607675299, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3667991829, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3659818253, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 797929883, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 3233258978, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 2860731098, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 4168622125, count = 1
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 721441384, count = 1
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835101
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835102
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835103
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835104


This is no good, now I have actually lost some files that I moved to the NL box.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 14, 2007 4:30 am 
Offline

Joined: Sat Jun 02, 2007 2:45 am
Posts: 485
Location: France
Oats wrote:
# Dec 13 23:36:43 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: Freeing blocks not in datazone - block = 721441384, count = 1
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835101
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835102
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835103
# Dec 13 23:36:45 user.crit kernel: EXT2-fs error (device sd(8,1)): ext2_free_blocks: bit already cleared for block 7835104


This is no good, now I have actually lost some files that I moved to the NL box.


Hi Oats,

Don't be pessimistic yet ;) You unmount the drives in NL admin (Set to -- the export disk status: menu 3 then disk number, then option 1)). Reboot the NL box. Then go to the Storage config menu, and for each drive do a 6: Check and repair disk-? file system. You may do this several times if one pass didn't clean all the problems.

This usually puts the disks back in shape and corrects the fs (file system) errors.

Once finished, don't forget to put the disk export to RW (rear/write) and reboot.

I hope this helps.

Regards


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 14, 2007 11:58 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Hello Oats,

Let me make some assumptions first: The errors occur on a RAID that you are driving with a megaraid card. If that is the case, then rebooting alone may not be the best way of handling the problem. The first thing that is necessary is to ensure the hardware is in fact operating properly before expecting the software to successfully fix filesystem problems.

I'd suggest you start by first ensuring the system power supply is sufficient for the drives and they all spin properly. Most critical time is at startup. Continue by ensuring the card, drives, each cable and all of the associated connections are good by reseating all connectors and possibly switching or replacing cables. Run the associated OEM diag utility to make sure the card and the RAID are healthy and working as necessary.

Once you verify that all the hardware is running as it should, then you can proceed to filesystem repairs on the software level.

Keep in mind that NASLite does not change nor does it use stale hardware status data from previous boots as you may find with "installed" operating systems. Each boot of NASLite results in a complete and clean hardware rendering equivalent to the very first boot. In that respect, the behavior you can expect from NASlite is consistent and predictable.

I think the problem is related to hardware deficiencies so until all of that checks out, i'd be careful and probably not run any software based filesystem management utilities. On boot, NASLite is not aggressive with filesystem repairs. It will check agressively, but make only minor repairs, the heavy work however is done by the admin Check and Repair option manually. That should be avoided if the hardware is suspect.

Anyway, there is a good chance your files are ok, but first I'd be sure to check the hardware.

Hope that helps...


Top
 Profile  
 
 Post subject:
PostPosted: Mon Dec 17, 2007 1:45 am 
Offline

Joined: Sat Mar 03, 2007 9:01 pm
Posts: 12
Everything appears to be working again after running a disk check from the megaraid bios and the naslite check and repair.

Thanks for you help guys.


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 17 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