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.

ReiserFS Rebuild Help...

Featured Replies

Hi,

 

I recently upgraded the motherboard and CPU in my system and added a 2-port SATA PCIe card. When I restarted my system, 2 of my disks show up as unformatted (data disks). I ran reiserfs on one of the disks and it suggested a rebuild. Prior to going through with that, I am coming here for some assistance. Just want to make sure I am exhausting all my options before I have to lose data.

 

Below is an excerpt from my syslog during bootup:

 

Nov 12 09:53:43 Tower emhttp: Mounting disks...

Nov 12 09:53:43 Tower emhttp: shcmd (24): mkdir /mnt/disk1

Nov 12 09:53:43 Tower emhttp: shcmd (25): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger

Nov 12 09:53:43 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md1,

Nov 12 09:53:43 Tower logger:        missing codepage or helper program, or other error

Nov 12 09:53:43 Tower logger:        In some cases useful info is found in syslog - try

Nov 12 09:53:43 Tower logger:        dmesg | tail  or so

Nov 12 09:53:43 Tower logger:

Nov 12 09:53:43 Tower emhttp: _shcmd: shcmd (25): exit status: 32

Nov 12 09:53:43 Tower emhttp: disk1 mount error: 32

Nov 12 09:53:43 Tower emhttp: shcmd (26): rmdir /mnt/disk1

Nov 12 09:53:43 Tower emhttp: shcmd (27): mkdir /mnt/disk2

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md1): sh-2006 read_super_block: bread failed (dev md1, block 2, size 4096)

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md1): sh-2006 read_super_block: bread failed (dev md1, block 16, size 4096)

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md1): sh-2021 reiserfs_fill_super: can not find reiserfs on md1

Nov 12 09:53:43 Tower emhttp: shcmd (28): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

Nov 12 09:53:43 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Nov 12 09:53:43 Tower kernel: REISERFS (device md2): using ordered data mode

Nov 12 09:53:43 Tower kernel: reiserfs: using flush barriers

Nov 12 09:53:43 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Nov 12 09:53:43 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Nov 12 09:53:43 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Nov 12 09:53:43 Tower emhttp: shcmd (29): mkdir /mnt/disk3

Nov 12 09:53:43 Tower emhttp: shcmd (30): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Nov 12 09:53:43 Tower avahi-daemon[3581]: Server startup complete. Host name is Tower.local. Local service cookie is 588585268.

Nov 12 09:53:43 Tower avahi-dnsconfd[3592]: New DNS Server 10.0.1.1 (interface: 2.IPv4)

Nov 12 09:53:43 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Nov 12 09:53:43 Tower kernel: REISERFS (device md3): using ordered data mode

Nov 12 09:53:43 Tower kernel: reiserfs: using flush barriers

Nov 12 09:53:43 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Nov 12 09:53:43 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Nov 12 09:53:43 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

Nov 12 09:53:43 Tower emhttp: shcmd (31): mkdir /mnt/disk4

Nov 12 09:53:43 Tower emhttp: shcmd (32): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 |& logger

Nov 12 09:53:43 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

Nov 12 09:53:43 Tower kernel: REISERFS (device md4): using ordered data mode

Nov 12 09:53:43 Tower kernel: reiserfs: using flush barriers

Nov 12 09:53:43 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Nov 12 09:53:43 Tower kernel: REISERFS (device md4): checking transaction log (md4)

Nov 12 09:53:43 Tower kernel: REISERFS (device md4): Using r5 hash to sort names

Nov 12 09:53:43 Tower emhttp: shcmd (33): mkdir /mnt/disk5

Nov 12 09:53:43 Tower emhttp: shcmd (34): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger

Nov 12 09:53:43 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5,

Nov 12 09:53:43 Tower logger:        missing codepage or helper program, or other error

Nov 12 09:53:43 Tower logger:        In some cases useful info is found in syslog - try

Nov 12 09:53:43 Tower logger:        dmesg | tail  or so

Nov 12 09:53:43 Tower logger:

Nov 12 09:53:43 Tower emhttp: _shcmd: shcmd (34): exit status: 32

Nov 12 09:53:43 Tower emhttp: disk5 mount error: 32

Nov 12 09:53:43 Tower emhttp: shcmd (35): rmdir /mnt/disk5

