HELP! My drives disappear in fdisk after chroot of install

Guest

I've installed/ran gentoo before on a different drive in my exact same system. Now, instead of bothering with repartitioning my system, I found an older 8.4g drive to devote to gentoo.

I went through the installation process exactly as I have always done following the guide.

After I:

chroot /mnt/gentoo
env-update
source /etc/profile

and complete the remaining steps, GRUB will never initialize. It will always say "Error 21: Drive does not exist" when trying to "root (hd3,0)" [which is my secondary slave drive, applying grub to the boot sector of the root partition so I can use the XP bootloader to get into XP or Gentoo].

More insteresting - if I "fdisk -l" BEFORE chrooting, every drive will apear (3 total). However, after I do the chroot process and get to the new install's prompt, an "fdisk -l" will be BLANK, and GRUB will see NOTHING(geometry hd3 does nothing, nor does geometry hd0).

Any tips? I'm baffled since it worked in this exact same system just months ago, sans the "new" drive I've put in.

neeyo · n00b Joined: 20 Jul 2002 Posts: 32

Didn't log in before - oops.

rac · Posted: Sat Jul 20, 2002 6:02 am Post subject:

Are you sure /proc is mounted in the chrooted environment?
_________________
For every higher wall, there is a taller ladder

neeyo · n00b Joined: 20 Jul 2002 Posts: 32

Yep... here's the entire process I do from the first prompt after booting from the cd.

modprobe de4x5 - NIC
dhcpcd eth0 - NIC config

[fdisk -l works perfectly here]

mkdir /mnt/gentoo
mkdir /mnt/gentoo/boot
mount /dev/hdd3 /mnt/gentoo
mount /dev/hdd1 /mnt/gentoo/boot
mount -o bind /proc /mnt/gentoo/proc

chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile

[fdisk -l is now blank]

rac · Posted: Sat Jul 20, 2002 6:56 am Post subject:

And a really silly question, which I'll ask because I just can't get it out of my head - no chance it could be a jumper problem, right? Like two drives on that channel that both think they're slaves? It would seem that were that the case, you'd have problems everywhere, but...

Is there any change in /proc/ide? Can you see your drives in there? If you have strace available in the chrooted environment, does a comparison of

Darkstar · n00b Joined: 19 Jul 2002 Posts: 30

I'm having the exact same problem. Mylex DAC960 raid card and 4 scsi drives. I see /dev/rd/disc0/part1, part2 and part3 before and nothing after.

neeyo · n00b Joined: 20 Jul 2002 Posts: 32

Here's a 'ls -R' of my /proc from INSIDE my chrooted installation:

drizzt · Guru Joined: 21 Jul 2002 Posts: 428

I think you should exchange the order of your second mkdir command and your first mount command because your are 'overmounting' your /boot mountpoint and it will disappear....

Here is the (i think and it works for me) correct order:
mkdir /mnt/gentoo
mount /dev/hdd3 /mnt/gentoo
mkdir /mnt/gentoo/boot
mount /dev/hdd1 /mnt/gentoo/boot
mount -o bind /proc /mnt/gentoo/proc
and so on...
porbably this helps....

guest · Guest

I am having the exact same problem as Darkstar.

/dev/rd/disc0/part1 =/boot
/dev/rd/disc0/part2 =swap
/dev/rd/disc0/part3 =/

there is now /dev/rd/c0d0 listed although modprobe DAC960 refers to it

chroot /mnt/gentoo /bin/bash
grub
grub> root (hd0,0) no device
grub> root (hd0) no device
grub> device (hd0) /dev/rd/disc0/part1 no device
quit
alt-f2, enter, mkdir /mnt/gentoo/dev/rd, mount -o bind /dev/rd /mnt/gentoo/dev/rd
alt-f1
grub
grub> root (hd0,0) no device
grub> root (hd0) no device
grub> device (hd0) /dev/rd/disc0/part1 (ok)
grub> root (hd0) using all filesystem available
grub> setup (hd0) 17 : Cannot mount selected partition
quit

/me_fumes
/me_pulls_hair
/me_pulls_out_gun
/coworker_takes_gun_away
/me_kicks_coworker
/coworker_shoots_me_in_foot
/me "Ouch!"

Guest · Posted: Thu Aug 01, 2002 4:43 pm Post subject:

I can tell you away to get around this temporarily, but I must warn you, it involves floppies. /bleah

(posted the long silly guest post).

make a grub boot disk
mke2fs /dev/fd0
mount /def/fd0 /mnt/floppy (with chrooted install)
cp -R /boot/grub /mnt/floppy
grub
grub> root (fd0)
grub> setup (fd0) (on or two errors, no biggie)
grub> quit
unmount all your good stuff & reboot with floppy in
floppy will give you a prompt for the grub command line
type kernel (hd0,0)/boot/bzImage hit enter
should be all good.

this'll get you by till some smart person figures out wt heck is up with this.

you may need to have automount dev-fs in the kernel for this to work (and I donot use modules for any of this, take note).

Guest · Posted: Fri Aug 02, 2002 1:27 pm Post subject:

ebichu · Posted: Fri Aug 02, 2002 3:19 pm Post subject:

hd3 isn't always the secondary slave drive. It definitely depends which drive the BIOS booted from and may depend on how many other hard disks you have installed. Whichever HD the BIOS booted from will be hd0 (unless you've remapped it in some bootloader).
_________________
Ebichu wa chiizu ga daisuki dechu!

hielvc · Posted: Fri Aug 02, 2002 4:59 pm Post subject:

Is /dev/hdc a cdrom? Grub would not count it. So you would use "root (hd2.0)" [ 3rd harddrive] Also check your bios setup for hdd, you would want LBA on.

hielvc