Disk problems with replacement disk

[Rob_Dingen]

Hi,

It's a long time ago to visit the forum about 10 years my Unraid was running fine.

Now I want to replace my HDD to 8TB HDD's and started with Parity.

That's working fine.

Then I swaped  disk 5 to 8TB disk and it starts to rebuild (looks good)

When finished I replaced disk 4 but when I boot and start the array he tels that disk 5 is not bootable.

In the meantime he stard to rebuild disk 4.

I format disk 5 and reboot , then the disk is bootable but I lost my data and it's not rebuilding.

Can I attach the old disk 5 and copy it to the new disk?

If possible how or do I need another procedure?

I upgraded before I started to Version 6.12.6 2023-12-01.

 

Rob

[JorgeB]

6 minutes ago, Rob_Dingen said:

I format disk 5 and reboot

Format is never part of a rebuild.

 

7 minutes ago, Rob_Dingen said:

Can I attach the old disk 5 and copy it to the new disk?

You can, you can use the UD plugin to mount it, then copy the data to the array.

[itimpi]

6 minutes ago, Rob_Dingen said:

When finished I replaced disk 4 but when I boot and start the array he tels that disk 5 is not bootable

I assume you meant 'unmountable'?   Handling of unmountable disks is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. That would likely have fixed the issue.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.   The Unraid OS->Manual section covers most aspects of the current Unraid release. 

[Rob_Dingen]

I download UD but the only options I have with the old disk are format or preclear

[trurl]

You will have to try to repair the filesystem

59 minutes ago, itimpi said:

Handling of unmountable disks is covered here

Attach Diagnostics to your NEXT post in this thread so we can better understand where you are now and give more specific advice.

 

And please don't do anything else without further advice.

 

1 hour ago, JorgeB said:

Format is never part of a rebuild.

Mistakes when replacing disks are probably the cause of most serious data loss.

 

[Rob_Dingen]

Here is my diagnostic zip file.

 

tower-diagnostics-20240131-1843.zip

[trurl]

Is ZR15B4FJ the original disk that might still have your data?

[JorgeB]

If ST8000DM004-2U9188_ZR15B4FJ is the old disk post the output of

blkid

and

fdisk -l /dev/sdh

 

[trurl]

Or is MJ1321YNG0HN2A the original disk that may still have your data?

[Rob_Dingen]

6 minutes ago, trurl said:

Or is MJ1321YNG0HN2A the original disk that may still have your data?

That's the one. 

It's my old disk 4

I also have my old disk 5 but not online.

If I can read my old disk 4 I put a new 8TB disk that's the ZR15B4FJ and copy it back.

[JorgeB]

2 hours ago, Rob_Dingen said:

I format disk 5 and reboot , then the disk is bootable but I lost my data and it's not rebuilding.

Can I attach the old disk 5 and copy it to the new disk?

Not sure I follow, are you missing the data from disk4 or disk5?

 

 

[Rob_Dingen]

I also have my old parity disk 

[Rob_Dingen]

1e changed parity Disk and did a parity check.

2e shut down and changed Disk 5 start array and rebuilt

3e shut down and replaced Disk 4 start array.

But when I start the array disk 5 was unmountable and the only option was format.

So I mis Disk 5 and the array start with a new Disk 4 8TB  and I cannot put the old Disk 4 back.

So I mis Disk 4 and 5 but I have both the old ones also the old parity disk.

[Rob_Dingen]

I thought if I can put disk 5 back I can rebuild disk4

[JorgeB]

post the output of

blkid

 

[Rob_Dingen]

[trurl]

Just noticed ReiserFS. Instead of rebuilding ReiserFS you should be working toward copying that data to other disks that are not ReiserFS.

 

 

[Rob_Dingen]

root@Tower:~# fdisk -l /dev/sdb
Disk /dev/sdb: 746.52 GiB, 801569726464 bytes, 1565565872 sectors
Disk model: External        
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors Size Id Type
/dev/sdb1           1 4294967295 4294967295   2T ee GPT
 

[trurl]

OK, it looks like disks 4 and 5 were already XFS so OK to rebuild those (but not OK to format). Maybe copying the others was the reason for upsizing?

[JorgeB]

Disk4 was reiserfs, were you trying to rebuild as xfs? That won't work, click on disk4, change fs to reiser and post new diags after array start.

[trurl]

10 minutes ago, Rob_Dingen said:

Disk /dev/sdb: 746.52 GiB, 801569726464 bytes, 1565565872 sectors

Isn't sdb supposed to be 3TB?

[trurl]

2 minutes ago, JorgeB said:

Disk4 was reiserfs, were you trying to rebuild as xfs?

I see that now. I was looking at vars so they must have tried to change it.

 

And of course, they had already formatted disk5 as xfs. Probably it was reiserfs before.

[trurl]

This is what we are waiting for, just in case it got lost in the extra chatter.

20 minutes ago, JorgeB said:

click on disk4, change fs to reiser and post new diags after array start.

[Rob_Dingen]

Yes I put the new disk and select XFS and let it rebuild

 

The problem is that I format Disk 5 and the new disk 4 wasn't rebuild and I cannot put back the old disk 4.

I try to mount the old disk with data on my windows machine and copy it back to the new disk

 

Then I can preclear the new drive and use it as XFS.

 

 

[trurl]

Nobody is asking you to put any disks back. Please DO NOT do that.

On 1/31/2024 at 2:12 PM, JorgeB said:

click on disk4, change fs to reiser and post new diags after array start.