July 15, 20178 yr Hi, I am getting this error and really have no clue what can be causing it. I cannot start my windows vm. Everytime I start my vm this error shows up and unraid freezes forcing me to do an unclean poweroff. I thought it could be my cache ssd where the raw vdisk is. So I installed a new ssd mounted using unassigned devices, but same error shows up. Hope to hear good news to solve this. Rgds. tower-diagnostics-20170715-1938.zip
July 15, 20178 yr Community Expert Filesystem corruption on both your unassigned device and the docker image on your cache device, maybe worth running memtest to rule out RAM issues, if no errors run xfs_repair on the unassigned device and delete and recreate your docker image.
July 15, 20178 yr Author After doing this I still get the same error. I noticed at login in my monitor hooked up to unraid I see something before was not there: rc.diskinfo[7686]: process started. To terminate it, type: rc .diskinfo --quit How can I stop this?
July 16, 20178 yr Author I just reformatted the cache drive in xfs (before it was btrfs) and now the same vdisk works. I guess the error was produced by btrfs! Just wanted to post it in case someone goes through the same issue. Rgds.
July 16, 20178 yr Author Too early to say it works. Again -after reboot- I have the same error. Now I also tried another SSD formatted as XFS. And I did not use cache at all, only this SSD mounted using Unassigned Devices (UD). I did another 2 hours run of memtest with no errors. Docker (krusader) and VM (libvirt) where placed on the mounted SSD in UD. Docker and libvirt images were created new. My screenshot shows the error. I am not a linux expert so I can´t interpret this error. Any ideas how to proceed? Really don´t want to go the fresh Unraid install route, since now I am not sure if it is a hardware error or a pure software error. It only happens when starting the vm! Any help is appreciated.
July 17, 20178 yr 5 hours ago, luca2 said: I am not sure if it is a hardware error or a pure software error Its going to be hardware related. Whether that's due to bad ssd's, controller, cabling, or power is hard to say without a new set of diagnostics. 5 hours ago, luca2 said: It only happens when starting the vm! Because the system is unable to read the SSD at the sectors containing the libvirt.img. (And according to the screenshot, errors are also present on the docker.img file) Edited July 17, 20178 yr by Squid
July 17, 20178 yr Author Hi, if I have a backup of any of these .img's, and I already tried them and still get the error, how can I check the integrity of those .IMG?Also, if those .img's where created in an ssd formatted as btrfs, but now I formatted it as xfs, can this be also the causing issue? Enviado desde mi NX505J mediante Tapatalk
July 19, 20178 yr Author Ok, after 5 days working on my server I discovered the problem is caused when I plug a new USB hub I recently bought.Enviado desde mi NX505J mediante Tapatalk
Archived
This topic is now archived and is closed to further replies.