Nov 12 09:53:43 Tower emhttp: shcmd (36): mkdir /mnt/disk6

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md5): sh-2006 read_super_block: bread failed (dev md5, block 2, size 4096)

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md5): sh-2006 read_super_block: bread failed (dev md5, block 16, size 4096)

Nov 12 09:53:43 Tower kernel: REISERFS warning (device md5): sh-2021 reiserfs_fill_super: can not find reiserfs on md5

Nov 12 09:53:43 Tower emhttp: shcmd (37): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md6 /mnt/disk6 |& logger

Nov 12 09:53:43 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal

Nov 12 09:53:43 Tower kernel: REISERFS (device md6): using ordered data mode

Nov 12 09:53:43 Tower kernel: reiserfs: using flush barriers

Nov 12 09:53:43 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Nov 12 09:53:43 Tower kernel: REISERFS (device md6): checking transaction log (md6)

Nov 12 09:53:43 Tower kernel: REISERFS (device md6): Using r5 hash to sort names

Nov 12 09:53:43 Tower emhttp: shcmd (38): mkdir /mnt/cache

Nov 12 09:53:43 Tower emhttp: shcmd (39): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/sdd1 /mnt/cache |& logger

Nov 12 09:53:43 Tower kernel: REISERFS (device sdd1): found reiserfs format "3.6" with standard journal

Nov 12 09:53:43 Tower kernel: REISERFS (device sdd1): using ordered data mode

Nov 12 09:53:43 Tower kernel: reiserfs: using flush barriers

Nov 12 09:53:43 Tower kernel: REISERFS (device sdd1): journal params: device sdd1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Nov 12 09:53:43 Tower kernel: REISERFS (device sdd1): checking transaction log (sdd1)

Nov 12 09:53:43 Tower kernel: REISERFS (device sdd1): Using r5 hash to sort names

Nov 12 09:53:43 Tower avahi-daemon[3581]: Service "Tower" (/services/smb.service) successfully established.

Nov 12 09:53:43 Tower avahi-daemon[3581]: Service "Tower-AFP" (/services/afp.service) successfully established.

Nov 12 09:53:44 Tower emhttp: shcmd (40): mkdir /mnt/user0

Nov 12 09:53:44 Tower emhttp: shcmd (41): /usr/local/sbin/shfs /mnt/user0 -disks 16777214 -o noatime,big_writes,allow_other  |& logger

Nov 12 09:53:44 Tower emhttp: shcmd (42): mkdir /mnt/user

Nov 12 09:53:44 Tower emhttp: shcmd (43): /usr/local/sbin/shfs /mnt/user -disks 16777215 2000000 -o noatime,big_writes,allow_other -o remember=0  |& logger

Nov 12 09:53:44 Tower emhttp: shcmd (44): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 40 3 * * * /usr/local/sbin/mover |& logger"

Nov 12 09:53:44 Tower emhttp: shcmd (45): /usr/local/sbin/emhttp_event disks_mounted

Nov 12 09:53:44 Tower emhttp_event: disks_mounted

 

Below is the output of an fdisk lu command:

 

Disk 1

root@Tower:~# fdisk -lu /dev/sde

 

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.

 

 

Disk /dev/sde: 4000.8 GB, 4000787030016 bytes

256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sde1              1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

root@Tower:~#  dd if=/dev/sde count=195 | od -c -A d |  sed  30q

195+0 records in

195+0 records out

99840 bytes (100 kB) copied, 0.00223548 s, 44.7 MB/s

0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0000448 002  \0 356 377 377 377 001  \0  \0  \0 377 377 377 377  \0  \0

0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  U 252

0000512  E  F  I      P  A  R  T  \0  \0 001  \0  \  \0  \0  \0

0000528 354 357 242 345  \0  \0  \0  \0 001  \0  \0  \0  \0  \0  \0  \0

0000544 257 276 300 321 001  \0  \0  \0  "  \0  \0  \0  \0  \0  \0  \0

0000560 216 276 300 321 001  \0  \0  \0 211  e 025  ; 331 361  9  F

0000576 227 334 276 232  ; 374 214  q 002  \0  \0  \0  \0  \0  \0  \0

