one problem after another

[Max]

so guys almost a week back from now my disk 2 was showing showing disk read errors during parity run, so i requested for help over here, so after looking at my diagnostics @JorgeB suggested that its most likely is a cable issue so i should replace my cable. so i did and since then its been working fine until yesterday when suddenly disk 2 started showing read errors again and it got disabled. after which i follishly ended up rebooting my server without even first collecting diagnostic data. so i just reseated cables and reenabled my disk 2 after it was working fine until now.

now again its showing disk read errors and it got disabled.

so here diagnostic data after my disk 2 got disabled again. PLEASE HELP !!!!

Edit : forgot to mention that currently its not showing any smartdata but im pretty it will come back just like last time it did after reboot.

unraid-diagnostics-20201219-0158.zip

Edited December 18, 2020 by Max

[trurl]

Check connections, SATA and power, both ends, including splitters. Make sure connections sit square without any tension on cables that might disturb them, and don't bundle cables.

 

Then post new diagnostics.

[Max]

6 minutes ago, trurl said:

Check connections, SATA and power, both ends, including splitters. Make sure connections sit square without any tension on cables that might disturb them, and don't bundle cables.

 

Then post new diagnostics.

so first shutdown the server then check all cables splitters etc and then start the server and take diagnostics before reenabling disk 2. right ?

[trurl]

51 minutes ago, Max said:

before reenabling disk 2.

Yes but take diagnostics with array started.

[Max]

Just now, trurl said:

Yes but take diagnostics with array started.

okay but the problem is my unraid usb decided to die on me in a middle of this😭 and stupid old me never tried backing it up.

and now when i tried running chkdsk afterconnecting it to my laptop it reported that its filesystem is raw so it can't be fixed.

Sooo????

[trurl]

According to your diagnostics you had CA Backup plugin installed. Was it setup to backup your flash drive?

[Max]

i think i did set it up to backup my flash drive but still it would be backing it up on server.

[trurl]

Prepare a new install, assign your disks just as they were but don't assign any disk to any parity slot. That will be enough to get to your files and find the flash backup. Hopefully disk2 will mount without needing rebuild.

[Max]

30 minutes ago, trurl said:

Prepare a new install, assign your disks just as they were but don't assign any disk to any parity slot. That will be enough to get to your files and find the flash backup. Hopefully disk2 will mount without needing rebuild.

okay so after restoring my flash both disk 1 and disk 2 are coming as they should but pairty drive is still showing up as unassigned. so i guess i will have recreate the parity. right ?

or is their a way around it??

[trurl]

10 minutes ago, Max said:

restoring my flash

Do you mean you found your flash backup? Did you copy the config folder from that backup to your flash drive? The config folder has all of your configuration, including your disk assignments.

[Max]

1 minute ago, trurl said:

Do you mean you found your flash backup? Did you copy the config folder from that backup to your flash drive? The config folder has all of your configuration, including your disk assignments.

yes i found my flash backup and i copied everything from it not just config folder.

[trurl]

Did you reboot with it after you did the copy?

[Max]

2 minutes ago, trurl said:

Did you reboot with it after you did the copy?

yeah as i first copied the files from server to my laptop then from laptop to flash. so yeah in a way  i did reboot.

[trurl]

If you booted up with config/super.dat from your backup, then you should have exactly the same disk assignments you had when the backup was made. Is anything else working like you expect?

[Max]

4 minutes ago, trurl said:

If you booted up with config/super.dat from your backup, then you should have exactly the same disk assignments you had when the backup was made. 

my super.dat is named super.dat.CA_BACKUP could that be the issue.

 

6 minutes ago, trurl said:

Is anything else working like you expect?

i have not started my array yet so  can't about vm or dockers but plugins are showing up fine

[trurl]

7 minutes ago, Max said:

my super.dat is named super.dat.CA_BACKUP could that be the issue.

Yes I remember now. The backup plugin does that as a safety measure. If you are sure your disk assignments haven't changed since the backup was made you should rename that to super.dat and reboot.

 

The danger is if super.dat thinks a data disk is parity which can happen when someone reuses a parity disk for data and doesn't get a backup of that change.

[Max]

okay so now after renaming and rebooting, disk 2 is showing up as emulated. so now i just start array (which wil start data rebuild) and post diagnostics over here. right ?

[trurl]

2 minutes ago, Max said:

okay so now after renaming and rebooting, disk 2 is showing up as emulated. so now i just start array (which wil start data rebuild) and post diagnostics over here. right ?

right

[Max]

unraid-diagnostics-20201219-0627.zip

i  hope after all this mess u could find wht u needed to help me.

[trurl]

That looks OK so far. How does it look on the Main page?  Under Array Devices you should see mostly Writes to disk2 and mostly Reads from all other disks and no Errors on any disks. What does it look like under Array Operation? I would expect 4TB rebuild to take less than 12 hours.

[Max]

4 minutes ago, trurl said:

That looks OK so far. How does it look on the Main page?  Under Array Devices you should see mostly Writes to disk2 and mostly Reads from all other disks and no Errors on any disks. What does it look like under Array Operation?

so far 0 errors and everything looks fine except disk 2 is currently showing unmountable : not mounted, not sure whether it was showing up as unmountable the last time it was data rebuilding or not.

7 minutes ago, trurl said:

 I would expect 4TB rebuild to take less than 12 hours.

around 7 hours

[trurl]

It was showing as mounted in those first diagnostics you posted at the top of this thread. Maybe we should have assigned parity disks also when looking for your flash backup. We'll see what happens and what can be done after rebuild finishes.

[Max]

6 hours ago, trurl said:

It was showing as mounted in those first diagnostics you posted at the top of this thread. Maybe we should have assigned parity disks also when looking for your flash backup. We'll see what happens and what can be done after rebuild finishes.

okay rebuild just finished but still disk 2 is showing up as unmountable : not mounted.

here is the diagnostics after its done rebuilding

unraid-diagnostics-20201219-1453.zip

[JorgeB]

7 hours ago, trurl said:

Maybe we should have assigned parity disks also when looking for your flash backup.

Yep, you can't do that with a btrfs filesystem and then rebuild, or always mount them in read-only mode if doing it without parity, if not the trans id of the rebuilt disk won't match, and this error is fatal, best bet it to try the btrfs restore option here.

[Max]

6 minutes ago, JorgeB said:

Yep, you can't do that with a btrfs filesystem and then rebuild, or always mount them in read-only mode if doing it without parity, if not the trans id of the rebuilt disk won't match, and this error is fatal, best bet it to try the btrfs restore option here.

i ended up with this error.

root@Unraid:~# mkdir /x
root@Unraid:~# mount -o usebackuproot,ro /dev/sdc1 /x
mount: /x: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.

what should i do ??