February 24, 20251 yr Hi guys, My Cache SSD (256GB nvme drive, 2 years old) seems to have died completely (shows as missing in my Pool devices - Main after reboot), while watching a movie on plex being transcoded on cache. The syslog-previous file in diagnostics shows a lot of errors. This was the only drive in the cache pool. I have a few questions on what to do next: 1. With what it says in the logs, is my drive really dead? Is there anything to do or try to fix it? 2. If I buy a new one, what is the procedure to restore my data and docker images (all important files are on the array, my appdata was backed up the day before with the Appdata Backup plugin) ? 3. Are the root folders for the shares recreated on the new drive automatically (ex. domains, isos, system)? I'm using Unraid 7.0.0 Thank you! tower-diagnostics-20250224-1249.zip
February 24, 20251 yr Community Expert Try power cycling the server, not just rebooting, that may bring it back.
February 24, 20251 yr Author That worked thank you! Does that mean that the drive could be near a failure? (and is it worth it to buy a new one for redundancy in the pool?)
February 24, 20251 yr Community Expert 7 minutes ago, lilplants said: Does that mean that the drive could be near a failure? Not necessarily, try this, on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot and see if it doesn't happen again.
February 24, 20251 yr Author Here are the new diagnostics before and after doing what @JorgeB suggested. Everything seems to be fine after making the changes to Syslinux Configuration, but a parity check has started. tower-diagnostics-20250224-1405.zip tower-diagnostics-20250224-1415.zip
February 24, 20251 yr Community Expert 1 minute ago, lilplants said: but a parity check has started. Unclean shutdown was detected Feb 24 14:09:53 Tower emhttpd: unclean shutdown detected
February 24, 20251 yr Author 1 minute ago, JorgeB said: Unclean shutdown was detected This is weird because I rebooted from the Main page
February 25, 20251 yr Community Expert There could have been not enough time to shut down the services, or another thing preventing it, but if it were a one-time thing, I would ignore, if it happens again, it should be investigated.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.