Tyrus

For me it always took forever. About the same as a complete parity check. 4-6 Hours. Still going atm. Nope, is there a build in tool in Unraid or do I have to use some Linux commands?

Damn, I started the check filesystem now. Anything in particular you are looking for? Oh no, not again... But why is it showing up as ok on the ui main tab, if there is was an error detected in the background? I started a check, will be done in 4-5 hours.

It is just one particular folder that is having problems. Can I somehow just reassign/refresh the user shares for this folder? unraidnas-diagnostics-20260110-1429.zip

Has someone any ideas how to fix this problem? The files are there since the size also remains the same but I just can't see them over the network and the folder is just empty.

I noticed something yesterday. Before, the disc 2 always showed up as "unmountable: wrong or no file system". When I started the array. At some point I think I removed it from the array and something happened at this point. The unassigning from the array seems to have triggered something, so the disc was recognized differently after that.

So, fun thing happened yesterday after we talked. I wanted to go to bed but before that, I assigned the precleared "faulty" disc back to it's slot as disc 2 and it gave me a warning. Bla bla all the data on the disc will be lost, if you start this config and since it was pre-cleaned and the data lost anyway, I just did it. The array went online and started to recover from the parity drive so I went to bed. Now I come back from work and the drive is restored and also the files! So I guess the filesystem error happened through the OS update after all and not my parity swap adventures. Or how should I interpret all of this? :D But one thing bothers me and I noticed it yesterday. Yesterday, when someone asked me to mount the working data drive(disc1) that was not affected, as an unassigned device and check for data, I looked in a particular folder and there were files there. But after I put the disc back in the array, and access the NAS over the network, and access the same folder this way, there are no files. So now I put the disc1 back out of the array and mounted it as unassigned, the files show up there. Any Idea what the problem could be? And why they don't show up in the folder over the network?

As far as I can tell, the data I copied during that time is not that important. Most stuff that I can regenerate from project-files but it will take time. Most of it were huge cache files. But I can't tell if I haven't copied some other data in-between. But even than, it wouldn't be that bad. All important data is on disc 1. How do I proceed now? Just slot disc 2 back in? Format it and it should work as expected? And thank you a lot to everyone who tried to help me! You are the best <3 About real back-ups: Real Back-Ups is also something that is on my to-do list. The problem with the drive through my off my original plans and timing. I plan to buy an external 16TB drive, which will mirror the data on the NAS. At least that was my plan until now. about cache size: I think it is just a display thing with the cache size

I know I have done something to the old parity. But I can't remember if it was pre-clearing or formating. But when I finshed the procedure there were no warning or problems. Except the parity errors that appeared durung the next parity check.

I must have formatted it at some point. But I can't say it for sure. I am not even sure my cache is configured correctly. That is something I was planing to tackle later and make a proper config. Because I have questions about it. Since 500GB and 1TB Cache drives only show up as 756GB in total.

Oh, so I misunderstood parity swap and wasn't reading it thoroughly enough. Is this the probable cause for the data loss? Since it was in november I won't be able to recall all the steps I did. I think I misunderstood replace the data disk with put the old parity as new data disk. I think the only difference is, that I placed the old parity drive in a new slot, instead of replacing an existing data-slot with the old parity drive. Like it is said in the instruction(step 12)

As far as I can tell, there was no emulation message. I was replacing the parity disc. Isn't parity swap exactly for that? I replaced the old parity disc with a bigger one. After the replacement I used the now unused old parity disc as a second data disc to increase the size of my data-array.

Yes, I have definitly written data to it, since disk 1 was full and I was getting errors that there was no space, before adding disc 2. And the data was showing up(I think)

yes

sdc is disc 1(5S39) sdb is disc 2 (5SBX) Yeah, that is what i thought too but that's all I have done beside upgrading to new Unraid version after that. I haven't done any changes/configs or whatever besides that. And then suddenly disc 2 was showing as "unmountable" etc.

Sorry, missed the answer on the new page. So to clarify it with Serials: My original array was (WS255S39) as data and (WS255SBX) as parity. I wanted to swap the WS255SBX(old parity) with a new 8tb drive as the new parity and use the now free WS255SBX(old parity) as a second data drive beside WS255S39(old data drive) to expand the storage. Since my old data drive was full. So the new config looked like that: WS255S39(old data) + WS255SBX(old parity, now new data after parity swap) and WRQ31N7K as the new parity. The array was working like expected and I could copy new data to the array, since it was expanded by WS255SBX. The only problem was, that I was getting a ton of parity errors. After some time I tried to fix the parity errors with the "write corrections to parity disc" command and somewhere after that and the upgrade to 7.2.2 the data on WS255SBX was gone. I hope that helps :) unraidnas-diagnostics-20260106-2214.zip

It works but the data on the original disk was luckily never a problem. The problem is only with the new drive that I added to the array and the data that was on it.

I followed the parity swap instruction but probably messed something up. It was a while ago(in november) so I don't remember the details anymore... The array was working fine without errors or emulation. But something wasn't right with the new parity drive. I can. But what should I do afterwards?

I don't understand how that would work. My old array was sdc as data and sdb as parity. Everything was fine with that. Than I swapped the parity(sdb) with a new one(sde) and used the old parity(sdb) as an additional data disc on the array. My current array is sdb + sdc = data drives and sde as parity. This array had over 50 million parity errors and when I fixed them, it looks like I killed all the data on (sdb). So I am not sure where the parity information should come from, to restore the data. Or am I missing something?

Yes, the original Data-Disc from the "old" array is, sdc(4tb). sdb(4tb) was the old parity disc. sdb is the one that is now pre-cleared. And the new parity disc is sde(8tb) As far as my knowledge goes, the data on sdb is lost, isn't it? Luckily it's not thaaat bad. All the important stuff is on "sdc" and the stuff that was copied on sdb can mostly be redownloaded. If I am not missing some crucial files, that i copied on the NAS at the time, and forgot about...

Yes, exactly! Sorry I haven't specified it further.

So, the command wasn't able to fix this. And I have done some digging and I am missing files for sure that were on this drive. So I have started thinking about the pre-cleared state. And the only time the drive was precleared was when I updated my parity disc to an 8TB drive and used the old parity drive as a second hdd(sdb) in the array. I followed the official instructions HERE But after that, the drive was working and I copied files to the larger array which were also on the "new"(sdb) drive, since the other, original drive(sdc) was full. The only problem I had was, that I had tons of parity errors. Like 50+mil. Could it be that by fixing the parity problems, the drive was put back in the pre-cleared state because I messed something up? That was also around the time I did the update. But there was still no error showing up. The error "Unmountable: wrong or no file system" appeared only after the update. Could it be that the restart needed for the update triggered an issue that would have shown the error even with a "normal" system restart?

I don't understand how it was running before then. Because as far as I could tell, no data was missing. Started the command. Will report as soon as it finishes. EDIT: Sorry, could not find valid secondary superblock Exiting now.

I understand that the disk seems to be only precleared without any data but it wasn't showing up like that before the update. And I have also been copying data on the disk, since the other (sdc) is full. If it has been running in emulated mode the whole time, shouldn't it have said so? unraidnas-diagnostics-20260103-1142.zip

Before the update the disks weren't showing any errors or messages and worked fine. I tried to run the "check file system" thing again and pressed fix. When it finished it said "File system corruption detected." and I could press "fix" again and it started an other round of "fixing" and it is running now. But I tried all of this before. This is what fdisk -l /dev/sdb said: Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000NE001-2MA1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 1 4294967295 4294967295 2T 0 Empty

yes, it's still showing up as unmountable.