LunarstarFurry

So I have 5 SAS Drive in my system currently, 4 of them that's in a array seems to spin down without any issue, but my issue is that I've leave a single drive which I was planning to use as backups that won't spin down. since I won't be around server for almost a year, is there a proper way to have drives in the server that's deactivated until required? Also I did try to click the Spun down on the unassigned drive which sadly doesn't seems work. Dec 1 05:13:14 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sdf Dec 1 05:13:24 Lunar-UnRAID emhttpd: spinning down /dev/sdd Dec 1 05:13:24 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sdd Dec 1 05:34:09 Lunar-UnRAID webGUI: Successful login user root from 192.168.214.152 Dec 1 05:36:44 Lunar-UnRAID emhttpd: spinning down /dev/sde Dec 1 05:36:44 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sde Dec 1 05:36:52 Lunar-UnRAID emhttpd: read SMART /dev/sde Tho for some reason it seems to works fine for both sdd and sdf? (Their both in a Array unlike sde which is currently unassigned).

Goteverythign back to normal since everything starts from thew broken Disk, no data is lost !

Also I decided to disable everything but mount everything like normal, and turns our the data is indeed rebuilt in the 10TB Drive, so I have all the drive with all data intact(As far as I know that is, at least I try to select some files from all 3 drives and they seems to work flawlessly and the used storage on each drive is no longer empty) Was doing a Parity Check now which shows quite a lot of errors tho.

Yeah but the thing is it is possible that there's already the data available in the Disk1, since this is the drive that it suppostly rebuild on. If you recall there's a weird thing happened earlier where I set UnRaid to rebuild data on this specific Drive but after if finish and the array is stopped it reverted to the old drives again, so it could be possible that there's already my data in it and no rebuild is needed at all.

You mention having maintance mode on does it needs to be on? Since I want to check if the data is available.

Could I mount it directly by not having maintance mode on? Since the Disk1 does have a possibility to have data already.

Actually should I exclude the SSD Cache since that's working fine?

Sure, But If I want to try emulate Disk1 first I'll need to mount the old Disk3 first, but yeah feel free to send the instructions.

I'm just not that sure how does the new config interact with things, because I'd like to do a new config first to mount it (Since I can't mount a 4kn drive directly) and check if the data is there or not, but I'm just not sure if I'd able to revert it to the state now if I tried a new config? Does the Parity needs anything on the system? I'm pretty much just afraid that the parity would just completely stop working after I create a new config. (Like maybe Parity is depends on some data that currently exist on the system that might get removed after I create a new config?) Also could u explain a lil closer on how new config works as well? (Just clicking on the new config already shows me a few options)

Oh nope, the old Disk 3 is available tho. So should still be a parity if I could get that mounted?

I'll take it as a win if I could get back some of it tbh, tho could I try to see if there's data in there first by doing new config? Because I'm not sure if I could do another new config with a missing drive or not later. Because I want to try to see if there's data in the Disk1 First because it there is parity won't even be needed, just kinda worry if it's not there we wouldn't able to try and see if we can rebuild data anymore since the config is lost

It's xfs

When you change a drive would the Parity data change? Or does it actually just copy all data in the drive ?

Emulated disk definitely will not mount now because after the above event without checking I tried to replace disk3 which cause another empty drive, Can only tell that the old drive is still fully functional. So I wonder if I'd able to remount the old Disk3 again, which means Parity, Disk2, and 3 should be functional and hopefully I'd able to bring back 1? Also I've checked most likely only disk1 having xfs issue, which is the drive we trying to replace so should be good there.

Is there a more specific tutorial on how to do that? I neevr use New Config before Another question is if the Disk1 is confirmed to be gone but I could managed to get Disk2, Disk3, and the parity drive online would I able to rebuild the data still if using the new config?

Then is there a way to force assign without clearning drive then? Sicne if it did rebuild with the new 10TB Drive I should able to assign that but unraid is askign to clear data. If there's a way to force assign drive I might able to fix both problem at the same time. Since If i could force assign the old 2TB Drive back into Disk3 The parity should be valid and I might able to just rebuild Disk1, Since the old Disk3 is known to be fully functional.

First Part I was just trying to do the parity swap (https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/) Step1: Stop Array Step2: Unassign B Drive Step3: Start Array Step4: Stop Array Step5: Unassign A Drive Step6: Assign E Drive as Parity Drive and A Drive as Disk 1 Step7: Press Copy (For the Parity Info) and wait until copy completes Step8: Start the array Step9: Stop data-rebuild and the array instantly Step10: Unassign Disk1 and Assign F Drive as Disk1 Step11: Wait for the rebuild Completes. And that's pretty much all, but the weird thing that happened is after the Step11 everything seems to be normal at first with the F Drive as Disk1, but right after I stop the array, The Disk1 is somehow assign to the A Drive again. That's why I'm a little bit confused on where did it actually rebuild the data. Is it on the A Drive or F Drive? (This would be very easy to figure out just by looking at the data but I don't think the new 4kn Drive can be mounted using the simple mount command) Because if it's on the new F Drive, that could explain why there's so many error on Disk1 since this is supposed to have data for the parity drive not files, and the actual data it rebuild is on F Drive which is currently Unassigned. Oh and also Both Drive have been PreCleared before

