Copying an rhel as 3 installation from a PowerEdge 2650 to a 2950 2007-04-17 - By Gene
Back
All,
Thanks for all of your responses! It turned out to be a simple thing,
although not so much to me. I recreated the initrd and was able to boot
successfully. I retried restoring the dumps from the other existing system,
installed the driver and recreated the initrd and it worked.
Thanks again!
-Gene
On 4/11/07, Gene <gene@(protected)> wrote:
>
> Kevin,
>
> It does have the correct e2label, and I have tried using /dev/sda7
> (which is what it should be) and /dev/sdb7, and couple more down that line.
> It's as though the system cannot find /dev/sda at all, which leads me to
> believe that the driver isn't loading.
>
> I should have indicated as much in my original e-mail, but thank you for
> taking the time to ask.
>
> To others that have responded,
>
> Thank you very much for all of the responses! I will check what you have
> suggested.
>
> -Gene
> gene@(protected)
>
>
> On 4/11/07, Kevin Jackson <kevin@(protected) > wrote:
>
> > Gene,
> > Is this not because you are specifying an e2label label for a device and
> > you haven't labelled it yet?
> >
> > Try editing the grub line to say: root=/dev/sda2 or wherever your root
> > partition is set.
> > When it has booted up (perhaps you do need to go down the rescue cd root
> > or single user mode (S) as this will aslo be specified in the /etc/fstab)
> >
> > Kev
> >
> > On 11/04/07, Tom Sightler < ttsig@(protected)> wrote:
> > >
> > >
> > > >
> > > > These systems use different RAID controllers for the boot disk.
> > > > Because of this I have to load a new driver/module (megaraid_sas).
> > > > But, it is not working. When I try to boot I get:
> > > >
> > > > VFS: Cannot open root device "LABEL=/" or 00:00
> > > > Please append a correct "root=" boot option
> > > > Kernel panic: VFS: Uname to mount root fs on 00:00
> > > >
> > >
> > >
> > --
> > Kevin Jackson RHCE
> >
> > --
> > Taroon-list mailing list
> > Taroon-list@(protected)
> > https://www.redhat.com/mailman/listinfo/taroon-list
> >
>
>
All,<br><br> Thanks for all of your responses! It turned out to be
a simple thing, although not so much to me. I recreated the initrd and
was able to boot successfully. I retried restoring the dumps from the
other existing system, installed the driver and recreated the initrd and it
worked.
<br><br> Thanks again!<br><br>-Gene<br><br><div><span class="gmail_quote"
>On 4/11/07, <b class="gmail_sendername">Gene</b> <<a href="mailto:gene@(protected)
.org">gene@(protected)</a>> wrote:</span><blockquote class="gmail_quote" style=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding
-left: 1ex;">
Kevin,<br><br> It does have the correct e2label, and I have tried using
/dev/sda7 (which is what it should be) and /dev/sdb7, and couple more down that
line. It's as though the system cannot find /dev/sda at all, which
leads me to believe that the driver isn't loading.
<br><br> I should have indicated as much in my original e-mail, but thank
you for taking the time to ask.<br><br>To others that have responded,<br><br>
Thank you very much for all of the responses! I will check what you have
suggested.
<br> <br>-Gene<br><span class="sg"><a href="mailto:gene@(protected)" target="
_blank" onclick="return top.js.OpenExtLink(window,event,this)">gene@(protected)</a
><br><br><br></span><div><div><span class="e" id="q_111e0c53f0db44e3_3">
<span class="gmail_quote">On 4/11/07, <b class="gmail_sendername">Kevin Jackson
</b> <<a href="mailto:kevin@(protected)" target="_blank" onclick=
"return top.js.OpenExtLink(window,event,this)">kevin@(protected)
</a>> wrote:</span></span></div><blockquote class="gmail_quote" style=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding
-left: 1ex;"><div><span class="e" id="q_111e0c53f0db44e3_5">Gene,<br>
Is this not because you are specifying an e2label label for a device and you
haven't labelled it yet?
<br><br>Try editing the grub line to say: root=/dev/sda2 or wherever your
root partition is set.<br>When it has booted up (perhaps you do need to go down
the rescue cd root or single user mode (S) as this will aslo be specified in
the /etc/fstab)
<br><br>Kev<span><br><br><div><span class="gmail_quote">On 11/04/07, <b class=
"gmail_sendername">Tom Sightler</b> <<a href="mailto:ttsig@(protected)"
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ttsig@(protected)</a>> wrote:</span><blockquote class="gmail_quote" style=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding
-left: 1ex;">
<br>><br>> These systems use different RAID controllers for
the boot disk.<br>> Because of this I have to load a new driver/module
(megaraid_sas).<br>> But, it is not working. When I try to boot I
get:<br>
>
<br>> VFS: Cannot open root device "LABEL=/" or 00:00<br>>
Please append a correct "root=" boot option<br>> Kernel panic: VFS
: Uname to mount root fs on 00:00<br>><br><br></blockquote></div>
</span>
<br>-- <br><span>Kevin Jackson RHCE<br>
</span><br></span></div><span class="q">--<br>Taroon-list mailing list<br><a
href="mailto:Taroon-list@(protected)" target="_blank" onclick="return top.js
.OpenExtLink(window,event,this)">Taroon-list@(protected)</a><br><a href="https:/
/www.redhat.com/mailman/listinfo/taroon-list" target="_blank" onclick="return
top.js.OpenExtLink(window,event,this)">
https://www.redhat.com/mailman/listinfo/taroon-list</a><br></span></blockquote>
</div><br>
</blockquote></div><br>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
