Bugzilla – Bug 117658
installer ( update from 9.1 Suse) to 10.0 the config scan fails on FSTAB , dev. names.
Last modified: 2005-10-13 12:42:30 UTC
sys: ASUS A7V600 3.2ghz , 512mb based system , with xp-pro, suse9.1 , 200mb HDD with 6 partitions. (both OS are solid stable) boot SUSE 10.0 RC1 DVD I can see it mess up as soon as it reports my , hard Disk as HDA hda1-9 but mine are hde1-9 ran the repair on 10 install ,it is happy with HDA and FSTAB despite the conflict. What is happening (i think( is that the boot cd os used HDA and then when it sees my Suse 9.1 FSTAB , it HALTS. THAT IS, No recomendations. This AMD Semperon system is very common ( VIA KT600 with IDE and SATA). if anyone needs more information let me know. just email me . I will be testing suse 10.0 RC1 on many machines this week. Old and new. thanks one and all. Jerry H. my fstab /dev/hde8 / ext3 acl,user_xattr 1 1 /dev/hde9 /usr ext2 acl,user_xattr 1 2 /dev/hde1 /windows/C vfat users,exec,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hde5 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hde6 /windows/E vfat users,exec,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hde7 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 /dev/sda /media/jaz vfat rw,noauto,user,exec 0 0 /dev/hdh /media/dvdrecorder iso9660 user,ro 0 0 /dev/hdg /media/cdrecorder iso9660 user,ro 0 0
I forgot to say, I was doing an UPDATE mode in SUSE 10.0 Install booted from DVD Suse Install disk.
Update from 9.1 to 10.0 is not supported, but this might be another problem... Thomas?
Not much to say without y2log files. There is code in place that should change fstab accordingly.
where are y2logs located, could not find them. find *y2log*.* fails. If i can find them I can attach them below. let me know. thanks
The files are located in /var/log/YaST2, just tar the whole directory with "tar cvfz y2log.tgz /var/log/YaST2" and attach y2log.tgz.
Created attachment 50763 [details] logs of install Update suse 9.1 to 10.0 RC1
Unfortunately the log does not contain the the update of the system. Without logs there is not much I can do.
i will re-install in the morning and re-post this log. as an attachment. Hopefully Yast will log the errors, I get every time on the screen, that is , can not proceed with HDE1 (fstab) and HDA1(install) format. I will post it before noon , tomorrow , here. hope this helps.
Thanks for your effort. When reading your last comment I am not any more sure what you really did. If you use the function "Read /etc/fstab" in expert partitions then I have to say that there is no support for reading /etc/fstab when disk names change between releases. If you do a real update from 9.1 to 10.0 all should be fine. Anyway if you attach the logs I will se more clearly what you did and what the problem was.
Created attachment 50966 [details] new log new log, run install 10.0 rc1 ,update, i get the error onthe screen that says hda is not same as fstab hde , says can NOT PROCEED. I tried to print screen and was unable to find a place to save it. It looks to me like the log file is incomplete and does not mention the error. So that is another bug , I guess. I have installed Suse 8.1 thru 9.1 on many systems.and find many that use high hd letters. especially in SATA and PATA mixed IDE environs. I am unsure on how to get the logs to view on this error? , good day
my new attached log is a log that I cut out of YaST2 log file , i deleted all the old 2004 logs on top to shorten the file and show only todays install 9-27-05. It would seem that RC1 is not compatible with drive letters called hde. this should be easy to recreate , I would hope. regards, jerry
The log file does not contain anything regarding disk detection or disk configuration at all. If you start an installation but do not finish it YaST2 logs are kept in ramdisk image. If you do not finish installation, you have to copy the content of /var/log/YaST2 manually to one of you partitions.
Jiri, could you have a look. This looks like one of the cases where a disk was named /dev/hde in SL 9.1 and is called /dev/hda now in SL 10.0 Are there any fixes after RC1 that this case is covered during update?
hello, thank you, thomas, Id forgotten that it was all in ramdisk. so I must copy the virtual disk to some where , but to where? I have a ton of resouces on this system, 6 HDD PATA parttions, floppy,thumbdrive,cdr- burner, dvd-r-burner,JAZ2, external USB drives, just to name a few. Does the installer support support a transfer or must I somehow open a console (?) and do a mount. Whouldnt the mount fail for the same bad FSTAB names? My guess (weak as it is) is that only floppy and PATA are supported during install mode. Hay , a new feature in Yast , log to floppy the log files. Wouldnt that be useful to the millions out there trying to communicate errors to authors. Ok, I know , it is only a dream. Thanks PS> I aM PLANNING TO INSTALL 9.2, 9.3 AND ALL VERSIONS UPTO 10.0 AS UPDATE TO SEE AT WHAT POINT IT FAILS.
I don't remember me doing any fixes which could affect this issue. The code which "translates" the device names (like the problem with SATA name change) has been there for quite a long time IMO.
Unfortunately the hwinfo file is not what I need, I need the filw from /var/log/YaST2. You can simply change to a console with a shell during installation by pressing Ctrl-Alt-F2. You can do the following: - start 10.0 installation and let it run up to the point where YaST2 shows the problems - switch to shell by pressing Ctrl-Alt-F2. - mount one of the partitions at /mnt with the following commands: find out wht nanme your disk has with new kernel you can find tis with "cat /proc/partitions" so your have tu use either /dev/hda8, /dev/sda8 or /dev/sdb8 for your former /dev/hde8 modprobe ext3 mount -t ext3 <device name> /mnt cp -av /var/log/YaST2 /mnt umount /mnt - abort installation, reboot into your SL 9.1 installation and attach the files copied onto your disk.
will DO, now. back in a moment. and Thanks for very good instructions. jerry
Created attachment 51160 [details] the image of the files during OS 10.0 RC1 install fails for my fstab hde8 versas hda8. fdisk -l shows , hda8 , id 83 , boot suse thanks again for help and perfect ins. i only had to change permission, POC.
Sorry, but the tgz does not contain any log file from the installation environment. Alle the files contained logs from the installed system and no log entry is newer than 27.9.05 about 9:30.
Comment on attachment 51160 [details] the image of the files during OS 10.0 RC1 install oops , wrong file, sorry see next attach
Created attachment 51164 [details] 2nd try, looks good, right date this time. this is the YaST2 logs during the installation of OS10.0 RC1 over 9.1 , update mode and FSTAB fails for dev name letters.
Ok, from the logs I can see that the mechanism to recognize changed disk names when updateing from older distributions is broken. The directory /var/lib/hardware/unique-keys is missing in installation environment. I will reassign this bug to Steffen Winterfeld who maintains the inst-sys and might be able to provide a fix for that.
Hi: I took same box, installed suse 9.3 over 9.1 update mode it failed for other reasons in Fstab . ( it autoeconverted the wrong wrong names too, hde1 to hda1 ,etc. so i converted the lilo to grub, then corrected the bad entry , ntfs versas fat32, using the auto repair. then it inslalled perfect , that is 9.3 then followed up with 10.0 RC1 and it didnt skip a beat, not only that USB is greatly enhanced now. looks very solid.
Created attachment 53935 [details] compressed iso with driver update
Jerry, you can use the above driver update CD. It will create the missing directory mentioned in comment 22. If things work as expected that should help with the device renaming. In any case I've added the directory in 10.1. HTH. If not, reopen.