Disk disabled


Recommended Posts

In principle that is correct.    
 

However when you start the array with the drive unassigned Unraid should be emulating the missing drive and you should check that it contains the expected content before proceeding with the rebuild steps.    The rebuild will only end up with what is on the emulated drive so you do not want to overwrite the physical disk with that if the emulated contents do not look correct.

  • Thanks 1
Link to comment
On 5/5/2021 at 8:52 AM, JorgeB said:

Lots of UDMA CRC errors on the disable disk, you should replace the SATA cable before rebuilding.

Thanks, that did the trick.

But there's a new problem now. When connecting to the server in Windows Explorer, I can see al my user shares. For my user share "media - video", I can't see the content. It says that the folder is empty. Obviously this is the same in the Unraid WebUI. However, when I select each disk individually I can see the content of the user share "media - video". How does it come that I can't see the content when clicking on the user share?

toschestation-diagnostics-20210508-0057.zip

Link to comment

This is what I've got. So what should I do now?

 

reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' ########### reiserfsck --check started at Sat May 8 02:55:20 2021 ########### Replaying journal: Trans replayed: mountid 84, transid 281928, desc 5340, len 1, commit 5342, next trans offset 5325 Replaying journal: | | 0.9% 1 trans Trans replayed: mountid 84, transid 281929, desc 5343, len 1, commit 5345, next trans offset 5328 Trans replayed: mountid 84, transid 281930, desc 5346, len 1, commit 5348, next trans offset 5331 Trans replayed: mountid 84, transid 281931, desc 5349, len 1, commit 5351, next trans offset 5334 Trans replayed: mountid 84, transid 281932, desc 5352, len 1, commit 5354, next trans offset 5337 Trans replayed: mountid 84, transid 281933, desc 5355, len 1, commit 5357, next trans offset 5340 Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 6 transactions replayed Checking internal tree.. finished Comparing bitmaps..Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sat May 8 03:03:49 2021 ########### block 593874200: The number of items (3) is incorrect, should be (0) the problem in the internal node occured (593874200), whole subtree is skipped block 1156345027: The number of items (14) is incorrect, should be (4) the problem in the internal node occured (1156345027), whole subtree is skipped bad_internal: vpf-10320: block 458467751, items 96 and 97: The wrong order of items: [107 108 0x1ed7b001 IND (1)], [107 108 0x48d83001 IND (1)] the problem in the internal node occured (458467751), whole subtree is skipped vpf-10640: The on-disk and the correct bitmaps differs.

Link to comment
3 hours ago, JorgeB said:

Did it finish successfully? Post the current reiserfsck --check output.

Apparently not, as it says that it didn't complete. I've let it run overnight. Should I start it once again?
 

reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' ########### reiserfsck --check started at Sun May 9 05:30:51 2021 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete)

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.