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.

Serious issues after upgrade (SOLVED!)

Featured Replies

Hi all,

 

I just upgraded to 5.0 today and am running into some serious issues. 

 

1.  I cant write to any of my shares.  Access is denied.  I can write to the disks, but not the shares.

2.  Some of my files seem to be corrupted... ish.  I cant access them with XBMC and cant run them at all through my PC.

 

Any suggestions?  Im a pretty amateur user who just uses the system as a media storage center. 

 

Thanks!

 

Andrew

  • Author

Oh, I also cannot stream 1080p media.  Its choppy and slow.  Thanks :)

Did you come from 4.7? Most likely you are having permission issues. Check step four below and re-check the steps below.

 

http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes

 

From Version 4.7

 

1.    Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:

        Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there.

        If present, delete these files from the flash (sorry, you will have to re-enter all your users after booting this release):

            config/passwd

            config/shadow

            config/smbpasswd

2.    Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly except for the Cache disk. If you previously had a Cache disk assigned, you will need to re-assign it manually and re-apply any unique configuration settings for it.

3.    Carefully examine the Identification strings for each disk. If you see "MBR: error", or "MBR: unknown" for any disk, do not Start the array; instead post your finding in the Forum announcement thread for this release. If everything looks ok, click Start to bring the array on-line. Note: there is a new configuration setting on the Disk Settings page called "Enable auto start". If you set this to "Yes", then upon next server boot, if the array is valid, then it will be automatically Started (this is the old behavior).

4.    Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model.

5.    Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication.

6. Reboot the other machines too.

  • Author

I have ran the install instructions to the letter.  I have also ran the permissions twice.  The only difference is that I have never had any users.  Everything is set to public. From what I can gather, it seems that I have lost permissions to two of my disks (out of 7).  I have attached a couple screens... hope it helps.

 

Screen1.png

 

Screen2.png

 

Screen3.png

 

Screen4.png

 

Screen5.png

Did you reboot your Windows computer?

  • Author

Yes.  I have also rebooted the router, just for kicks.

Need a syslog

 

and the output of:

ls -al /mnt/disk6
ls -al /mnt/user/TV/Big\ Bang\ Theory/Season\ 5

On your Windows Computer.  Click on 'Start', Control Panel', 'System'.  Look under the "Computer Name, Domain, and workgroup settings".  See what your Workgroup' name actually is.  In unRaid, you have it set to "Workgroup".  It should be the same as in Windows.

  • Author

Syslog attached.

 

Prostuff1, it will take me some time to get that output.  My server is pushed away in a corner.  Ill pull out a old monitor and keyboard in a bit. 

 

Frank, yes, workgroup is the group on all my computers :)

 

Thanks again guys!

syslog.txt

disk6 has some corruption on it.  It is being mounted read-only by unRAID to protect it from being corrupted any further.

 

You will need to run a reiserfsck on the disk and fix the corruption before doing anything else.

 

There should be instructions on this in the wiki somewhere.  Start with the Trouble Shooting link in my sig

  • Author

Results of "reiserfsk --check /dev/md1"

 

root@Tower:~# reiserfsck --check /dev/md1

