During the re-sync monitor syslog to see if there are still disk related errors.

11 hours ago, JorgeB said:

Since parity is invalid you'll need to do a new config to re-enable disk3 and re-sync parity.

Did that and looking good now. Speed is at 120mb/sec (much better than the 1mb I had two days ago).

After parity sync is done adding new disks and changing the file system.

So just when I tought I was almost done with everything, a new problem occured.

 

After changing 2 disks from reiserfs to xfs and transfering files to another disk, I replaced one of two older disks by a newer/bigger disk. 

 

I follow the WIKI procedure for this. After having shut down the server, swapping the old with the new disk, I tried rebooting the server.

 

Unfortunately withouw any luck as the server couldn't be found in my network. After hooking up the server to a screen a can only see a black screen with in the right corner below B2. 

 

I've already tried various USB ports without any luck. 

 

Should I make a back-up of the files on the USB and then put a new build on the USB? Or are there other steps before doing this? Couldn't find any topics about this B2 message (except for Backblaze B2 topics).

6 minutes ago, Starkiller said:

a screen a can only see a black screen with in the right corner below B2. 

That looks like a BIOS post code, does Unraid start booting, i.e., do you see the Unraid boot menu?

6 minutes ago, JorgeB said:

That looks like a BIOS post code, does Unraid start booting, i.e., do you see the Unraid boot menu?

Unfortunately I can't see anything, except for the black screen with that B2.

 

Some days ago I've updated to the latest version of Unraid but there weren't any problems when shutting down/rebooting the server. Except for yesterday, just after I swapped disks.

 

Would it be a BIOS problem with the motherboard or the LSI board?

As I can't find the server in my network, my guess is it won't boot into Unraid. If it would boot I should be able to see the server in my network. Or not?

59 minutes ago, Starkiller said:

nfortunately I can't see anything, except for the black screen with that B2.

Power off the server, power back on, what do you see? Normal post process or just that code, or initial BIOS post and that code? If you only see that try resetting the CMOS.

When connecting the new 18TB disk, I can get into the LSI BIOS but not in the motherboard BIOS. After exiting the LSI BIOS I get the black screen with B2 in the lower right corner.

 

When connecting my old 10TB disk (which served previously as the parity disk and was replaced by another 18TB disk) I can get into the LSI BIOS as well as the motherboard BIOS and Unraid boots. 

 

So my guess is the new 18TB is causing the problem. I've tried connecting it to a SATA port on the motherboard and by connecting it to the LSI board. No matter what I do, with the new 18TB disk the system doesn't boot.

 

Any clues as what could cause this? My new 18TB disk as well as my 18TB parity disk are the same type WD 18TB ultrastar dc hc550 disks.

If it boots with just the other identical 18TB it suggests tome that one has a problem.

Man I'm really getting fed up with all these problems.

As told, yesterday I've put the old 3TB disk back, as Unraid didn't wanted to boot with the new 18TB disk. As I knew Unraid booted with the old 10TB data disk (which was previously my parity disk and replaced by another 18TB disk) I decided to replace the 3TB disk with the old 10TB disk.

I followed these steps:

 

1. Stop the array

2. Unassign the old 3TB drive if still assigned (to unassign, set it to No Device)

3. Power down

4. Connected the cables from the 3TB drive to my 10TB drive

5. Power on

 

After that, Unraid tells me the 3TB disk is missing. However, it doesn't mention the 10TB disk. So I can't assign it to the slot of the old 3TB disk.

Am I missing something?

My goal was to change already the 3TB disk with a 10TB disk before dealing with that new 18TB disk.

3 minutes ago, Starkiller said:

Am I missing something?

Difficult to follow, at leas for me, what you have done, please post a screenshot of the current array and the diagnostics.

After having shut down, with the 10TB disk still connected (but not detected by Unraid), I connected the 3TB disk again and rebooted. It detected the old 3TB as a new disk and asked to do a data-rebuild. So this is now running. Is this data rebuild necessary knowing that the data from old 3TB disk was formatted to XFS earlier?

 

It's not the first time I've changed disks. This server has been running for almost a decade and now all of a sudden nothing than troubles :s

 

 

toschestation-diagnostics-20221003-2009.zip

Changing array disks always requires either a disk rebuild or parity sync, it's always been like that.

With so little RAM probably best if you don't try to do anything except NAS (no dockers, no VMs)

21 hours ago, trurl said:

With so little RAM probably best if you don't try to do anything except NAS (no dockers, no VMs)

I've got no VMs, just one docker (Emby) but that one is stopped.

22 hours ago, JorgeB said:

Changing array disks always requires either a disk rebuild or parity sync, it's always been like that.

Yes, I know but what I don't understand is when I follow the replace disk procedure Unraid doesn't detect my 10TB disk as a new unassigned device. With the 3TB disk Unraid detects it immediately.

44 minutes ago, Starkiller said:

Yes, I know but what I don't understand is when I follow the replace disk procedure Unraid doesn't detect my 10TB disk as a new unassigned device. With the 3TB disk Unraid detects it immediately.

Don't ask me how but I've tried my luck again this evening and Unraid finally detected the 10TB disk. I'm letting Unraid run the disk clear for that 10TB disk now. After that I'll try my luck again with the 18TB disk.

Now that everything is back up and running, the filesystems have been changed to xfs and my 10TB and 18TB disk have been added I would like to thank @JorgeB and @trurl for all your help!!! Much appreciated!