March 7, 20179 yr As of yesterday I am unable to boot my server. Moments after showing the login prompt the server suddenly shuts down and reboots. This keeps happening on both Unraid OS, Unraid GUI and Unraid Safe. Memtest runs fine and has been running for a couple of hours. The probable cause: Yesterday I added a new SSD to my cache pool. I made sure to preclear the disk first. However, when I added the disk to the array i got the following message: Event: unRAID Cache disk message Subject: Warning [HOMESERVER] - Cache pool BTRFS too many profiles Importance: warning After trying to stop the array, the server became unresponsive so i made the call to reboot. This is when the problem started. After that shutdown it never turned on anymore and has been in a bootloop ever since. The normal boot runs fine and I don't see any errors during boot. Everything works until the login prompt shows. 5 to 10 seconds after booting has finished the server suddenly shuts down (And auto restarts). Before all this the server was running stable for 2 years. Any help would be greatly appreciated! EDIT: I am able to start the server with an offline array. The system crashes the moment I try to start the array and a parity check begins (Even without the new drive) EDIT 2: I switched out my PSU just to be sure and the array is working fine now. No driver or memory errors whatsoever... Seems it was the PSU all along! Edited March 8, 20179 yr by Zwooosh Solved the issue
March 7, 20179 yr Community Expert That warning can happen when the initial cache pool balance runs after adding a new device, array won't stop until the balance finishes, if you let it finish probably there woudn't be any issue. Power down the server, disconnect the new SSD and try to start the array, if it starts you'll need to wipe the new SSD before re-adding it.
March 7, 20179 yr Author I tried this, but even without the new disk the system crashes as soon as the parity check starts.
March 7, 20179 yr Community Expert Disable array autostart by editing disk.cfg on your flash drive (config folder) and changing startArray="yes" to "no". The unassign all cache devices and start the array to confirm the issue is cache related.
March 8, 20179 yr Author I've tried each disk, but it kept failing. At the end I switched out my PSU just to be sure... and the array is running fine now (even with the new disk). Seems it was the PSU all along. Me adding a new cache disk was just a bad coincidence I guess...
Archived
This topic is now archived and is closed to further replies.