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.

Transfer Data from unraid V5 disk to new setup unraid V6 server

Featured Replies

  • Replies 58
  • Views 6.6k
  • Created
  • Last Reply
  • Author

So  i followed your link, used the "[Plugin] Fix Common Problems".

The initial scan showed me this:

unraid4.PNG.79751d8fc5fba6164ea3b18ad8a07ceb.PNG

  • Author

Then when is re-scanned this (the system file errror disappeared, is this because of maintenance mode?):

 

unraid6.PNG.f7c0fc23fab3241cb2e57279a961e145.PNG

  • Author

And the information i get when i start the array in "maintenance mode":

unraid5.PNG.5a1f976f028331ad17c5b9b96091662b.PNG

And the information i get when i start the array in "maintenance mode":

How did the file system type get set to BTRFS? It should be ReiserFS like your previous screenshot showed.

(the system file errror disappeared, is this because of maintenance mode?):

Yes

And the information i get when i start the array in "maintenance mode":

How did the file system type get set to BTRFS? It should be ReiserFS like your previous screenshot showed.

Because he was playing with the different FS types trying to get it to mount.  Probably left it at btrfs.

 

Should switch it to ReiserFS before running the FS checks (since OP is coming from V5 it's going to be Reiser)

And the information i get when i start the array in "maintenance mode":

How did the file system type get set to BTRFS? It should be ReiserFS like your previous screenshot showed.

Because he was playing with the different FS types trying to get it to mount.  Probably left it at btrfs.

 

Should switch it to ReiserFS before running the FS checks (since OP is coming from V5 it's going to be Reiser)

Since the disk was used in V5, it should be ReiserFS. I'd try manually setting the file system type in the disk setting to Reiser and see if it mounts.

And the information i get when i start the array in "maintenance mode":

How did the file system type get set to BTRFS? It should be ReiserFS like your previous screenshot showed.

Because he was playing with the different FS types trying to get it to mount.  Probably left it at btrfs.

 

Should switch it to ReiserFS before running the FS checks (since OP is coming from V5 it's going to be Reiser)

Since the disk was used in V5, it should be ReiserFS. I'd try manually setting the file system type in the disk setting to Reiser and see if it mounts.

I tried it out(ReiserFS,see screenshots), It's says: "unmountable Disk"

After that i tried to mount it as the other two disk formats(xfs and the third one), same result:"unmountable Disk"

 

  • Author

And the information i get when i start the array in "maintenance mode":

How did the file system type get set to BTRFS? It should be ReiserFS like your previous screenshot showed.

Because he was playing with the different FS types trying to get it to mount.  Probably left it at btrfs.

 

Should switch it to ReiserFS before running the FS checks (since OP is coming from V5 it's going to be Reiser)

Since the disk was used in V5, it should be ReiserFS. I'd try manually setting the file system type in the disk setting to Reiser and see if it mounts.

I tried it out(ReiserFS,see screenshots), It's says: "unmountable Disk"

After that i tried to mount it as the other two disk formats(xfs and the third one), same result:"unmountable Disk"

 

Squid is right, file format was still on BTRF, now i returned it ReiserFS and got this:

unraid7.PNG.095833e657a7a16b70ff36b09f949381.PNG

  • Author

So what should be my next step?

unraid8.PNG.0b50e0af79973880e54dcdac8082c84f.PNG

Run the file system check previously linked

 

Sent from my LG-D852 using Tapatalk

 

 

  • Author

My result of  using file system check:

unraid9.PNG.63e81a83d04992664045036110158d83.PNG

  • Author

It seems my main problem is the missing superblock?!

It looked it up and found this instruction on:

https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

Would you recommend these steps? or should i try the "reiserfsck --fix-fixable /dev/md3 -> fixes file system errors" first?

And can i use the "answers" from the example below for my drive(it is noticed that inaccurate answers could damage the system)?

unraid10.PNG.4dd1951c51ad1bcb560d28ff2e66d93a.PNG

Just follow the instructions exactly as reiserfsck gives them, assisted by that section from Check Disk File systems.  Without a ReiserFS superblock, you can't try any other options, as they won't even be able to start.  Once you have a valid ReiserFS superblock, you will be instructed to run it again with the --rebuild-tree option.  Just do whatever it says.

  • Author

Tried it with this result:

unraid11.PNG.1e7059b8ad93e89c348302160d602fe4.PNG

  • Author

Then i tried to rebuild the root tree with following result:

unraid12.jpg.469e3caeeb3fe4423a2eb71f7d57c131.jpg

  • Community Expert

That means the disk has bad sectors, you can try using -B, but there will/could be some data loss.

  • Author

That means the disk has bad sectors, you can try using -B, but there will/could be some data loss.

No other way?  What does -B mean? For not running in background? I just know --rebuild-tree -S /Dev/md2

  • Community Expert

You basicalyy have 2 options:

 

Try to remap the bad sectors with HDD Regenerator (or similar) and then run reiserfsck again.

 

or

 

Run badblocks to generate a list of bad sectors on that disk, then run reiserfsck --rebuild-tree -B file.txt (using the previously generated file so reiserfsk knows how to handle those sectors)

 

 

If the disk is severely damaged with lots of bad sectors it may not work, with either option.

  • Author

You basicalyy have 2 options:

 

Try to remap the bad sectors with HDD Regenerator (or similar) and then run reiserfsck again.

 

or

 

Run badblocks to generate a list of bad sectors on that disk, then run reiserfsck --rebuild-tree -B file.txt (using the previously generated file so reiserfsk knows how to handle those sectors)

 

 

If the disk is severely damaged with lots of bad sectors it may not work, with either option.

 

Is the Command "reiserfsck --rebuild-tree -B file.txt" or "reiserfsck --rebuild-tree -B /Dev/md2" (in my case disk2)?

  • Community Expert

It would be something like this:

 

reiserfsck --rebuild-tree -B /boot/badblocks.log /dev/md2

 

Obviously indicating the right path/name to the badblocks output.

  • Author

It would be something like this:

 

reiserfsck --rebuild-tree -B /boot/badblocks.log /dev/md2

 

Obviously indicating the right path/name to the badblocks output.

 

"reiserfsck --rebuild-tree -B /boot/badblocks.log /dev/md2" doesn't work(oh wonder) so i tried:

 

"reiserfsck --rebuild-tree -B /boot/stdout.log /dev/md2" doesn't work ether, tried it because it console said "...write log file into 'stdrou' "

 

What i'm doing wrong?

  • Community Expert

Did you run badblocks first?

  • Author

Sorry, can't find/know the command for that?!

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.