Le dim 14/10/2007 à 05:41, David Timms a écrit :
> Doug Purdy wrote:
> > I installed Fedora 7 from Christopher Negus' Fedora 7 and Red Hat
> > Enterprise Linux Bible book, left it a week, and then spent a few hours
> > trying to figure it out before I let it update. After the reboot it
> > complains of Inconsistent filesystem structure, offers two kernels and
> > "Other" in Grub but will only boot "Other." I don't see what is
> > inconsistent. Suggestions appreciated.
> >
> > Here's what it says:
> >
> > root (hd1,1)
> > Filesystem type is ext2fs, partition type is 0x83
> > kernel /vmlinuz-2.6.22.9-91.fc7 ro root=dev/VolGroup00/LogVol00 rhgb
> > quiet
> ? typo or missing / between = and dev /\
> ? did you mean to be using LVM {should be type 8e}
> ? did it run out of space on /boot
Thanks for your reply Dave.
Yes, the missing "/" is a typo.
I know next to nothing about LVM and just let anaconda do whatever it
preferred. My preference would be a /home partition to protect my data
during future upgrades but I need to learn how to save to cd/dvd and
that would be better protection.
I'm confused by your question "did it run out of space on /boot?" I
don't know how it would run out of space. I believe I made my original
Fedora 7 /boot partition much bigger than my FC2 /boot partition but I
can't find my records and anaconda might have changed it to whatever it
wanted - I believe I answered 'yes' to anaconda's question "Erase all
partitions and install Fedora?" Let's let the computer tell the tale.
Here is a copy of the output of fdisk -l and fdisk /dev/sdb with x then
p commands. I used the Negus Fedora 7 book's Live cd.
[root@localhost ~]# fdisk -l
Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4864 39070048+ 7 HPFS/NTFS
Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 5000 40162468+ 83 Linux
/dev/sdb2 5001 5013 104422+ 83 Linux
/dev/sdb3 5014 24321 155091510 8e Linux LVM
Disk /dev/dm-0: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 156.6 GB, 156699197440 bytes
255 heads, 63 sectors/track, 19050 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-2 doesn't contain a valid partition table[root@localhost
~]# fdisk /dev/sdb
The number of cylinders for this disk is set to 24321.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): x
Expert command (m for help): p
Disk /dev/sdb: 255 heads, 63 sectors, 24321 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 1 0 254 63 1023 63 80324937 83
2 00 254 63 1023 254 63 1023 80325000 208845 83
3 00 254 63 1023 254 63 1023 80533845 310183020 8e
4 00 0 0 0 0 0 0 0 0 00
>
> > [Linux-bzImage, setup=0x1e00, size=0x1d4854]
> >
> > Error 16: Inconsistent filesystem structure
> It doesn't understand the disk.
> Make sure the disk is logically sound with:
> - boot rescue cd or dvd with: linux rescue
> - don't mount your partitions
> - fsck -f /dev/sda1 (and 2 and so on)
Again, using the Live cd from Negus' Fedora 7 book (hopefully that would
produce the same answers as a rescue cd would?):
[root@localhost ~]# fsck -f /dev/sb1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext2: No such file or directory while trying to open /dev/sb1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
Unfortunately as I wrote above I don't have records of the superblocks
from when I set up the partitions if that is what fsck is referring to
and the disk was probably repartitioned by anaconda in any case.
>
> > Selecting either Fedora kernel just repeats the above.
> >
> > 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.
Doug
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
