FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 03-24-2008, 11:38 PM
"Chu Jeang Tan"
 
Default Boot issue after changing m/b

After upgrading to a new CPU/mb, I've transferred my two harddrives
over, attached to IDE 1 master and slave (in the same order).

Booting into FC8 shows the following error
mount: could not find filesystem '/dev/root'

I've tried editing grub parameters by providing root=/dev/sda2
(also tried hda2 and other combos) and getting the same error.

I'm using FC8's kernel /boot/vmlinuz-2.6.24.3-34.fc8 , there should
not be an issue with lack of drivers?

Any tips and directions towards solving this?

The new mother board has 1 EIDE and 4 SATA, of which only the EIDE is
loaded with the two harddisks.

I'm waiting to install a SATA dvd drive before I can boot in the rescue disk.

--
Chu Jeang Tan
chujtan@gmail.com

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-24-2008, 11:56 PM
Ian Chapman
 
Default Boot issue after changing m/b

Chu Jeang Tan wrote:


I've tried editing grub parameters by providing root=/dev/sda2
(also tried hda2 and other combos) and getting the same error.

I'm using FC8's kernel /boot/vmlinuz-2.6.24.3-34.fc8 , there should
not be an issue with lack of drivers?

Any tips and directions towards solving this?


Did you change the grub line from root=LABEL=/ ? If not, try that. Also
I believe when you install a kernel, the initial ramdisk is built with
drivers based upon what controllers you have installed in the system. If
you move the hard disk to another machine it may not contain the
appropriate drivers.


There may be easier ways of doing it, but one solution that's worked for
me in the past is to boot off the CD/DVD in rescue mode, chroot
/mnt/sysimage then uninstall the kernel with rpm and then reinstall it,
ideally the same version. It should then rebuild the initial ramdisk
with the appropriate drivers. Note, it used to depend on the value of
the scsi_hostadapter settings in /etc/modprobe.conf to decide what
modules to use. I'm not sure if it still does but it might be worth
setting them to appropriate drivers for your sata/ata controllers.


--
Ian Chapman.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 01:30 AM
"Chu Jeang Tan"
 
Default Boot issue after changing m/b

I'll try that after I've installed a cdrom drive... At the meantime,
is there anything I can do to get to command prompt?

Such as dropping to command prompt when ram disk is finished
executing, prior to mounting the actual file system?

On Mon, Mar 24, 2008 at 7:56 PM, Ian Chapman
<packages@amiga-hardware.com> wrote:
> Chu Jeang Tan wrote:
>
> > I've tried editing grub parameters by providing root=/dev/sda2
> > (also tried hda2 and other combos) and getting the same error.
> >
> > I'm using FC8's kernel /boot/vmlinuz-2.6.24.3-34.fc8 , there should
> > not be an issue with lack of drivers?
> >
> > Any tips and directions towards solving this?
>
> Did you change the grub line from root=LABEL=/ ? If not, try that. Also
> I believe when you install a kernel, the initial ramdisk is built with
> drivers based upon what controllers you have installed in the system. If
> you move the hard disk to another machine it may not contain the
> appropriate drivers.
>
> There may be easier ways of doing it, but one solution that's worked for
> me in the past is to boot off the CD/DVD in rescue mode, chroot
> /mnt/sysimage then uninstall the kernel with rpm and then reinstall it,
> ideally the same version. It should then rebuild the initial ramdisk
> with the appropriate drivers. Note, it used to depend on the value of
> the scsi_hostadapter settings in /etc/modprobe.conf to decide what
> modules to use. I'm not sure if it still does but it might be worth
> setting them to appropriate drivers for your sata/ata controllers.
>
> --
> Ian Chapman.
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>



--
Chu Jeang Tan
chujtan@gmail.com

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 03-25-2008, 04:25 PM
Ian Chapman
 
Default Boot issue after changing m/b

Chu Jeang Tan wrote:

I'll try that after I've installed a cdrom drive... At the meantime,
is there anything I can do to get to command prompt?

Such as dropping to command prompt when ram disk is finished
executing, prior to mounting the actual file system?


It might be possible, but I'm not aware of any way. Even if you could, I
doubt you'd be able to do much from such a limited environment, being
restricted to the following commands for example.


insmod
modprobe
nash
rmmod

There's other methods that would work, which wouldn't necessarily
require a CD/DVD drive being connected to the machine, but they are far
more involved and convoluted.


--
Ian Chapman.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 10:10 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org