ifihaffto

Thanks @JorgeB So, stop the array, power down the nas and physically remove the disk. Use UFS explorer or similar to try and recover any data. Copy that somewhere (I'll get a replacement disk as it could do with some extra space). This is where I'm unsure of the order... Replace the disk, fire up the nas and add it back to and start the array (changed file system and formatted). This is effectively adding a blank disk to the array. Copy the files back to either the replaced disk or the share. How did I go?

Thanks for your help so far. I get Failed to open the device '/dev/md2p1': Unknown code er3k 127 when I attempt to rebuild the superblock. reiserfsck --rebuild-sb /dev/md2p1 Does it need to be an UNASSIGNED disk? It's currently in the array, which was started in maintenance mode.

It was. And I've left it that way to reduce the chance of me making anything worse.

No Sir, I did not. Unfortunately I know barely enough to scrape by (as you have seen ). Does that get appended to the reiserfsck command or is it run separately?

6.12.10 I ran the amended code you provide and got this: Failed to open the device '/dev/md2p1': Unknown code er3k 127

Yeah, it appears I didn't quite get it right.

Unraid console

Where will I find evidence of the check taking place? After running the command I got a message telling me where the log will be (kind of - it just said it will be in sdout but not where to find it), but nothing else to indicate something is actually happening.

Thank you! I will give that a try and report back. Exactly as written, or replace md2 with the disk assignment for Disk2? EDIT: NVM, I did some googling ... md2

Argh. Bugger. I figured taking it out of the array would stop the parity in place? Restart array > rebuild. As though it was a swapped drive? OK. Thanks

Parity to Disk 2 read/write would indicate that it should have rebuilt the disk. Did something I did delete the data from the Parity drive and it rebuilt empty blocks?

Hey everyone. I had an array disk that was on REISERFS and I was continually being warned that it was getting deprecated. I've been avoiding it for ages and thought I should bite the bullet. I was considering how I was going to shuffle all my data around, which was going to end up requiring a larger drive to be bought/installed, when it dawned on me that all I should need to do is just treat it like a disk replacement and the parity drive would take care of it. I think I was a little clumsy with the order of proceedings, which may have caused me to bollocks it up completely. From dodgy memory... I stopped the array. Changed the FS on the disk. Started the array. I figured this is where it would ask me to format the disk, which I would, then it would re-build the array. I saw that the disk was unmoutable and didn't check down the bottom to format the disk with the new FS. I stopped the array again. Unassigned the disk. Started the array. Why? I figured I needed to tell unraid that the disk wasn't being used and to rely on the parity drive. "I'll get you a new disk in a minute" Stopped the array again. Assigned the drive back again. Either started the array or formatted the disk and then restarted the array, which ever way that has to happen. The disk was formatted. Then I saw that the array or disk was being rebuilt. Huzzah! ... I thought. I confirmed that LOTS of writes to the disk in question were being performed, and I thought I was off to the races. I monitored it for a few minutes, and I started to get hot all of a sudden when I noticed that although there were lots of writes, the disk wasn't getting any fuller. Be patient, the UI just might not be a proper reflection of things. Next morning... my disk usage is the same as it was when the rebuild started (despite the writes) and I seem to have lost all the data that was on the disk. What did I do wrong?

Great. I'll stay tuned. Thanks

As others have said, thanks for your hard work on this plugin. I've recently upgraded Unraid to 6.12.10 and updated your plugin. The Status/Log indicates that the backups are all successful, but my [binhex-plex] container seems to get wiped out every time the backup runs. [23.07.2024 03:47:26][ℹ️][binhex-plex] Starting binhex-plex... (try #3) Container did not started! - Code: No such container I don't know if it's my docker config or backup. Any help would be greatly appreciated. Thanks again.

Thanks for the reply and suggestion. I'll give that a go.