0000592 200  \0  \0  \0 200  \0  \0  \0 270  8  { 250  \0  \0  \0  \0

0000608  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0001024 257  = 306 017 203 204  r  G 216  y  =  i 330  G  } 344

0001040  ;  k 342  @ 375  | 215  E 246 327  C 302  _ 212  |  X

0001056  @  \0  \0  \0  \0  \0  \0  \0 216 276 300 321 001  \0  \0  \0

0001072  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0098304 311 027  8  : 224  \ 006  4 027  \0 035 003 022  \0  \0  \0

0098320  \0  \0  \0  \0  \0      \0  \0  \0 004  \0  \0 343 270  9 003

0098336 204 003  \0  \0 036  \0  \0  \0  \0  \0  \0  \0  \0 020 314 003

0098352  \b  \0 002  \0  R  e  I  s  E  r  2  F  s  \0  \0  \0

0098368 003  \0  \0  \0 005  \0  q  t 002  \0  \0  \0 002 251 001  \0

0098384 001  \0  \0  \0 371 326 307 314  1 274  G 270 256  \f 221 242

0098400 245 244  T 367  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

0098416  \0  \0  \0  \0  S  \0 036  \0  6 265  ,  N  \0  N 355  \0

0098432  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0098496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 001  \0  \0  \0

 

...and here is the same result for the second "Unformatted disk"

 

Disk 2

root@Tower:~# fdisk -lu /dev/sdc

 

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes

1 heads, 63 sectors/track, 31008336 cylinders, total 1953525168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdc1              63  1953525167  976762552+  83  Linux

Partition 1 does not end on cylinder boundary.

root@Tower:~#  dd if=/dev/sdc count=195 | od -c -A d |  sed  30q

195+0 records in

195+0 records out

99840 bytes (100 kB) copied, 0.021666 s, 4.6 MB/s

0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0000448  \0  \0 203  \0  \0  \0  ?  \0  \0  \0  q  m  p  t  \0  \0

0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  U 252

0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0097792 256  \r 216 016  _ 322 230  \0  X 022  e 006 022  \0  \0  \0

0097808  \0  \0  \0  \0  \0      \0  \0  \0 004  \0  \0 205 345 365  F

0097824 204 003  \0  \0 036  \0  \0  \0  \0  \0  \0  \0  \0 020 314 003

0097840 212  \0 002  \0  R  e  I  s  E  r  2  F  s  \0  \0  \0

0097856 003  \0  \0  \0 005  \0 035 035 002  \0  \0  \0  X  X  \0  \0

0097872 001  \0  \0  \0  " 350 203 371  4  b  I  H 252 003 210  &

0097888 332 226 177 311  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

0097904  \0  \0  \0  \0 245  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

0097920  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0097984  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 001  \0  \0  \0

0098000  O 004  \0  \0  P 004  \0  \0  T 004  \0  \0  U 004  \0  \0

0098016  / 005  \0  \0  2 005  \0  \0 357  \b  \0  \0 360  \b  \0  \0

0098032 271  \t  \0  \0 321  \t  \0  \0  ,  \n  \0  \0  -  \n  \0  \0

0098048  3  \n  \0  \0  4  \n  \0  \0  :  \n  \0  \0  ;  \n  \0  \0

0098064  `  \n  \0  \0  a  \n  \0  \0  k  \n  \0  \0  l  \n  \0  \0

0098080  o  \n  \0  \0  p  \n  \0  \0  v  \n  \0  \0  w  \n  \0  \0

0098096  x  \n  \0  \0  y  \n  \0  \0 201  \n  \0  \0 202  \n  \0  \0

0098112 211  \n  \0  \0 213  \n  \0  \0 214  \n  \0  \0 215  \n  \0  \0

0098128 216  \n  \0  \0 217  \n  \0  \0 220  \n  \0  \0 221  \n  \0  \0

0098144 222  \n  \0  \0 223  \n  \0  \0 224  \n  \0  \0 225  \n  \0  \0

0098160 226  \n  \0  \0 227  \n  \0  \0 230  \n  \0  \0 231  \n  \0  \0

  • Author

Someone please help, thank you!

  • Author

bump...need some help

  • 2 weeks later...

See check disk file systems in my sig. What command did you enter exactly?

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.