This seems to continue to on and on.

Parity check came back with 377559 errors, and fix common problems states "Unable to write to disk1".

 

ANY HELP, truely appreciated!

Im a lost newbie.

tower45tb-syslog-20210926-1652.zip tower45tb-diagnostics-20210926-1059.zip

There are constant ATA errors on disks 1 and 3, check replace cables on both, there's also data corruption being detected on disk1, run memtest.

replaced the cables, now I recieve "Unmountable disk present" for disk 1

tower45tb-syslog-20210928-1423.zip tower45tb-diagnostics-20210928-0923.zip

There were some writes missing to disk1, likely due to the cable issues, you can try btrfs restore (option #2) to recover the data, disk will need to be formatted after, this error is fatal, and if you haven't yet you should first run memtest like mentioned above.

Thanks

not sure how to run memtest. Do I boot up on the non GUI to run?

It's the last option on the Unraid boot menu, it doesn't work if booting UEFI, only CSM.

 

 

 

I see option 2 is not GUI either. Kinda out of my abilities as a newbie. Shouldnt my parity disk be able to rebuild my disk 1?

Prior I could read my data on Disk 1, but not write to it. Now I can 't access it to copy it or backup. Any suggestions that are in the GUI interface for a newbie?

Anyway I can get back to previous position of just read only on Disk 1 so that I can back up files?

so "Format will create a file system in all Unmountable disks." will not bring back my files on disk 1 from the parity disk? I thought UNRAID could lose one disk and it could recover. What am i missing?

17 minutes ago, BigDaddyMoe said:

so "Format will create a file system in all Unmountable disks." will not bring back my files on disk 1 from the parity disk? I thought UNRAID could lose one disk and it could recover. What am i missing?

The problem is not a lost disk, but file system corruption.

 

the general case for handling this is described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.

I do not have access to check filesystem status, scrub, or balance they ar all greyed out and say "See Disk Settings" after them.

Anyway I can get back to read only so I can save the files? It is frustrating that I really dont have 1 disk loss recovery!

 

tower45tb-diagnostics-20210928-1129.zip tower45tb-syslog-20210928-1628.zip

What do I do if I DO NOT have access to "check filesystem status" ?

9 hours ago, BigDaddyMoe said:

What do I do if I DO NOT have access to "check filesystem status" ?

Just to be sure, did you start the Array in Maintenance mode ?

 

Can you make a screenshot of the drive setting ?

Check filesystem is going to help here, best bet is using btrfs restore like I mentioned above, I think the instructions in the FAQ are fairly easy to follow even for users not familiar with the CLI, but feel free to ask here if you have any doubts.

I am able to restore the files with "btrfs restore -vi /dev/sdi1 /mnt/disk7/restore" only problem all the historical dates of the files are changed to today

 

I did not start in maintence mode, didn't think that worked for btrfs.

"If the file system is BTRFS, then make sure the array is started, and NOT in Maintenance mode.

Important note! Drives formatted with XFS or ReiserFS must be checked and repaired in Maintenance mode. Drives formatted with BTRFS cannot be checked or repaired in Maintenance mode! They must be checked and repaired with the array started in the regular mode."

Edited October 1, 20214 yr by BigDaddyMoe

But mine is greyed out so?

Like already mentioned check filesystem won't help for this case.

On 9/29/2021 at 2:53 AM, JorgeB said:

Check filesystem is going to help here, best bet is using btrfs restore like I mentioned above, I think the instructions in the FAQ are fairly easy to follow even for users not familiar with the CLI, but feel free to ask here if you have any doubts.

Check filesystem is NOT going to help here?

4 minutes ago, BigDaddyMoe said:

is NOT going to help here?

Yes, not going to help, sorry, that was a typo before.

Any other advice?

As already mentioned only/best option for that problem is using btrfs restore.