Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (X11; U; SunOS 5.8 sun4u) Description of problem: I am trying to upgrade from Red Hat 7.1 to Red Hat 7.2. The upgrade fails consistently. A dialog pops up and displays this message: "One or more of the filesystems for your Linux sytsem was not unmounted cleanly. Please boot your Linux installation, let the filesystems be checked, and shut down cleanly to upgrade." All filesystmes were unmounted cleanly, I checked that multiple times. Note that my PC has a Jaz disk drive. It could be related. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Take a PC (probably one with a Jaz drive). 2. Install Red Hat 7.1 3. Upgrade to Red Hat 7.2 Additional info: This is what appears on the 4th console (Ctrl+Alt+F4) when the upgrade process fails: [...] <6>Device not ready. Make sure there is a disk in the drive. <4>sdb : READ CAPACITY failed. <4>sdb : status = 1, mesage = 00, host = 0, driver = 28 <4>Current sd00:00: sns = 70 2 <4>ASC=3a ASCQ= 0 <4>Raw sense data: 0x70 0x02 [...] <4>sdb : block size assumed to be 512 bytes, disk size 1GB. <6> sdb: I/O error: dev 08:10, sector 0 <4> unable to read partition table <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
If you don't have a disk in the Jaz drive does it succeed?
No, it does not suceed. I tried with and without a Jaz disk in the drive, I rebooted multiple times, ran chdisk. No result... The error messages in 4th console are normal. They are typical of a Jaz drive without a Jaz disk inside.
Please attach your /etc/fstab file.
This seems to be fixed in Red Hat 7.2. Anyway, here is the /etc/fstab, it shouldn't have changed since I was using Red Hat 7.1, although of course I can't tell for sure.
Created attachment 42616 [details] /etc/fstab after Red Hat 7.2 installation
Do not take the sentence "This seems to be fixed in Red Hat 7.2" into account, sorry. I thought this was a report about another bug. Again /etc/fstab should not have changed since Red Hat 7.1. I had saved my disk before upgrading to Red Hat 7.2 and copied/pasted the saved 7.1 system files to modify my 7.2 system files.
Would you please put the 'fsset.py' attached file on a ext2 floppy and boot the installers with 'updates' on the commandline, like 'linux updates', insert the floppy when asked, and when you get the message about dirty filesystems please hit CNTL-ALT-F3 and look for a message like: FS on <devicename> is dirty - cannot continue and tell me what that message contains for <devicename>?
Created attachment 42617 [details] fsset.py with debugging info about dirty filesystems
My error... sorry for the noise. The message from fsset.py is: FS on hda3 is dirty - cannot continue So one file system was corrupted after all: # fsck /dev/hda3 Parallelizing fsck version 1.23 (15-Aug-2001) e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 /dev/hda3 was not cleanly unmounted, check forced. ... Note however that /dev/hda3 is an old disk I don't use anymore now that I have SCSI disks. I had Red Hat 6.2 installed on it years ago and I hadn't actually mounted it for months. It's not even in /etc/fstab In short I wasn't even aware it still exists... Sorry again. Nevertheless the error message could be made more explicit by specifying the disk that has a problem. If not in the popup dialog, at least output a message in the 3rd console so that one knows which file system has the problem with Ctrl+Alt+F3. The new fsset.py file is actually perfect. Thank you for your time. Best Regards, Dimitri
msf, you can close this one if it's fixed. Do you want to change the error statement?
The device which is dirty is getting logged to tty3 now, which is somewhat better
A complete fix will be done in a future release.
Added new wording to dialog in CVS so that you get "The following devices were not cleanly unmounted. /dev/foo /dev/bar "
Time tracking values updated
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.