fireplex Posted May 9, 2015 Share Posted May 9, 2015 So, changed nothing , needed to turn off power at home, so did graceful domain shutdown, stopped the array and ran a power off from the GUI. Power back on, array starts fine, cannot start domains: root@Tower:/mnt/cache/domains/dlna# virsh start DLNA error: Failed to start domain DLNA error: internal error: process exited while connecting to monitor: 2015-05-09T09:24:59.869165Z qemu-system-x86_64: -drive file=/mnt/cache/domains/dlna/dlna.img,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=native: could not open disk image /mnt/cache/domains/dlna/dlna.img: Could not open '/mnt/cache/domains/dlna/dlna.img': Permission denied root@Tower:/mnt/cache/domains/dlna# ls -l total 41943052 drwxrwxrwx 1 root root 36 Apr 30 21:44 DLNA/ -rw-rw-rw- 1 root root 0 Mar 30 2014 README.md- -rw-rw-rw- 1 root root 843 Apr 20 12:07 dlna.cfg -rw-rw-rw- 1 root root 843 Apr 20 12:12 dlna.cfg- -rw-rw-rw- 1 root users 42949672960 May 9 09:55 dlna.img -rw-rw-rw- 1 root root 771 Mar 30 2014 win7.cfg- root@Tower:/mnt/cache/domains/dlna# id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),281(docker) Same problem for other domain. Any ideas ? I'm root and permissions seem fine.... Should have added I first tried to start them via the GUI but got no error message, just didn't start - is there an error log somewhere for GUI failures? Quote Link to comment
bonienl Posted May 9, 2015 Share Posted May 9, 2015 This could well be a corruption on your USB stick. Run a windows disk check on it to repair any errors. Quote Link to comment
fireplex Posted May 9, 2015 Author Share Posted May 9, 2015 Looks like my cache drive went read only, btrfs complaining all over the place. Ever since I went to KVM my system has been so unstable... > > > Quote Link to comment
jonp Posted May 9, 2015 Share Posted May 9, 2015 Sounds like something else going on. KVM has nothing to do with your cache device going read only. Maybe look at smart data for the device and post syslog on the general support forum? Have you tried running btrfs scrub? Quote Link to comment
fireplex Posted May 9, 2015 Author Share Posted May 9, 2015 Everything was rock solid under Xen. I rebooted again and it mounted rw, ran a scrub on btrfs and no errors, copied data off it, reformatted cache as xfs maybe that will help... Running parity check. No smart errors anywhere I can see. Quote Link to comment
jonp Posted May 12, 2015 Share Posted May 12, 2015 Everything was rock solid under Xen. I rebooted again and it mounted rw, ran a scrub on btrfs and no errors, copied data off it, reformatted cache as xfs maybe that will help... Running parity check. No smart errors anywhere I can see. Not sure if this issue is still bothering you, but this line is a little odd: -rw-rw-rw- 1 root users 42949672960 May 9 09:55 dlna.img The rest of the files in there are root/root. This is root/users. Maybe a chown would solve that for you? Not sure how it got changed to begin with though... Quote Link to comment
fireplex Posted May 12, 2015 Author Share Posted May 12, 2015 Touch wood everything has been OK since moving to XFS but need to carry out some host reboots to be sure as that's when the issue occurred. Quote Link to comment
jonp Posted May 12, 2015 Share Posted May 12, 2015 Touch wood everything has been OK since moving to XFS but need to carry out some host reboots to be sure as that's when the issue occurred. Ok. Next time you do, please report back and let me know if you have an issue. Definitely want to make sure no problems occur. Quote Link to comment
mr-hexen Posted May 13, 2015 Share Posted May 13, 2015 is your cache drive a SSD? Some SSD's go read-only for a short while before they finally die and refuse to power up. This is BY DESIGN, to protect against ultimate data loss, as data could be recovered by special data recovery agents. 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.