reiserfsck 3.6.21 (2009 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will read-only check consistency of the filesystem on /dev/md1

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

###########

reiserfsck --check started at Mon Jul  9 09:39:43 2012

###########

Replaying journal: Done.

Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 476962

        Internal nodes 2837

        Directories 112

        Other files 1504

        Data block pointers 482613804 (129 of them are zero)

        Safe links 0

###########

reiserfsck finished at Mon Jul  9 09:57:13 2012

###########

root@Tower:~#

  • Author

Prostuff1:

 

root@Tower:~# ls -al /mnt/disk6

/bin/ls: cannot access /mnt/disk6: No such file or directory

root@Tower:~# ls -al /mnt/user/TV/Big\ Bang\ Theory/Season\ 5

/bin/ls: cannot access /mnt/user/TV/Big Bang Theory/Season 5: No such file or di

rectory

root@Tower:~#

Disk6 has the problem. md1 refers to disk1.

 

Results of "reiserfsk --check /dev/md1"

 

root@Tower:~# reiserfsck --check /dev/md1

reiserfsck 3.6.21 (2009 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will read-only check consistency of the filesystem on /dev/md1

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

###########

reiserfsck --check started at Mon Jul  9 09:39:43 2012

###########

Replaying journal: Done.

Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed

Checking internal tree.. finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 476962

        Internal nodes 2837

        Directories 112

        Other files 1504

        Data block pointers 482613804 (129 of them are zero)

        Safe links 0

###########

reiserfsck finished at Mon Jul  9 09:57:13 2012

###########

root@Tower:~#

  • Author

My apologies :)  Heres the correct scan (or the last part it would let me copy/paste):

 

 

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (225) to

the block (128025565), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (226) to

the block (128025566), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (227) to

the block (128025567), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (228) to

the block (128025568), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (229) to

the block (128025569), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (230) to

the block (128025570), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (231) to

the block (128025571), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (232) to

the block (128025572), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (233) to

the block (128025573), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (234) to

the block (128025574), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (235) to

the block (128025575), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (236) to

the block (128025576), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (237) to

the block (128025577), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (238) to

the block (128025578), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (239) to

the block (128025579), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (240) to

the block (128025580), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (241) to

the block (128025581), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (242) to

the block (128025582), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (243) to

the block (128025583), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (244) to

the block (128025584), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (245) to

the block (128025585), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (246) to

the block (128025586), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (247) to

the block (128025587), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (248) to

the block (128025588), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (249) to

the block (128025589), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (250) to

the block (128025590), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (251) to

the block (128025591), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (252) to

the block (128025592), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (253) to

the block (128025593), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (254) to

the block (128025594), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (255) to

the block (128025595), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (256) to

the block (128025596), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (257) to

the block (128025597), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (258) to

the block (128025598), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (259) to

the block (128025599), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (260) to

the block (128025600), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (261) to

the block (128025601), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (262) to

the block (128025602), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (263) to

the block (128025603), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (264) to

the block (128025604), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (265) to

the block (128025605), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (266) to

the block (128025606), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (267) to

the block (128025607), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (268) to

the block (128025608), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (269) to

the block (128025609), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (270) to

the block (128025610), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (271) to

the block (128025611), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (272) to

the block (128025612), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (273) to

the block (128025613), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (274) to

the block (128025614), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (275) to

the block (128025615), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (276) to

the block (128025616), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (277) to

the block (128025617), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (278) to

the block (128025618), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (279) to

the block (128025619), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (280) to

the block (128025620), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (281) to

the block (128025621), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (282) to

the block (128025622), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (283) to

the block (128025623), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (284) to

the block (128025624), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (285) to

the block (128025625), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (286) to

the block (128025626), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (287) to

the block (128025627), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (288) to

the block (128025628), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (289) to

the block (128025629), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (290) to

the block (128025630), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (291) to

the block (128025631), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (292) to

the block (128025632), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (293) to

the block (128025633), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (294) to

the block (128025634), which is in tree already

bad_indirect_item: block 127963071: The item (2727 2767 0x1 IND (1), len 1184, l

ocation 96 entry count 0, fsck need 0, format new) has the bad pointer (295) to

the block (128025635), which is in tree already

bad_path: The left delimiting key [2727 2767 0x0 SD (0)] of the node (127963071)

must be equal to the first element's key [2727 2766 0xe64d001 IND (1)] within t

he node.

/124 (of 149\/155 (of 170-bad_path: block 128025320, pointer 154: The used space

(4072) of the child block (128156025) is not equal to the (blocksize (4096) - f

ree space (504) - header size (24))

/125 (of 149-/  1 (of 123\bad_path: The left delimiting key [2727 2770 0x3bb3001

IND (1)] of the node (128214911) must be equal to the first element's key [2727

2771 0x0 SD (0)] within the node.

/126 (of 149-/  1 (of 123\bad_path: The left delimiting key [2727 2772 0xe537001

IND (1)] of the node (128346504) must be equal to the first element's key [2727

2773 0x0 SD (0)] within the node.

/123 (of 123/bad_path: The right delimiting key [2727 2775 0xaac7001 IND (1)] of

the node (128537827) must be greater than the last (0) element's key [2727 2775

0xe21f001 IND (1)] within the node.

/127 (of 149-/  1 (of 142\bad_node: vpf-10350: The block (128537812) is used mor

e than once in the tree.

the problem in the internal node occured (128537812), whole subtree is skipped

/129 (of 149\/  1 (of 101|bad_node: vpf-10350: The block (128852515) is used mor

e than once in the tree.

the problem in the internal node occured (128852515), whole subtree is skipped

/130 (of 149// 48 (of 115/bad_path: The left delimiting key [2727 2784 0xf7cd001

IND (1)] of the node (129083893) must be equal to the first element's key [2727

2785 0x0 SD (0)] within the node.

/104 (of 115/bad_path: The left delimiting key [2727 2785 0xdd04001 IND (1)] of

the node (129204777) must be equal to the first element's key [2727 2783 0xf5790

01 IND (1)] within the node.

/131 (of 149//  1 (of 117-bad_node: vpf-10350: The block (128278516) is used mor

e than once in the tree.

the problem in the internal node occured (128278516), whole subtree is skipped

/132 (of 149\/  7 (of  85-bad_stat_data: The objectid (2790) is shared by at lea

st two files. Can be fixed with --rebuild-tree only.

bad_path: The left delimiting key [2727 2788 0xd733001 IND (1)] of the node (129

311242) must be equal to the first element's key [2727 2787 0xbe63001 IND (1)] w

ithin the node.

/  8 (of  8|/153 (of 153//170 (of 170\block 34139919: The level of the node (0)

is not correct, (1) expected

the problem in the internal node occured (34139919), whole subtree is skipped

finished

Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.

Bad nodes were found, Semantic pass skipped

30 found corruptions can be fixed only when running with --rebuild-tree

###########

reiserfsck finished at Mon Jul  9 16:30:32 2012

###########

root@Tower:~#

30 found corruptions can be fixed only when running with --rebuild-tree

Now,re-run the reiserfsck command, but with the --rebuild-tree option, as requested by the prior reiserfsck command.

reiserfsck --rebuild-tree /dev/md6

  • Author

Done. 

 

 

Tower login: root

Linux 3.0.35-unRAID.

root@Tower:~# reiserfsck --rebuild-tree /dev/md6

reiserfsck 3.6.21 (2009 www.namesys.com)

 

*************************************************************

** Do not  run  the  program  with  --rebuild-tree  unless **

** something is broken and MAKE A BACKUP  before using it. **

** If you have bad sectors on a drive  it is usually a bad **

** idea to continue using it. Then you probably should get **

** a working hard drive, copy the file system from the bad **

** drive  to the good one -- dd_rescue is  a good tool for **

** that -- and only then run this program.                **

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will rebuild the filesystem (/dev/md6) tree

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

Filesystem seems mounted read-only. Skipping journal replay.

###########

reiserfsck --rebuild-tree started at Mon Jul  9 21:57:33 2012

###########

 

Pass 0:

####### Pass 0 #######

Loading on-disk bitmap .. ok, 181385077 blocks marked used

Skipping 15663 blocks (super block, journal, bitmaps) 181369414 blocks will be r

ead

0%....20%                                                  left 138405815, 2136

                                                          left 0, 17451 /secc

3315 directory entries were hashed with "r5" hash.

        "r5" hash is selected

Flushing..finished

        Read blocks (but not data blocks) 181369414

                Leaves among those 179650

                Objectids found 3350

 

Pass 1 (will try to insert 179650 leaves):

####### Pass 1 #######

Looking for allocable blocks .. finished

0%....20%....40%....60%....80%....100%                        left 0, 137 /sec

Flushing..finished

        179650 leaves read

                179588 inserted

                62 not inserted

        non-unique pointers in indirect items (zeroed) 374

####### Pass 2 #######

 

Pass 2:

0%....20%....40%..vpf-10260: The file we are inserting the new item (2727 2766 0

x105001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) i

nto has no StatData, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x4f9001 IND (1), l

en 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDat

a, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x8ed001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xce1001 IND (1), l

en 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDat

a, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x10d5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x14c9001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x18bd001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x1cb1001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x20a5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x2499001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x288d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x2c81001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

60%vpf-10260: The file we are inserting the new item (2727 2766 0x3075001 IND (1

), len 4048, location 48 entry count 0, fsck need 0, format new) into has no Sta

tData, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x3469001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x385d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x3c51001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x4045001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x4439001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x482d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x4c21001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x5015001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x5409001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x57fd001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x5bf1001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x5fe5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x63d9001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x67cd001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x6bc1001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x6fb5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x73a9001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x779d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x7b91001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0x7f85001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x8379001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x876d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x8b61001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x8f55001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

80%vpf-10260: The file we are inserting the new item (2727 2766 0x9349001 IND (1

), len 4048, location 48 entry count 0, fsck need 0, format new) into has no Sta

tData, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x973d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x9b31001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0x9f25001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xa319001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0xa70d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xab01001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xaef5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xb2e9001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xb6dd001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0xbad1001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xbec5001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xc2b9001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xc6ad001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xcaa1001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0xce95001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xd289001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xd67d001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xda71001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xde65001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatDa

ta, insertion was skipped

.vpf-10260: The file we are inserting the new item (2727 2766 0xe259001 IND (1),

len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatD

ata, insertion was skipped

vpf-10260: The file we are inserting the new item (2727 2766 0xe64d001 IND (1),

len 2772, location 1324 entry count 0, fsck need 0, format new) into has no Stat

Data, insertion was skipped

100%                        left 0, 124 /sec

Flushing..finished

        Leaves inserted item by item 62

Pass 3 (semantic):

####### Pass 3 #########

Flushing..finished

        Files found: 3046

        Directories found: 271

Pass 3a (looking for lost dir/files):

####### Pass 3a (lost+found pass) #########

Looking for lost directories:

Looking for lost files:2 /sec

vpf-10680: The file [2727 2729] has the wrong block count in the StatData (50768

8) - corrected to (503304)

vpf-10680: The file [2727 2732] has the wrong block count in the StatData (40816

8) - corrected to (7288)

vpf-10680: The file [2727 2746] has the wrong block count in the StatData (50828

0) - corrected to (5512)

vpf-10680: The file [2727 2750] has the wrong block count in the StatData (50757

6) - corrected to (507464)

vpf-10680: The file [2727 2752] has the wrong block count in the StatData (50704

8) - corrected to (3752)

vpf-10680: The file [2727 2759] has the wrong block count in the StatData (51838

4) - corrected to (6224)

vpf-10680: The file [2727 2761] has the wrong block count in the StatData (47171

2) - corrected to (6480)

vpf-10680: The file [2727 2768] has the wrong block count in the StatData (49294

4) - corrected to (1280)

vpf-10680: The file [2727 2782] has the wrong block count in the StatData (44586

4) - corrected to (1544)

vpf-10680: The file [2727 2783] has the wrong block count in the StatData (50509

6) - corrected to (3144)

Flushing..finished

        Objects without names 20

        Files linked to /lost+found 20

Pass 4 - finished done 176163, 98 /sec

        Deleted unreachable items 707

Flushing..finished

 

The partition is mounted ro. It is better to umount and mount it again.

 

Syncing..finished

###########

reiserfsck finished at Tue Jul 10 01:44:32 2012

###########

root@Tower:~#

You will now need to re-mount the file system so it is writable.  You can either stop and re-start unRAID, or type

mount -o remount,rw /dev/md6

at the command line.

 

  • Author

Done.  Everything is working great now!  Thank you all for the assistance!

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.