Moving drives from old version to new version unRAID.


64 posts in this topic Last Reply

Recommended Posts

15 minutes ago, itimpi said:


since you were coming from an old Unraid version then maybe the drive is in ReiserFS format so you would need to use reiserfsck rather than xfs_repair.    In either case do not forget to include the partition number as omitting that will cause the superblock not to be fund.

 

I believe you are right, however, I did the XFS repair already. Now running reiserfsck  gives me this:

 

root@Tower:~# reiserfsck --check /dev/sde1
reiserfsck 3.6.27

Will read-only check consistency of the filesystem on /dev/sde1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes 
Failed to open the device '/dev/sde1': Unknown code er3k 127


root@Tower:~# 

 

 

Link to post
  • Replies 63
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

One more thing.  When you upgrade from a version prior to version 5.0, you will have to run the   New Permissions   Tool that is in the new version.   The permissions/owners changed with the introduct

SpaceInvader One has just put a video up on this subject.  

Just need to check "parity is already valid" after the new config and before array start.

Posted Images

12 minutes ago, ChipBuffalo said:

I believe you are right, however, I did the XFS repair already. Now running reiserfsck  gives me this:

 

root@Tower:~# reiserfsck --check /dev/sde1
reiserfsck 3.6.27

Will read-only check consistency of the filesystem on /dev/sde1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes 
Failed to open the device '/dev/sde1': Unknown code er3k 127


root@Tower:~# 

 

 


That suggests that the device /dev/sde may have dropped offline.

Link to post
1 minute ago, itimpi said:


That suggests that the device /dev/sde may have dropped offline.

Here is how it's showing up:

 

image.thumb.png.3f8880273a7da50e22ead39012e33e79.png

 

Little history, I was able to mount 3 of my 4 drives as unassigned devices to move the data onto new array. This drive is one that I thought I could put into my Desktop to get the files, which is probably what i did wrong right off the bat. 

What I was really hoping to do here is start a new temp unraid server with old array disks installed and see if I could get disk 4 to rebuild from the parity disk. 

 

Here is what came with that attempt: 

 

From there I went a little astray. 

 

 

Link to post

A possibility is to plug that drive into a Windows system and use a data recovery utility like UFS Explorer to see what it thinks is on the drive.   UFS Explorer is not free  if you actually want to use its recovery capabilities, but you do not have to pay for th option to simply scan the drive looks for files.

Link to post
1 hour ago, ChipBuffalo said:

root@Tower:~# reiserfsck --check /dev/sde1
reiserfsck 3.6.27

Will read-only check consistency of the filesystem on /dev/sde1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes 
Failed to open the device '/dev/sde1': Unknown code er3k 127

I did ask if it was XFS...

 

Try rebuild the superblock, then you'll need to run reiserfsck again with --rebuild-tree:

 

https://wiki.unraid.net/Check_Disk_Filesystems#Rebuilding_the_superblock

Link to post
2 minutes ago, JorgeB said:

xfs_repair didn't damage anything since it was run in read-only mode (-n), but it was a waste of time.

Knowing my situation, which command would you use?

 

reiserfsck --check /dev/md3 -> checks file system for errors

reiserfsck --fix-fixable /dev/md3 -> fixes file system errors

reiserfsck --rebuild-tree /dev/md3 -> rebuilds the file system (may have lost files)

reiserfsck --rebuild-tree -S /dev/md3 -> rebuilds the file system from entire partition (may have lost files, may recover old deleted files or their pieces)

reiserfsck --rebuild-sb /dev/md3 -> rebuilds superblock based on series of questions, answers MUST be accurate! Please see the Rebuilding the superblock section below.

Link to post
3 minutes ago, JorgeB said:

reiserfsck --rebuild-sb /dev/sde1

 

Follow the instructions carefully, once it's done:

 


reiserfsck --rebuild-tree /dev/sde1

 

This last one will take several hours.

Thank you JorgeB, this is how I will finish up with this drive. Learning alot here. Thank you for your patience and follow up. I will post on how it goes!

Link to post
14 minutes ago, JorgeB said:

reiserfsck --rebuild-sb /dev/sde1

 

Dang it:

 

root@Tower:~# reiserfsck --rebuild-sb /dev/sde1
reiserfsck 3.6.27

Will check superblock and rebuild it if needed
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Failed to open the device '/dev/sde1': Unknown code er3k 127


root@Tower:~# 
 

Link to post

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.