xenserver error fsck
-
@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.
-
@BRRABill said in xenserver error fsck:
Wnen I hit backup in xsconsole it gives me an option of where to store it.
Do you have a local usb or something attached?
-
I do get a prompt of where to backup too, but local storage is the only option.
-
@DustinB3403 said in xenserver error fsck:
@BRRABill said in xenserver error fsck:
Wnen I hit backup in xsconsole it gives me an option of where to store it.
Do you have a local usb or something attached?
No. In fact my only option is my SR location.
Probably since the USB is having issues, maybe you can't back up the metadata?
-
@DustinB3403 said in xenserver error fsck:
I do get a prompt of where to backup too, but local storage is the only option.
Oh yeah, me too. I just renamed mine. Duh. (Duh on me.)
-
I dont even think I can migrate the VM's off.
-
@DustinB3403 said in xenserver error fsck:
I dont even think I can migrate the VM's off.
Probably not if the boot device isn't writable.
-
@Danp said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
I dont even think I can migrate the VM's off.
Probably not if the boot device isn't writable.
gotta fix that issue.... some how...
-
Hrm, maybe try remounting root? I think this should do it:
mount -o remount,rw / -
@travisdh1 said in xenserver error fsck:
Hrm, maybe try remounting root? I think this should do it:
mount -o remount,rw //devb/sdb1 read-write is write-protected.
So how do I remove that?
-
@DustinB3403 said in xenserver error fsck:
@travisdh1 said in xenserver error fsck:
Hrm, maybe try remounting root? I think this should do it:
mount -o remount,rw //devb/sdb1 read-write is write-protected.
So how do I remove that?
If it's write protected to the point that it won't remount in read/write mode (what you have here), it's time to assume the storage is not recoverable.
The good news (if such a thing exists in this situation), is that restoring from XO backups is quite quick. This is what I got to deal with 3 weeks ago. XS Root drive went into a read only state, and was stuck that way even between reboots. Replaced the root drive and imported the XO backups... I used XenCenter to import the XO image itself, and then used XO to import the other backups.
-
@travisdh1 said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
@travisdh1 said in xenserver error fsck:
Hrm, maybe try remounting root? I think this should do it:
mount -o remount,rw //devb/sdb1 read-write is write-protected.
So how do I remove that?
If it's write protected to the point that it won't remount in read/write mode (what you have here), it's time to assume the storage is not recoverable.
The good news (if such a thing exists in this situation), is that restoring from XO backups is quite quick. This is what I got to deal with 3 weeks ago. XS Root drive went into a read only state, and was stuck that way even between reboots. Replaced the root drive and imported the XO backups... I used XenCenter to import the XO image itself, and then used XO to import the other backups.
We've got dc's on this host...... which means I have to do a SPX restore (since XO) isn't backing up.
-
@DustinB3403 said in xenserver error fsck:
@travisdh1 said in xenserver error fsck:
@DustinB3403 said in xenserver error fsck:
@travisdh1 said in xenserver error fsck:
Hrm, maybe try remounting root? I think this should do it:
mount -o remount,rw //devb/sdb1 read-write is write-protected.
So how do I remove that?
If it's write protected to the point that it won't remount in read/write mode (what you have here), it's time to assume the storage is not recoverable.
The good news (if such a thing exists in this situation), is that restoring from XO backups is quite quick. This is what I got to deal with 3 weeks ago. XS Root drive went into a read only state, and was stuck that way even between reboots. Replaced the root drive and imported the XO backups... I used XenCenter to import the XO image itself, and then used XO to import the other backups.
We've got dc's on this host...... which means I have to do a SPX restore (since XO) isn't backing up.
-
And a f***ing massive file server.
-
Any chance you previously saved the metadata to your SR?
-
Sorry you are going through this.
Especially on a Friday night.
-
Im going to start an restore from the 21'st to my second host, which is running fine. And then we'll have to do file level restores from there....
For the DC going to have to bring in our MSP.....
F**** [moderated] XenServer why do you hate me so much.
Why has my original XS host run fine (literally like a f***** [moderated] dream for 2 years) and these two hosts are giving me issues....
what the f**** [moderated]!
