X500658

Yeah, little update. Whole thing is basically gone, lots of stuff got corrupted (I blame myself for accidentally wiping the good drive) Nothing too major lost but my latest appdata backup was in 2025 Looks like I gotta buy a new NVMe 😐 Thank you @JorgeB and @trurl

Hello @JorgeB , I've spent the day copying the accessible data to my windows pc via scp, lots of I/O errors 🙁 I'll just swallow the pain of some of the files that have been corrupted (hopefully appdata and dockers are fine) By recreate, do you mean that I erase the pool? not just remove

I had the cache missing issue and followed https://forums.unraid.net/topic/179091-wrong-pool-state-cache-invalid-expansion/#comment-1483964 Now shares are missing even after reboot I also accidentally formatted nvme1 trying to fix, I can't find a way for "force accept" nvme2 ChatGPT says nvme2 is slightly not using the latest data but I know there was no important changes. probably just logs If someone could please point me in the right way Thank you tower-diagnostics-20260827-0235.zip

Hello, I recently swapped cases and didn't realize that it had a type-C front panel port. Pleasant surprise but my mobo (TUF X570 PLUS WIFI) doesn't have a connector for it, instead I still have the 2 PCIE x1 slots available. So far, I've found these two that seem to be the most believable ones: https://www.amazon.com/gp/product/B09YL8XG5D/ (ASM1042A) https://www.amazon.com/gp/product/B0B156WMGC/ (ASM3142) I'd like to ask if any of these work well with Unraid. I've read to avoid ASM HBAs and I don't know if it also applies to other types of cards. I've also read of user who had to edit the sysconfig file, I'd rather not do that, skill issue sadly.

Thank you, it works. I've reseated the cables as a temporary measure. I think the molex to SATA adapters were to blame. I'll be upgrading to a better one with more ports.

2 flash drives, one I've been using since 2021 and a newly flashed one using the tool. Both restart upon loading the unraid selecting from the startup menu like in the video

Hello, I'd like some help with my server, it was working smoothly for a year. Yesterday, I cleaned it (just removed dust) and now it boot loops on the unraid startup/selection screen. Even the debug lights show that it boots up fine. I'm using a Ryzen 5 3600, TUF X570 Plus Wifi, with BIOS ver 1405 while the latest is 4408. I doubt that I'd need to update my BIOS ver since all parts have been compatible since I them bought in 2020. I've tried the following: cleared CMOS several times reenabled several BIOS settings (CSM, SVM, fan curves, disabled fast boot) tried UEFI and Legacy individually and both at once checked the USB drive and it's fine, files match my last backup also ran chkdsk on Win10, no corruption memtest86, passed and 0 errors, 4/4 passes (dedicated memtest not the one built-in with the unraid usb) flashed a new unraid usb (still doesn't work) renamed "EFI-" to "EFI" in both usb drives it immediately restarts if boots in Legacy mode, I'm assuming this to be normal since the folder name is "EFI" If I press any arrow key or tab, it doesn't restart immediately but still will after I select one, regardless of whichever option I choose, even memtest Its stable when I stay in the BIOS, but after that, the fans ramp up and slow down immediately, and it restarts. In cases where I was able to select an option, it also took a while for it to finish loading bzroot (and bzroot-gui), then a few of the usual startup console messages pop up then it restarts. Here's a (relatively clear) video of it: https://imgur.com/a/QPQFMHj Can anyone tell me what's wrong? Did I miss something? I'm stumped Thanks 🙂

tried that beforehand and didn't work, and now it does? Weird. Thankfully the files are intact. sadly, now the parity drive is missing although it was detected by my sata hba controller on boot. Again did the shutdown and cable check, still nothing. Do I try again?

Woke up, booted with plans to build parity disk2 keeps giving read errors until it became unmountable in maintenance mode, xfs_repair -n says "fatal error --i/o error" and now it turned into the Ø array and I don't know anymore is this a PSU problem? tower-diagnostics-20220618-2348.zip

Silverstone ST70F-ES230 700W, 80+ plain/bland It has two molex lines with a 5-sata adapter (HDD, SSD, 3 HDDs) and 2-sata adapter (2 HDDs), one 2 sata line (2 HDDs) and one 2-sata line that became a failed 4-sata mod (cut too deep that it cant power drives) Now knowing that the 5-sata adapted molex line can't handle it properly, I plan to turn it to (3 HDDs, 2 SSDs) and move disk3 to the other molex/2-sata line, whichever has the vacancy. Lesson learned, especially now that I'm using 4TB drives that reach 10 hrs preclearing or parity syncing 😭

Oh damn, I'll transfer that drive and plan for a larger & better PSU. for future reference, how many drives is recommended from a molex line?

could being at the end of a molex to 5-sata cable be the cause?

I know, but I gave up on that data. I'll just hunt for new stuff tower-diagnostics-20220618-0057.zip

yes, replaced cables and also did -n

So disk3 became unmountable, I failed at xfs_repair -L (got stuck at "phase 7 format log to cycle 4"), all data was lost (byebye plex library) Now I'm trying to preclear it. the drive only says ST4000VN008 (lacking the -2DR166 in the model) and its at 10-15MBps. How badly did I mess up and can this still be fixed?