xenserver error fsck
-
Is the boot drive on the same drive as the VMs?
-
@BRRABill Good point. I thinks he's booting from a USB. Couldn't he rebuild on a new USB and then reintroduce the existing local storage?
-
@Danp said in xenserver error fsck:
@BRRABill Good point. I thinks he's booting from a USB. Couldn't he rebuild on a new USB and then reintroduce the existing local storage?
I was thinking that would be a lot easier to try than migrating 14TB of data.
-
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
-
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
-
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
-
@Dashrender said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
Ok so there is two questions here.
First - meta data backup. I know you've done this before. Got instructions lying around?
What gotcha's are needed to backup?
-
@Dashrender said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
Yeah but the host is still up he can take a backup of that still.
Either through XC or the CLI.
-
@BRRABill said in xenserver error fsck:
@Dashrender said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
Yeah but the host is still up he can take a backup of that still.
Either through XC or the CLI.
XO backups are not operational at moment.
-
@DustinB3403 said in xenserver error fsck:
@Dashrender said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
Ok so there is two questions here.
First - meta data backup. I know you've done this before. Got instructions lying around?
What gotcha's are needed to backup?
Nope, I never did this. I read about it.
-
@DustinB3403 said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@Dashrender said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
Yes the boot device is USB.
I can do this, assuming the underlying storage is reliable enough.
Any concerns or recommendations on doing so?
I'd be introducing the existing SR's back into the USB xs install.
Why would the underlying file system of the VM storage come into play? Isn't it the boot (USB) that is having the issue?
you have to adopt the SR back into the new install, and if your meta data isn't restored, you have to manually rebuild all of your VMs from the VDIs.
Yeah but the host is still up he can take a backup of that still.
Either through XC or the CLI.
XO backups are not operational at moment.
XO might be able to grab a meta data backup, but maybe not.
-
You can do it right from the graphical user thing on the host.
-
-
backing up metadata doesn't look like it'll work. at least to the localhost.
-
@DustinB3403 said in xenserver error fsck:
backing up metadata doesn't look like it'll work. at least to the localhost.
is it failing?
-
@DustinB3403 said in xenserver error fsck:
backing up metadata doesn't look like it'll work. at least to the localhost.
In that case, open XC or XO and write down the label of every VM, along with the disks for each and their exact order, along with the assigned resources (RAM, CPU).
then you can manually recreated them after the reinstall, then reattach the VDIs to the VMs.
This is what I had to do when boot system died.
-
@Dashrender said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
backing up metadata doesn't look like it'll work. at least to the localhost.
is it failing?
Yes, saying
-
@Dashrender said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
backing up metadata doesn't look like it'll work. at least to the localhost.
In that case, open XC or XO and write down the label of every VM, along with the disks for each and their exact order, along with the assigned resources (RAM, CPU).
then you can manually recreated them after the reinstall, then reattach the VDIs to the VMs.
This is what I had to do when boot system died.
So VM UUID and Disk UUID (and order)
-
What about this?
Collect VM metadata and store on shared storage.
xe-backup-metadata -u <UUID of SR you want the metadata saved to>
This creates a VDI containing VM metadata. Having this metadata available speeds up VM recovery because it creates the VM itself and restores the mappings between VMs and their disks (VDIs) - Otherwise must be done manually. -
Wnen I hit backup in xsconsole it gives me an option of where to store it.
