Another kernel panic after preupgrade

oekopez at gmx.de oekopez at gmx.de
Thu Nov 11 20:10:34 UTC 2010


> > The old F13 kernel, which are booting partly but failing with some
> > graphic card problems include root hd(0,0), also. 
> 
> If the old root was hd(0,0) then preupgrade should leave your root
> as hd(0,0).
> 
> If you follow Joe's suggestion about running fdisk from a live CD, can
> you also show the contents of your /etc/grub.conf and /etc/fstab.
> 
> > After reboot the
> > upgrade process failed upgrading one package
> 
> I interpret this a meaning that all the packages were downloaded, but
> after it asked you to reboot and you did, it started the upgrade but
> failed part way through.
> 
> This is a likely cause of your problem.  Do you remember the package
> that failed? Or any error message preupgrade might have printed at the
> time of failure?  It sounds like your system was in the middle of
> upgrading and hung. Is that true?  If that is the case, it gives a
> reason for your problem. Is it possible you ran out of disk space for
> the upgrade?  It takes almost twice as much room because it has to
> store two versions of everything before upgrading.
> -- 
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

To confirm your questions: Yes, the upgrade failed in the middle of the reboot / upgrade process. The package was a parallel data viewer (I think paraview) which I installed rather out of curiosity. After it failed I had not written down any messages, since I didn't expect the whole system to be killed if a single unused application has problems! I don't believe in disk full problems, but I can't be sure, since I am not able to mount sda2. (see below after fdisk output) 

# fdisk -l
[root at localhost liveuser]# fdisk -l

Disk /dev/sda: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              64       30395   243627008   8e  Linux LVM

Disk /dev/sdb: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008e400

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       30394   244139773+  83  Linux

Disk /dev/dm-0: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

Disk /dev/dm-3: 187.3 GB, 187334393856 bytes
255 heads, 63 sectors/track, 22775 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-3 doesn't contain a valid partition table

Disk /dev/dm-4: 8422 MB, 8422162432 bytes
255 heads, 63 sectors/track, 1023 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-4 doesn't contain a valid partition table

# cat /etc/grub.conf
cat: /etc/grub.conf: No such file or directory

# cat /etc/fstab 
/dev/root  /         ext4    defaults,noatime 0 0
devpts     /dev/pts  devpts  gid=5,mode=620   0 0
tmpfs      /dev/shm  tmpfs   defaults         0 0
proc       /proc     proc    defaults         0 0
sysfs      /sys      sysfs   defaults         0 0

But this is the live-cd!
# mkdir sda1
# mount /dev/sda1 sda1
# ls sda1
config-2.6.33.3-85.fc13.x86_64         lost+found
config-2.6.34.7-56.fc13.x86_64         memtest86+-4.10
config-2.6.34.7-61.fc13.x86_64         System.map-2.6.33.3-85.fc13.x86_64
config-2.6.35.6-48.fc14.x86_64         System.map-2.6.34.7-56.fc13.x86_64
efi                                    System.map-2.6.34.7-61.fc13.x86_64
elf-memtest86+-4.10                    System.map-2.6.35.6-48.fc14.x86_64
grub                                   upgrade
initramfs-2.6.33.3-85.fc13.x86_64.img  vmlinuz-2.6.33.3-85.fc13.x86_64
initramfs-2.6.34.7-56.fc13.x86_64.img  vmlinuz-2.6.34.7-56.fc13.x86_64
initramfs-2.6.34.7-61.fc13.x86_64.img  vmlinuz-2.6.34.7-61.fc13.x86_64
initrd-plymouth.img                    vmlinuz-2.6.35.6-48.fc14.x86_64

# mkdir sda2
# mount /dev/sda2 sda2
mount: unknown filesystem type 'LVM2_member'

Does this make sense to you?

Cheers, and already thanks a lot,

Philipp
-- 
GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit 
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl


More information about the users mailing list