[Bug 205724] New: Obsolete "Unable to Update" message URL
https://bugzilla.novell.com/show_bug.cgi?id=205724 Summary: Obsolete "Unable to Update" message URL Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ed.reed@aesec.com QAContact: jsrain@novell.com How I got here is a long and sad story - it involves an OpenSUSE 10.1 FCS system with a corrupted disk, and my attempts to rectify the problem by "updating" the software via YAST2. I'll give more detailed explaination of the background below. But my issue is that the error message I ultimately got included the advice that I needed to refer to an article at "http://portal.suse.com/sdb/en/2003/cn/fhassel_update_not_possible.html" (That "cn" might be an "en", but when I transcribed it I wrote "cn"). Said link no longer exists, as the sdb has been moved into a WIKI. But looking through the WIKI SDB pages for 2003, nothing obviously applies to my problem, so I'm reporting the stale link here, now. The function I was attempting to perform when I got the message was update installed system from the Installation CD No - I'm not overly surprised that what I tried to do failed - I'm kvetching about the stale link. Which is why this is a "minor" bug. Detailed sad story: 1) had an installed and supposely up-to-date OpenSUSE 10.1 FCS instance on a single processor (with hyperthreading enabled) Pentium 4 box, 1GB memory, 1.5TB of disk. 2) root partition was on a reiser partition that may have been resized (like I said, I'm not surprised there may have been problems). There was known to be evidence of corruption in the /opt directory, too, a reiserfs on software raid1 partition that had lost its mirror (I said it was a sorry tail). That partition had a file which, when you tried to copy, tar or cat it would lockup the processor in a tight loop - no panic, no dump, just lock up solid requiring a power reset to recover. 3) To try to fix this, I created a new partition on another disk, formatted this time with ext3 (I think my next set of troubles began here) and copied via tar the root partition (while in init level 1) to the new partition. I then tried (unsuccessfully) to figure out how to coordinate MBR and grub updates to point to the new disk (I didn't realize it needed to be a disk on one of the internal IDE controllers to work). So, I figured I'd reboot with the install CD and use that to try to fix things up. 4) of course, the SUSE CDs don't seem to work will with an ext3 boot disk - I don't think the installation/recovery kernels you provide include ext3 in the list of modules you have available in the kernel. So, when I DID get the system to attempt to boot from the ext3 root, the kernel paniced because it didn't have the ext3 drivers. 5) I figured the problem with #4 was that a new initrd needed to be created, that included ext3, and that the installation CD repair system might do that. So, I booted the installation CD, selected "fix installed system" and asked for it to autorepair the installation on the ext3 root volume. 6)The root resident data evidenced "problems". Specifically, when I tried to use the installation disk to auto-repair the system, the repair would fail with a segfault while trying to verify the installed packages (on the first package it tried). 7) So, I tried "update system" option instead. The installation got to the point of trying to mount the ext3 root partition and complained that it couldn't mount the root partition - I confess that I didn't write down the message (by this time panic was setting in) - the message seemed to suggest there was a conflict between the partition it was trying to mount (hda3, by this time) and what it was trying to do (something with hda2, which ought to have been the swap partition). That's when it advised me to see the article at the broken link identified above (http://portal.suse.com/sdb/en/2003/cn/fhassel_update_not_possible.html ) "And that's the truth". ttttttthhhhhppppppptttttttttt. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205724 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205724 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |locilka@novell.com ------- Comment #1 from fehr@novell.com 2006-09-21 01:42 MST ------- Reassigned to maintainer of yast2-update -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205724 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |ed.reed@aesec.com ------- Comment #2 from locilka@novell.com 2006-09-21 01:49 MST ------- Could you, please, try to get into the same state "Cannot update..." and attach YaST logs? http://en.opensuse.org/Bugs/YaST Let's see what's really the "problem". Thx -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205724 ed.reed@aesec.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ed.reed@aesec.com | ------- Comment #3 from ed.reed@aesec.com 2006-09-21 04:43 MST ------- Well, no, sorry. See the sad tale described in my original post - I have that machine back up and running and in production, now. To recreate this, I think I need to create a system with EXT3 root file system with OpenSuSE 10.1 and try to update it from the same OpenSuSE 10.1 CD. But - if you'd like to grep for the URL that includes "fhassel_update_not_possible", you might find the literal string that provided the bogus URL, at least, and that's really all I was reporting on. In the end, having encountered troubls with SuSE bootable cd support for ext3 file systgems, I reformated the root volume and started over. So, mark this abandoned if the grep doesn't show anything worth fixing. Sorry, Ed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205724 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #4 from locilka@novell.com 2006-09-22 02:39 MST ------- Ah, I see. That link must have been already removed from installation (10.2 and SLES 10 SP1). I'm afraid this cannot be fixed for 10.1 :( Anyway, thanks for reporting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com