chropass

I've been identifying what files should I salvage from the physical HDD before rebuilding it. And after finishing it, I finally decided to start rebuild. Before doing that, I assume the loosen cable caused the issue, I wanted to make sure that the sata cables are properly connected. So i shutdown the server. After checking it, I booted the server, and now, somehow the server won't start up. I didn't force shutdown this time. Just initiated it from WebGUI. Trouble after trouble... But as for the initial issue, I think now I know what I should next. Assign the disk again and start the array. the disk would be rebuilt automatically, I think. Since the initial issue is almost solved, I set this post as solved now. Thank you everyone patiently helped me for more than a week. I really appriciate you!

I'm trying to identify them, but I feel like I cannot fully check every file... Now I'm starting to think I should just compare the whole 4TB worth of subdirectories between the emulated disk1 and the physical disk and see what's not there. Maybe it'll take several hours?

Disk1 is mounted (I saw the filesystem is stated as mounted, in Main->disk1 setting screen), disabled, and emulated, if I'm understanding correctly. Now I installed unassigned devices app and restarted the array with disk1 unassigned. Now I can browse it. Compared to what I can see in Share, it looks like some files/directories are missing. Also there's no lost+found folder.

Sorry for the confusion, maybe my English wasn't good enough Yes, I can see many files and directories exist there. I also noticed that actually many files I can see in Share are actually located at disk 1. I thought it's emulated by parity and not actually referencing disk 1, since disk 1 is still disabled...

I reboot and check lost+found via Share, but it's still only "Invalid path." tower-diagnostics-20260522-0216.zip

I want to repair every files including the ones that I don't recognize at this point. I can see the files inside lost+found when I browse it via Main -> Disk 1, but when I try to access it via Shares, it's empty or says "Invalid path." Does this mean those specific files are currently not being emulated? If so, should my next step be to get those contents to show up correctly under the lost+found share first?

I found lost+found but there's nothing there... But i can do see there's something in lost+found folder, if I browse it from Main->Disk1. I don't recognize every one of the files in the folders but like half of them were definitely looked familiar... Did I wrong something when i checked lost+found on Share?

I checked the filesystem of disk 1 and fixed it. (I had to clear log stuff) After that, it showed something like "no corruption on the filesystem". (sorry i didn't save the exact message somewhere) Then I stopped array and restarted without maintenance mode. Now I guess I can see everything I can remember on share! But disk 1 is still disabled. I really appreciate you and glad that at least my data is not lost. Now, what should i do next? (diags is taken after the array restarted) tower-diagnostics-20260521-2011 (1).zip

Here's a new diags. I can see folders in my share now. But I think not all of the share is restored, and disk 1 is still disabled. Because the free space of disks other than disk 1 is mostly unused, I believe most (or probably all?) of the data is stored in disk1. Is there any way to restore the date from disk1? tower-diagnostics-20260520-0741.zip

I replaced the parity drive's SATA cable with a spare one I had. Also, I noticed that the SATA port latch on Disk 1 is broken, so the cable comes off very easily (it doesn't lock in place). After rebooting the server, Disk 1 is still disabled. Array is not started. Here are the new diagnostics taken right after the reboot. (I just noticed that my cache is missing. I think it just became loose while replacing the sata cable on the parity. I'll fix it later.) Now, what should I do next to fix the Disk 1? tower-diagnostics-20260519-2328.zip

I tried to power it down from gui but it have been stuck at Array Stopping•Sync filesystems... for days (I wrote more details in the original post) And that is exactly the first question I wanted to ask, how should I power it down safely? Am I okay to forcibly shutdown it by long pressing the power button, for example? Also, I thought it was Disk 1 having some trouble because it's disabled, but does it looks like it was actually the parity?

Sorry, I thought I did post the diagnostics, but it was a smart report... tower-diagnostics-20260516-1637.zip

Hi. I got an issue on my server and lost access to my share. I need help safely shutting down, recovering my data, and diagnosing the root cause. Few days ago, in the morning, i noticed that i cannot access to my share. I checked webGUI and noticed that Disk 1 is disabled. People told me that it could be the SATA cable issue, so i started shutdown the server. Then the server started stoping the array. But it never ends until now, have been stuck at Array Stopping•Sync filesystems... The server log only shows error like below; The server have been stuck this state for few days now. I want to know how to safely shut it down so I can replace the sata cable of the Disk 1 so I can see if it actually caused the problem. I mainly used my server as simply a file server for last few months, and didn't any unusual stuff before the day i noticed the issue. My array is consist of 1 16TB parity, 1 16TB Disk 1 (which is disabled now), 2 1TB Disk 2 and 3 which is mostly unused, 1 500GB SSD cache. All of disks are xfs and cache is btrfs. The setting screen of Disk 1 shows it's mounted. Attributes tab has only one line; Smartctl open device /dev/sdc failed The parity says it's valid, but the last check completed was almost a year ago. (I will definitely schedule a parity check more frequently after this issue solved...) And the error count of the parity in the main screen looks too big. it's 6,795,035,043. I don't remember the count before the issue happens, but this is not okay I think? I though if the failure is happened on the disk 1, it would be emulated and I can still access to my share, as long as parity is valid. But now, my share is empty and I cannot access. What I want to know and need help is; Since the WebGUI is completely stuck on "Sync filesystems", how can I safely force a shutdown without causing further data loss? Why is Disk 1 not being emulated? Is it because the Parity drive (disk0) is also failing based on the log errors? Once I manage to reboot, what is the best way to test if this is a bad SATA cable/power split issue or a total hard drive failure? Thank you so much for any advice. I am a beginner of Unraid so please tell me if I'm lacking some info. tower-smart-20260517-0530.zip

Ok, I will try to resolve the video issue. I got another unused graphics card so maybe swap to it. If I got the video output back, what should I look for?