Le dim 14/10/2007 à 15:43, Doug Purdy a écrit :
> Le dim 14/10/2007 à 05:41, David Timms a écrit :
> > Doug Purdy wrote:
> > > Fedora is installed on the second ATA drive in the machine. It was an
> > > NTFS disk but Fedora wouldn't install until I used fdisk and mk2fs with
> > > the book's Fedora Live CD and I created ext3 partitions which I had
> > > marked as type 83. Then anaconda did a uneventful full install.
> >
> > Which disk and partition is grub installed to ?
> >
> > Can you boot the cd to get into rescue mode ?
> > What partitions are where {fdisk -l} ?
> >
> > DaveT.
>
> It will take me a bit longer to answer the questions on grub but I can
> use the Negus F7 Live cd that I used to cut and paste the outputs above
> between the 2 computers via floppy.
>
> Thanks again for your reply Dave. I hope these details provide
> interpretable clues to the problem.
>
> One point, the computer rebooted 2x from disk without problem before the
> updates.
I can mount the NTFS drive and I can mount sdb2 if I don't specify the
filesystem type. That's where Grub is in a folder with the 2 kernel
config, initrd, systme.map and vmlinuz files. I haven't figured out how
to mount the sdb1 partition and the sdb3 LVM partition claims to be
mounted already although I don't know where to look for it. Maybe it
will mount if I try a link.
[root@localhost ~]# mount -t ext3 /dev/sdb1 /media/d2p1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[root@localhost ~]# dmesg | tail
SELinux: initialized (dev fd0, type vfat), uses genfs_contexts
floppy0: data CRC error: track 1, head 0, sector 1, size 2
floppy0: data CRC error: track 1, head 0, sector 1, size 2
end_request: I/O error, dev fd0, sector 36
floppy0: data CRC error: track 1, head 0, sector 1, size 2
floppy0: data CRC error: track 1, head 0, sector 1, size 2
end_request: I/O error, dev fd0, sector 36
fuse init (API version 7.8)
SELinux: initialized (dev sda1, type fuseblk), uses genfs_contexts
VFS: Can't find ext3 filesystem on dev sdb1.
[root@localhost ~]# mount /dev/sdb3 /media/d2p3
mount: /dev/sdb3 already mounted or /media/d2p3 busy
[root@localhost ~]# mount /dev/sdb2 /media/d2p2
[root@localhost ~]# mount /dev/sdb1 /media/d2p1
Failed to read last sector (390716801): Invalid argument
Perhaps the volume is a RAID/LDM but it wasn't setup yet, or the
wrong device was used, or the partition table is incorrect.
Failed to startup volume: Invalid argument
Failed to mount '/dev/sdb1': Invalid argument
The device '/dev/sdb1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
Here's grub
# 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 (hd1,1)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.22.9-91.fc7)
root (hd1,1)
kernel /vmlinuz-2.6.22.9-91.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
initrd /initrd-2.6.22.9-91.fc7.img
title Fedora (2.6.21-1.3194.fc7)
root (hd1,1)
kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
initrd /initrd-2.6.21-1.3194.fc7.img
title Other
rootnoverify (hd0,0)
chainloader +1
I wonder if it's worth all this work. I could just reinstall from the
Negus Fedora 7 dvd although would I not find myself in the same place
again after an update? What could be the source of the problem? I used
the disk check option when I partitioned.
Doug
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
