Berdad_Zero Posted January 18 Share Posted January 18 So recently my NVME SSDs started droping off line I was able to move most of my appdata off of it just fine and now that I have rebuilt my docker containers and now after a reboot it wont start the array. After many reboots and testing things it shill wont mount. I'm out of ideas. Here is the diag file, I was not able to make one after a reboot if it tried to auto start. I was able to boot into safe mode and make one. aoi-box-diagnostics-20240117-1837.zip Quote Link to comment
JorgeB Posted January 18 Share Posted January 18 Enable the syslog server, start the array, and post that log. Quote Link to comment
Berdad_Zero Posted January 18 Author Share Posted January 18 Ok so here you go. I'm thinking the syslog-previous is after I enabled it, started the array told it to shutdown let it sit for a while before killing the power so i could recover the file. syslog.zip Quote Link to comment
Solution JorgeB Posted January 18 Solution Share Posted January 18 Zfs pool is crashing, see if it mounts in read only mode: zpool import -o readonly=on newcache If successful you can then start the array, the GUI will still show the pool unmountable, but the data will be under /mnt/newcache, you can then try to backup anything important and then reformat the pool. 1 Quote Link to comment
Berdad_Zero Posted January 18 Author Share Posted January 18 I got the array started. I have backed up the data, and its doing a parity check. It will take about a day and a half to complete. After its done I'll remove the zfs pool since there is ether something wrong with my drives or the motherboard, like I said all 3 would just drop off randomly. Thank you so much for the help! I was at my wits end. 1 Quote Link to comment
Recommended Posts
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.