empty directories installed by fc5 x86_64
Toad
keepertoad at verizon.net
Tue Dec 12 15:49:35 UTC 2006
New attempted install of 64 bit fc5 results in
empty /boot, /dev, /home. /misc, /mnt, /opt, /proc, /selinux, /srv, /sys
and /net is totally missing (no such directory). Needless to say the
system does not boot properly.
Machine is asus 64 bit motherboard with two ide drives and one sata.
sda contains 64 bit CentOS 4.4 which is rock solid. hdb contains fc5 32
bit which likewise has no known significant issues. fc5 64 bit install
is on hda. hda is partitioned as follows.
[root at office keepertoad]# parted
GNU Parted 1.8.0
Using /dev/hda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: WDC WD1200JB-00GVA0 (ide)
Disk /dev/hda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 107MB 107MB primary ext3 boot
2 107MB 31.6GB 31.5GB primary ext3
3 31.6GB 33.7GB 2097MB primary linux-swap
4 33.7GB 120GB 86.4GB extended
5 33.7GB 120GB 86.4GB logical ext3
hda1=/boot
hda2=/
hda5=/home
mounting hda2 on /mnt/fc5-64 reveals the following.
[root at office keepertoad]# ls -l /mnt/fc5-64/dev
total 0
Same is true for other directories listed above. md5sum and media check
o.k. Downloaded and burned iso twice with same result. I did not
install grub on hda but manually entered data for this install in
grub.conf on sda. Attempted boot of fc5 64 bit on hda starts out fine
with proper kernel, *2054*, and shows proper version of nash 5.0.32 but
somehow switches to the CentOS 64 bit install on sda and boots it.
Here is my grub.conf.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/hda
default=3
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title CentOS-4 x86_64 (2.6.9-42.0.3.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-42.0.3.ELsmp.img
title CentOS-4 x86_64 (2.6.9-42.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-42.ELsmp.img
title Fedora Core x86_64 (2.6.15-1.2054)
root (hd1,0)
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5.img
title Fedora Core (2.6.18-1.2239.fc5smp)
root (hd2,0)
kernel /vmlinuz-2.6.18-1.2239.fc5smp ro root=/dev/VolGroup00/LogVol00
rhgb quiet
initrd /initrd-2.6.18-1.2239.fc5smp.img
title Fedora Core (2.6.16-1.2111_FC5smp)
root (hd2,0)
kernel /vmlinuz-2.6.16-1.2111_FC5smp ro root=/dev/VolGroup00/LogVol00
rhgb quiet
initrd /initrd-2.6.16-1.2111_FC5smp.img
Replacing root=LABEL=/1 with root=/dev/hda in the third title entry
results in kernel panic which may be consistent with all the empty
directories. I did RTFM and google LABEL but still not sure exactly how
it works.
Would appreciate any thoughts about why empty directories are installed
and how to resolve that issue.
Thanks in advance.
B.J. McClure
Fedora Core 5, Linux 2.6.18-1.2239.fc5smp athlon 09:07:54 up 30 min, 2
users, load average: 0.06, 0.05, 0.11
More information about the fedora-list
mailing list