Dell PERC Question (Server Down)
-
I was going to log into the iDRAC and get a screen there to show the difference, but for some reason it is not pulling an address..
-
You people need to quit making me work!
-
@JaredBusch said in Dell PERC Question (Server Down):
@scottalanmiller said in Dell PERC Question (Server Down):
Do you mean that the OMSA can't manage the PERC?
The iDRAC is not OMSA they are different.
The OMSA was in reference to managing via the Dom0.
-
@JaredBusch said in Dell PERC Question (Server Down):
@scottalanmiller said in Dell PERC Question (Server Down):
Right, using OMSA in the Dom0 should work fine for working with the PERC. Unless I've missed something.
Yes, but my point was you claimed to use iDRAC.
I claimed both, but as two separate means of doing it.
-
That is what I was saying, that the iDRAC is pretty powerless with storage.
I'll work on getting OMSA on the XS.
-
@scottalanmiller said
No, I missed it. How slow was it?
So is somewhat slow speed OK for booting/updating off USB2?
-
@JaredBusch said in Dell PERC Question (Server Down):
You people need to quit making me work!
And after a long drive!
So sorry!
-
@BRRABill said in Dell PERC Question (Server Down):
@scottalanmiller said
No, I missed it. How slow was it?
So is somewhat slow speed OK for booting/updating off USB2?
Sure, what difference does the boot speed make realistically?
-
@BRRABill said in Dell PERC Question (Server Down):
That is what I was saying, that the iDRAC is pretty powerless with storage.
Did my link about that not work?
-
@scottalanmiller said
Sure, what difference does the boot speed make realistically?
I was theorizing ... none.
And the initial update is a PITA, but that's a one time thing.
-
@scottalanmiller said
Did my link about that not work?
Oh ... OK I just took a look.
You do remember you are talking to Mr. GUI, right?
-
@BRRABill said in Dell PERC Question (Server Down):
@scottalanmiller said
Sure, what difference does the boot speed make realistically?
I was theorizing ... none.
And the initial update is a PITA, but that's a one time thing.
If it ads ten minuets or something, sure. That could be a conceivable issue for a lot of systems. That's a ten minute risk. But generally it's like an extra 10 - 60 seconds kind of thing. Hard to have that end up being a risk, especially when we are talking it only coming up during a pretty major event. It's not like an old server without virtualization that would reboot weekly. These tend to stay up for a season.
-
Well, over the weekend I got all the important data off this array, and this morning I TRASHED IT!
I unplugged all the drives, then re-plugged in all DELL-only drives.
The arrays built, initialized, and thus far seem fine.
I guess there is no way to test except actually putting the data back on there, so that will be the next step.
Oh, and prayer.
-
Wish you the best.
-
-
When I plugged the DELL drives in last week, two of the three of them failed.
Today, those same DELL drive, in the same slots, are all working fine.
I wonder if there really was something corrupted in the array because of the other drives. DELL mentioned that as a good possibility ... but is that really possible?
But so far it seems like the PERC and the backplane are working fine.
-
What's the latest on this cluster (pun intended.)
-
I have not put any more data back on there yet, but the server has been up (with the array intact) for 24 hours now. Seems to be no issues, but the array had no issues for months until I started using it in production, so we'll have to wait and see. (Assuming it was the extra activity that got it.)
-
@BRRABill said in Dell PERC Question (Server Down):
I have not put any more data back on there yet, but the server has been up (with the array intact) for 24 hours now. Seems to be no issues, but the array had no issues for months until I started using it in production, so we'll have to wait and see. (Assuming it was the extra activity that got it.)
Is the array actually mounted somewhere? I'd try hammering it for a bit. IE:
dd if=/dev/random of=/dev/array bs=4k count=1000000000will write 4gb of random stuff to the array.
-
As part of this discussion about booting off of USB, I decided that since I needed to redo my entire XS installation anyway, I would install to USB.
But as I was doing a little research, I found online people recommending against this, since XS (and other hypervisors, too, I'm not sure) writes a lot to the boot disk. The fear is that this constant writing with fry a USB stick that doesn't have the smarter controllers that SSDs have. I spoke with @scottalanmiller a little bit about this, and he said it made sense, and to definitely get the logs off there.
So my question is ... how many of you that boot off USB have had issues with your USBs not booting? Do you agree this might be an issue? (Yes, I know that you can clone another USB, but that;s not really the point.
)And how many of you that boot XS off USB are sending your logs elsewhere?
