Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.19-7.0.1 i686; Nav) Description of problem: When upgrading from 7.0 to 7.1 after choosing to Upgrade then choosing Next on the customize packages screen I get the traceback in the accompanying attachment: How reproducible: Always Steps to Reproduce: 1.upgrade from 7.0 to 7.1 cd, ftp, and nfs install 2.choose upgrade then select next at following screen Actual Results: window pops up saying there is a bug and report it to bugzilla with the traceback Expected Results: should have started the upgrade Additional info: The dmesg from the current boot is included in an attachment to give information about my system:
Created attachment 17748 [details] anaconda traceback
Created attachment 17749 [details] dmesg from current boot
Can you try booting with 'linux ide=nodma'? Does that help?
Using 'linux ide=nodma' gives the same result. I looked at the Alt-F4 log and get something like the following. This all happens before the graphical interface pops up and doesn't seem to go any further after the anaconda exception. Pretty normal looking up to here. Looks like scsi stuff is detected etc. <6>sdb: sdb1 <7>ISO 9660 Extenstions: RRIP_1991A <4>Unable to identify CD-ROM format <6>raid0 personality regestered as nr 2 <6>raid1 personality regestered as nr 3 <6>raid5: measuring checksumming speed ... some numbers/speeds ... <4>raid5: using function: p5_mmx (1168.00 MB/sec) <6>raid5 personality registered as nr 4 Then that's it except that the time that I recorded this, two of my disks were at maximal mount count and I was getting warnings about it like. <4>EXT2-fs: maximal mount count reached, ... I don't know what all the raid stuff is about. I have never explicitely included any raid support. On a normal boot I get a message like: autodetecting RAID arrays autorun ... ... autorun DONE. instead of all the details.
Can you boot into your 7.0 system and post the output of the 'mount' command. Also, 'fdisk -l /dev/hda' would be nice.
$ mount /dev/sda3 on / type ext2 (rw,usrquota) none on /proc type proc (rw) usbdevfs on /proc/bus/usb type usbdevfs (rw) /dev/sda1 on /sda1 type ext2 (rw) /dev/sda2 on /boot type ext2 (rw) /dev/sdb1 on /sdb1 type ext2 (rw,usrquota) /dev/hda2 on /hda2 type ext2 (rw,usrquota) none on /dev/pts type devpts (rw,gid=5,mode=620) walrus:/c1 on /nfs/walrus type nfs (rw,rsize=8192,wsize=8192,addr=129.79.225.52) $ fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 3739 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 510 4096543+ b Win95 FAT32 /dev/hda2 511 3739 25936942+ 83 Linux Also here is sda which is where the / (root) and /boot partitions are. fdisk -l /dev/sda Disk /dev/sda: 255 heads, 63 sectors, 2213 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 1 130 1044193+ 83 Linux /dev/sda2 131 132 16065 83 Linux /dev/sda3 133 2181 16458592+ 83 Linux /dev/sda4 2182 2213 257040 5 Extended /dev/sda5 2182 2197 128488+ 82 Linux swap /dev/sda6 2198 2213 128488+ 82 Linux swap
Ok, it looks like /dev/sda3 is your / partition. Do any of your other Linux partitions contain an /etc/fstab file? I'm curious if disconnecting the IDE hard drive would have any effect.
There are no other /etc/fstab files anywhere. I think I see the problem. I am having lilo install the boot loader on the IDE MBR boot=/dev/hda. I think I ended up doing this because I couldn't get it to work when I loaded it on /dev/sda. Can you verify that this is likely the problem without me messing with it first? What solution would you recommend in terms of the boot loader if this is the problem? Here is my lilo.conf: #disk=/dev/sda bios=0x80 #boot=/dev/sda boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=linux message=/boot/message image=/boot/linux-2.2.19 label=linux initrd=/boot/initrd-2.2.19-7.0.1.img read-only root=/dev/sda3 image=/boot/bzImage-2.2.19 label=linux3 read-only root=/dev/sda3 image=/boot/vmlinuz-2.2.19-7.0.1 label=linux2 # initrd=/boot/initrd-2.2.19-7.0.1.img read-only root=/dev/sda3 other=/dev/hda1 label="Windows 98"
No, there should be no problem with installing lilo to the MBR of the SCSI drive.
I disconnected the IDE drive and am still getting the exact same error when I try to upgrade from 7.0 to 7.1.
The problem could be that your /etc/lilo.conf file has the line: boot=/dev/hda but it sounds like /dev/sda is your root device. If you have disconnected the IDE drive, the line should be "boot=/dev/sda"
I was previously installing the boot loader on hda but changed it to sda before I disconnected hda (ie. I already added the "boot=/dev/sda" line in lilo.conf). I made sure I was able to boot with hda disconnected before I tried to do the upgrade without hda.
I have the same problem while upgrading from 6.2 to 7.1 (the same traceback). Here is my /etc/fstab: /dev/hdb3 / ext2 defaults 1 1 /dev/hdb1 /usr ext2 defaults,ro 1 1 /dev/hdb4 /home reiserfs defaults,nosuid,nodev 1 1 /dev/hda1 /mnt/DOS vfat user,noauto,rw 0 0 /dev/hdc /mnt/cdrom iso9660 user,noauto,ro 0 0 /dev/fd0 /mnt/floppy ext2 user,noauto 0 0 /dev/sda4 /mnt/zip vfat user,noauto 0 0 /dev/sda1 /mnt/zip vfat user,noauto 0 0 /dev/hdb2 none swap sw proc /proc proc defaults My partitions looks like this: Disk /dev/hda: 64 heads, 63 sectors, 621 cylinders Units = cylinders of 4032 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 621 1251904+ c Win95 FAT32 (LBA) Partition 1 has different physical/logical endings: phys=(619, 63, 63) logical=(620, 63, 63) Disk /dev/hdb: 128 heads, 63 sectors, 782 cylinders Units = cylinders of 8064 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 573 2310304+ 83 Linux /dev/hdb2 766 782 68544 82 Linux swap /dev/hdb3 574 701 516096 83 Linux /dev/hdb4 702 765 258048 83 Linux
As an experiment I installed 7.1 on a different partition. Unlike the upgrade attempts everything worked fine.
After editing my /etc/fstab I was able to upgrade from 7.0 to 7.1 with no problem. The original /etc/fstab was: /dev/sda3 / ext2 defaults,usrquota 1 1 # 15 G /dev/sda1 /sda1 ext2 defaults 1 0 # 1 G /dev/sda2 /boot ext2 defaults 1 2 # 16 M /dev/sda5 swap swap defaults 0 0 # 128 M /dev/sda6 swap swap defaults 0 0 # 128 M /dev/sdb1 /sdb1 ext2 defaults,usrquota 1 2 # 8.5 G /dev/hda1 /mnt/W98 vfat noauto 0 0 # 3.9 G /dev/hda2 /hda2 ext2 defaults,usrquota 1 2 #24.7 G /dev/fd0 /mnt/floppy ext2 owner,noauto 0 0 /dev/cdrom /mnt/cdrom iso9660 owner,noauto,ro 0 0 none /proc proc defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 herbie:/linux /nfs/herbie nfs noauto,rsize=8192,wsize=8192 0 0 walrus:/c1 /nfs/walrus nfs rsize=8192,wsize=8192 0 0 dugong:/ /nfs/dugong nfs noauto,rsize=8192,wsize=8192 0 0 Before I upgraded I removed the comments at the end of the entries and commented out the unneccesary partitions to give. /dev/sda3 / ext2 defaults,usrquota 1 1 #/dev/sda1 /sda1 ext2 defaults 1 0 /dev/sda2 /boot ext2 defaults 1 2 /dev/sda5 swap swap defaults 0 0 /dev/sda6 swap swap defaults 0 0 #/dev/sdb1 /sdb1 ext2 defaults,usrquota 1 2 #/dev/hda1 /mnt/W98 vfat noauto 0 0 #/dev/hda2 /hda2 ext2 defaults,usrquota 1 2 /dev/fd0 /mnt/floppy ext2 owner,noauto 0 0 /dev/cdrom /mnt/cdrom iso9660 owner,noauto,ro 0 0 none /proc proc defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 #herbie:/linux /nfs/herbie nfs noauto,rsize=8192,wsize=8192 0 0 #walrus:/c1 /nfs/walrus nfs rsize=8192,wsize=8192 0 0 #dugong:/ /nfs/dugong nfs noauto,rsize=8192,wsize=8192 0 0 I guess anaconda didn't like my original fstab file.
It could be that mid-line '#' characters in /etc/fstab don't get handled nicely by the installer.
I had some tab characters in my fstab, I solved the problem by replacing those with spaces.
I don't think that tab versus spaces should make a difference, but putting mid-line '#' (comment) marks will cause problems. I think that, as a general rule, comments should only be used at the beginning of the line in the /etc/fstab file.