Let me explain what I did in 2 part so it won't be that confusing. Would be easier to figure out a solution as well. There's currently 6 Drives in the system, A: Old Parity Drive B: Disk 1 C : Disk 2 D : Disk 3 (Have Smart Error needed to be replaced) E: One of the new 10TB Drive to replace Parity F: Another new 10TB Drive to replace one of the Data Drive

I wonder if it was possible to check the log, maybe there's indication where the data is being rebuild? (sdc is the new 10TB Drive) (It could be either in the original drive (2TB) or the new (10TB) Drive

Also I already tried the xfs repair which does not work on the disk 1, the utility end up just placing a lost and found folder. As for Disk 3 I feels like the Parity Rebuild doesn't even work, Because what I was trying to do was replace a older drive to a new drive, but after the Data-Rebuild the new drive just appears empty. (Maybe could because the Disk 1 is already broke at that time but I and UnRAID just didn't notice?) Which is why I ask if it would be possible for me to remount the old drive again? If I'd able to remount the old Disk3 maybe It would be possible for me to just rebuild Disk1 since the parity should be valid again? Or the other options would be the weird bug I experience where I have mounted the new 10TB Drive in Disk1 and complete the data rebuild already(At least UnRAID Said rebuild is complete), but settings seems to got revert as soon as I stop the array, so maybe the full data is already available in the new 10TB Drive?

But it's been running fine until I started the Parity swap and the disk replacement tho But I'll still give memtest a go

Try to do the xfs_repair will all 3 drive which seems like the Drive 1 have a lot of CRC Error (Do I just repir that one first? Also another info as well, initially I was trying to replace the Disk1 with one of the new 10TB Drive right after the Parity Swap, which seems to went well (It shows the new Drive name and everything) but I notice that the storage indicated by UnRAID is remain at 2TB, so I end up restarting the array. That's where the weird thing happened, right after the array stopped the Disk1 just suddenly change back to the old 2TB Drive.

Aw Thanks eitherway, I think the Parity Swap went well, but when I tried to swap out an old 2TB drive to a new one is what went wrong (The other 2 Drive in the pool seems to still have all the data). (But since I'm just replacing old drive means the data is still in the old drive as far as I know) Could also be that since I didn't check the parity after doing the parity swap so a broken parity cause it to unable to calculate data as well.

Pretty much data rebuild seems to have failed or somethin, but I cold still copy the data over from the old one

Oh no, the data is still there as far as I know but it only exist in the old drive, not the drive that it being replaced with (The drive tht do the data rebuild pretty much)