Major root file system crashes after messing with virt-manager/virsh edit
Clash Royale CLAN TAG#URR8PPP
I have had two recent incidents of major root filesystem corruption after modifying or attempting to modify virtual machine domain XML file. In the first case, I don't remember if I actually succeeded in modifying the domain XML, but when I started the VM, virt-manager froze, I was unable to restart, so I did a hard reset. On restart, I got a GRUB rescue screen. Inspecting with gparted showed that my RAID1 array (my root FS) still existed, but the partition tables on it were gone.
I assumed that this was a one-off freak thing, possibly related to overused SSDs, so I tried again with a pair of brand new SSDs (in RAID1, which was also the case on the first go-round). This time, I again succeeded in creating a VM, but when I tried to use virsh-edit, I got a file system not writeable error. After restarting (I have a RX470 card which forces me to restart the machine between VM reboots), I got fcsk problems:
[![My second crash[1]](https://i.stack.imgur.com/xFCMa.jpg)
I don't know if the two are related, but they both seem to have to do with corruption and happened after monkeying with KVM/virt-manager. I don't know where to go from here. Is this a bug in something virtualization related that corrupts my disks? Is something about my system configuration or partition scheme making me vulnerable?
I realize that the fact that two different types of crashes does not bode well for reproducibility or troubleshooting, but I any suggests/stories about similar situations would be helpful.
Edit: So after recovering from the previous initramfs (using fsck), I have had another crash, again after editing with virsh-edit. In this case, I edited the XML and started the VM, which produced no response or error. I was unable to restart normally, and on hitting reset I booted to this:
fsck did not help in this case.
kvm raid root-filesystem corruption virt-manager
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
add a comment |
I have had two recent incidents of major root filesystem corruption after modifying or attempting to modify virtual machine domain XML file. In the first case, I don't remember if I actually succeeded in modifying the domain XML, but when I started the VM, virt-manager froze, I was unable to restart, so I did a hard reset. On restart, I got a GRUB rescue screen. Inspecting with gparted showed that my RAID1 array (my root FS) still existed, but the partition tables on it were gone.
I assumed that this was a one-off freak thing, possibly related to overused SSDs, so I tried again with a pair of brand new SSDs (in RAID1, which was also the case on the first go-round). This time, I again succeeded in creating a VM, but when I tried to use virsh-edit, I got a file system not writeable error. After restarting (I have a RX470 card which forces me to restart the machine between VM reboots), I got fcsk problems:
[
I don't know if the two are related, but they both seem to have to do with corruption and happened after monkeying with KVM/virt-manager. I don't know where to go from here. Is this a bug in something virtualization related that corrupts my disks? Is something about my system configuration or partition scheme making me vulnerable?
I realize that the fact that two different types of crashes does not bode well for reproducibility or troubleshooting, but I any suggests/stories about similar situations would be helpful.
Edit: So after recovering from the previous initramfs (using fsck), I have had another crash, again after editing with virsh-edit. In this case, I edited the XML and started the VM, which produced no response or error. I was unable to restart normally, and on hitting reset I booted to this:
fsck did not help in this case.
kvm raid root-filesystem corruption virt-manager
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30
add a comment |
I have had two recent incidents of major root filesystem corruption after modifying or attempting to modify virtual machine domain XML file. In the first case, I don't remember if I actually succeeded in modifying the domain XML, but when I started the VM, virt-manager froze, I was unable to restart, so I did a hard reset. On restart, I got a GRUB rescue screen. Inspecting with gparted showed that my RAID1 array (my root FS) still existed, but the partition tables on it were gone.
I assumed that this was a one-off freak thing, possibly related to overused SSDs, so I tried again with a pair of brand new SSDs (in RAID1, which was also the case on the first go-round). This time, I again succeeded in creating a VM, but when I tried to use virsh-edit, I got a file system not writeable error. After restarting (I have a RX470 card which forces me to restart the machine between VM reboots), I got fcsk problems:
[
I don't know if the two are related, but they both seem to have to do with corruption and happened after monkeying with KVM/virt-manager. I don't know where to go from here. Is this a bug in something virtualization related that corrupts my disks? Is something about my system configuration or partition scheme making me vulnerable?
I realize that the fact that two different types of crashes does not bode well for reproducibility or troubleshooting, but I any suggests/stories about similar situations would be helpful.
Edit: So after recovering from the previous initramfs (using fsck), I have had another crash, again after editing with virsh-edit. In this case, I edited the XML and started the VM, which produced no response or error. I was unable to restart normally, and on hitting reset I booted to this:
fsck did not help in this case.
kvm raid root-filesystem corruption virt-manager
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
I have had two recent incidents of major root filesystem corruption after modifying or attempting to modify virtual machine domain XML file. In the first case, I don't remember if I actually succeeded in modifying the domain XML, but when I started the VM, virt-manager froze, I was unable to restart, so I did a hard reset. On restart, I got a GRUB rescue screen. Inspecting with gparted showed that my RAID1 array (my root FS) still existed, but the partition tables on it were gone.
I assumed that this was a one-off freak thing, possibly related to overused SSDs, so I tried again with a pair of brand new SSDs (in RAID1, which was also the case on the first go-round). This time, I again succeeded in creating a VM, but when I tried to use virsh-edit, I got a file system not writeable error. After restarting (I have a RX470 card which forces me to restart the machine between VM reboots), I got fcsk problems:
[
I don't know if the two are related, but they both seem to have to do with corruption and happened after monkeying with KVM/virt-manager. I don't know where to go from here. Is this a bug in something virtualization related that corrupts my disks? Is something about my system configuration or partition scheme making me vulnerable?
I realize that the fact that two different types of crashes does not bode well for reproducibility or troubleshooting, but I any suggests/stories about similar situations would be helpful.
Edit: So after recovering from the previous initramfs (using fsck), I have had another crash, again after editing with virsh-edit. In this case, I edited the XML and started the VM, which produced no response or error. I was unable to restart normally, and on hitting reset I booted to this:
fsck did not help in this case.
kvm raid root-filesystem corruption virt-manager
kvm raid root-filesystem corruption virt-manager
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
edited Feb 20 at 7:12
Thoughtcraft
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
asked Feb 20 at 4:50
ThoughtcraftThoughtcraft
18611
18611
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30
add a comment |
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501766%2fmajor-root-file-system-crashes-after-messing-with-virt-manager-virsh-edit%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501766%2fmajor-root-file-system-crashes-after-messing-with-virt-manager-virsh-edit%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What changes were you trying to make to the VM?
– Michael Hampton
Feb 21 at 0:58
I'm not sure about the first time, the second and third time I was changing the PCI address of a passed-through card so that another card would pass through.
– Thoughtcraft
Feb 21 at 2:02
Did you do something like try to use a physical hard drive partition as VM storage?
– Michael Hampton
Feb 21 at 2:23
No, this was just a .IMG.
– Thoughtcraft
Feb 21 at 2:23
Actually the first time was a zvol, but the last two were .img.
– Thoughtcraft
Feb 21 at 2:30