Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ominous ReiserFS messages

Featured Replies

I posted a few days ago re a problematic hard disk. The disk had sync errors after the server lost power during a lightning storm (although I believe all disks were spun down at the time) and I couldn't write to the server.

 

I've replaced it and unRaid did a rebuild (I'm on 4.4.2), but now I still can't write to the server. I keep on getting "I/O device error" in both Win7 and WinXP. At first I blamed Windows, but then I took a look at the syslog (attached) and saw a lot of worrying messages re disk 11, which is the new disk. Some of the lines are:

 

May  4 21:38:54 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [56750 56751 0x0 SD]

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-2180: finish_unfinished: iget failed for [56750 56751 0x0 SD]

 

and

 

May  4 21:42:03 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:42:03 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:42:03 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:42:03 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:04 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:04 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:04 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:04 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:35 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:35 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:35 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:35 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:44:15 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:44:15 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:44:15 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:44:15 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:08 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:08 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:08 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:08 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:46 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:46 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:46 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:46 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:47:06 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:47:06 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

 

Any suggestions? Should I run a parity check first and then try Fsck? Or something else?

syslog-2010-05-04.txt

I posted a few days ago re a problematic hard disk. The disk had sync errors after the server lost power during a lightning storm (although I believe all disks were spun down at the time) and I couldn't write to the server.

 

I've replaced it and unRaid did a rebuild (I'm on 4.4.2), but now I still can't write to the server. I keep on getting "I/O device error" in both Win7 and WinXP. At first I blamed Windows, but then I took a look at the syslog (attached) and saw a lot of worrying messages re disk 11, which is the new disk. Some of the lines are:

 

May  4 21:38:54 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [56750 56751 0x0 SD]

May  4 21:38:54 Tower kernel: ReiserFS: md11: warning: vs-2180: finish_unfinished: iget failed for [56750 56751 0x0 SD]

 

and

 

May  4 21:42:03 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:42:03 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:42:03 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:42:03 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:04 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:04 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:04 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:04 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:35 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:35 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:43:35 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:43:35 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:44:15 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:44:15 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:44:15 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:44:15 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:08 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:08 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:08 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:08 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:46 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:46 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:45:46 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:45:46 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

May  4 21:47:06 Tower kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 1

May  4 21:47:06 Tower kernel: ReiserFS: md11: warning: vs-5150: search_by_key: invalid format found in block 268828712. Fsck?

 

Any suggestions? Should I run a parity check first and then try Fsck? Or something else?

Parity check will not help, as odds are it is corrupted in exactly the same fashion.  It will certainly not fix anything.

 

You need to run a file-system check as described in the wiki : http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Joe L.

  • Author

Thanks, Joe. Ran the reiserfsck and now I'm happily writing to the server.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.