Displaying 3 results from an estimated 3 matches for "rdosshel".
Did you mean:
rdosshell
2015 Dec 29
2
Centos 7, grub2-mkconfig, unsupported sector
..., I get back from vacation, and three CentOS 7 boxes didn't come up
this morning (my manager and the other admin did the update & reboot).
On these three - but *not* another one or two, and I don't think those
others are Dells, they're supermicro's - the 327 kernel fell into the
rdosshell, I guess. I finally got one the three up by going back to the
228.14 kernel.
Now, after googling and finding the CentOS bugzilla, 0009860, that
referenced the upstream bugzilla, I applied the workaround discussed in
it, Adding initcall_blacklist=clocksource_done_booting to
GRUB_CMDLINE_LINUX i...
2015 Dec 29
0
Centos 7, grub2-mkconfig, unsupported sector [followup]
...cation, and three CentOS 7 boxes didn't come up
> this morning (my manager and the other admin did the update & reboot).
> On these three - but *not* another one or two, and I don't think those
> others are Dells, they're supermicro's - the 327 kernel fell into the
> rdosshell, I guess. I finally got one the three up by going back to the
> 228.14 kernel.
>
> Now, after googling and finding the CentOS bugzilla, 0009860, that
> referenced the upstream bugzilla, I applied the workaround discussed in
> it, Adding initcall_blacklist=clocksource_done_booting...
2016 Jan 01
1
Centos 7, grub2-mkconfig, unsupported sector [followup]
...e CentOS 7 boxes didn't come up
>> this morning (my manager and the other admin did the update & reboot).
>> On these three - but *not* another one or two, and I don't think those
>> others are Dells, they're supermicro's - the 327 kernel fell into the
>> rdosshell, I guess. I finally got one the three up by going back to the
>> 228.14 kernel.
>>
>> Now, after googling and finding the CentOS bugzilla, 0009860, that
>> referenced the upstream bugzilla, I applied the workaround discussed in
>> it, Adding initcall_blacklist=cloc...