Dell PERC Question (Server Down)
-
@scottalanmiller said:
@BRRABill said:
@jleskovsky said:
Given that the issue appears to currently be resolved, I would still agree with Dell that this could easily be a one-off fluke. That being said, please keep and eye on it and please update this thread if anything unusual occurs with those drives. You can also e-mail me directly at [email protected] and I will be more than happy to in any way I canto get the situation resolved for you. Thanks!
OK, let's keep our fingers crossed and hope for the best. I will keep you (and ML) updated.
I did update the iDRAC on Friday and it did not require a reboot. Who knows ... maybe that did something.
Can't require a reboot, it is its own computer with its own cup, memory, firmware, etc. if you reboot the server the ilo or idrac do not reboot. They stay on even when the system is powered down.
Assuming the server has power.
-
Well, everything has been OK thus far. We shall see.
Gremlins, perhaps.
-
Is there any issue with updating any of the firmware/BIOS of the DELL server? Is there ever a chance that might mess with the co-operation between the EDGE drive and the server?
-
@BRRABill said:
Is there any issue with updating any of the firmware/BIOS of the DELL server? Is there ever a chance that might mess with the co-operation between the EDGE drive and the server?
While not directly related to drives - but sadly the answer is - Of course. In my case updating the iLo caused the fans in the system to spin up and down. But updating the firmware in a RAID card could add or remove a feature that the drive is unaware of and then have an issue. Is that that likely? Probably not - we don't see those kinds of problems on other systems when you update firmware on Mobo's and drives in general.
-
Well, this happened again today.
I think it is time to yank those drives.
-
@BRRABill said:
Well, this happened again today.
I think it is time to yank those drives.
That really sucks man
-
@MattSpeller said:
That really sucks man
It's a character builder, i say.
The thing that sucks is that I wasn't in the office, again, when it happened. Thank goodness for iDrac!
-
@BRRABill said:
@Dashrender said:
Wait - what? Why? Does xByte no longer believe in their SSDs?
I would not say that.
I'm not really sure WHAT is going on. I did ask for clarification as to what they think the issue is.
Now I just pray the thing stays up until I can get a new array in there. I'll probably going to start a "which hard drive thread" as well as a "how do i copy this XS instance" thread.
By following this guide if you're in any way similarly setup.
-
@DustinB3403 said:
By following this guide if you're in any way similarly setup.
I don't have it booting off USB.
I have a test XS set up that I could copy the VM to, then install the new disk array, then install XS onto the new array and copy the VM back. Other than it taking a while, is there any reason that wouldn't work well?
-
You have XS installed directly to the hardware, rather than an SD or USB? Seems a bit odd to configure it like that for the very issue you mentioned when posting above. Which is "how do you replicate your boot device?"
When you install it directly to the server hardware, it's difficult to protect from a buggard OS, or patch.
But on SD or USB you can always just keep a current version in your safe in case anything happens to the boot partition.
Is XS installed directly to the hardware?
-
@DustinB3403 said:
You have XS installed directly to the hardware, rather than an SD or USB? Seems a bit odd to configure it like that for the very issue you mentioned when posting above. Which is "how do you replicate your boot device?"
When you install it directly to the server hardware, it's difficult to protect from a buggard OS, or patch.
But on SD or USB you can always just keep a current version in your safe in case anything happens to the boot partition.
Is XS installed directly to the hardware?
+1, usb boot works a treat for hypervisors that are not made by microsoft
-
@DustinB3403 said:
Is XS installed directly to the hardware?
Yes, though I am starting to question that decision.
I'm sensing a feeling in the force...move that install to USB!
-
@BRRABill said:
@DustinB3403 said:
Is XS installed directly to the hardware?
Yes, though I am starting to question that decision.
I'm sensing a feeling in the force...move that install to USB!
Coolest part is that there's no need to even prep a spare one. If it dies you just install a clean one onto a fresh USB drive. All the actual config data / important shit is in your VM's. I do suggest you document what version/options etc you used just in case of brain fart during disaster recovery.
-
@MattSpeller said:
@BRRABill said:
@DustinB3403 said:
Is XS installed directly to the hardware?
Yes, though I am starting to question that decision.
I'm sensing a feeling in the force...move that install to USB!
Coolest part is that there's no need to even prep a spare one. If it dies you just install a clean one onto a fresh USB drive. All the actual config data / important shit is in your VM's
Well there is, for example if you have a software RAID (you really want those configurations in place). Otherwise the hardware raid controller would manage the array and you'd be in golden shape to just stand up a new hypervisor.
SD cards generally are more reliable over USB. But both are perfectly suitable.
-
@DustinB3403 said:
@MattSpeller said:
@BRRABill said:
@DustinB3403 said:
Is XS installed directly to the hardware?
Yes, though I am starting to question that decision.
I'm sensing a feeling in the force...move that install to USB!
Coolest part is that there's no need to even prep a spare one. If it dies you just install a clean one onto a fresh USB drive. All the actual config data / important shit is in your VM's
Well there is, for example if you have a software RAID
Pffffft no one does that
-
<throat clearing....> hmmm
-
So, here is my scenario...
I have this DELL server. There are two arrays in it.
Array1 is the troublesome SSD array. It is where XS is installed, and also where the VMs reside. This array need sto be replaced.
Array2 is the SATA array that came with the server. Two 7.2K drives in RAID1. (Originally purchased just to run Hyper-V, which I am now no longer using.)Is there a way to install XS to a USB, and boot the server off that USB and have it recognize the VMs that are currently on Array1? I could even copy them to Array 2 (is THAT possible) while I figure out what I am going to do purchasing new drives for an array.
-
I'm not sure if you could move them around on the arrays (there might be some way, I just don't know). I'd just export them to external media and import them once you have the new installation stood up.
-
I have a DELL T320.
Apparently it has an INTERNAL SD card. (Interesting from the articles I read, it appears to be a redundant internal SD card reader for hypervisor usage.) Though I did not purchase that with my server.
So I could try to acquire one (or install a thrid party SD card reader) or just use a USB stick.
Go with the USB stick?
-
@BRRABill said:
So, here is my scenario...
I have this DELL server. There are two arrays in it.
Array1 is the troublesome SSD array. It is where XS is installed, and also where the VMs reside. This array need sto be replaced.
Array2 is the SATA array that came with the server. Two 7.2K drives in RAID1. (Originally purchased just to run Hyper-V, which I am now no longer using.)Is there a way to install XS to a USB, and boot the server off that USB and have it recognize the VMs that are currently on Array1? I could even copy them to Array 2 (is THAT possible) while I figure out what I am going to do purchasing new drives for an array.
Xen is just linux underneight, so sure you can do this.. you'll likely need to do it while the VMs are turned off. If push comes to shove, you can do it a the linux command line with cp from one mount point to another.
