https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c2 --- Comment #2 from Maciej Pilichowski 2011-06-08 18:40:44 UTC --- * external CD (via USB) is not recognized either I restored the system luckily, so now I attach yast logs, from the point when I restored only cron. For all other lost souls hit by "quality software", here is how you restore the system: * insert installation CD in the drive * reboot * start installation * at the second stage, when the hardware is initialized go to console * mount your harddisk * mount CD * cp -av /your_cd_mount_point /your_harddrive/INSTALLCD * when done, eject CD, reboot * rpm -qa --last > installed_recently_rpms * find out all suspicious packages, first will be the kernel for sure * go to repositories management * disable all repositories * add local repo from HDD (the one you just installed) * accept, run software managemet * find all packages you selected, choose "update unconditionally" (in my case I also deleted packagekit, as after such update, I don't trust any updates anymore) * accept * reboot In my case, I get the system back. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c zj jia changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |jsuchome@novell.com |ovo.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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c5 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | --- Comment #5 from Maciej Pilichowski 2011-06-16 12:02:46 UTC --- It would mean installing patch, rebooting machine, checking if everything is OK, then another and another? Sorry, with second spare computer it would be possible, but with only main computer -- I cannot do this. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c7 --- Comment #7 from Maciej Pilichowski 2011-06-17 14:18:44 UTC --- Kernel... now I am thinking, is updating kernel related to altering boot partition? If yes, it might be culprit -- not the kernel, but the way it is updated. You see, normally I do NOT have boot partition mounted, and even it was mounted, it would be read-only. The whole process of updating went smooth anyway, and I was NOT asked to mount boot partition. Contrary when I was reverting the updates -- I was asked to mount it. I posted this report just after the problems was apparent, and now I check FAKE /boot "partition" (it is directory actually, nothing else). "not-mounted" is my file which reminds me that the partition is not mounted. You can see a lot of useless files, among others you see files marked Jun 8 -- the day of update. -rw-r--r-- 1 root root 2246829 Apr 26 21:02 System.map-2.6.37.6-0.5-desktop -rw-r--r-- 1 root root 120322 Apr 26 19:29 config-2.6.37.6-0.5-desktop lrwxrwxrwx 1 root root 27 Jun 8 16:28 initrd -> initrd-2.6.37.6-0.5-desktop -rw-r--r-- 1 root root 11626357 Jun 8 16:28 initrd-2.6.37.6-0.5-desktop -rw-r--r-- 1 root root 0 Mar 27 09:22 not-mounted -rw-r--r-- 1 root root 196504 Apr 26 21:18 symvers-2.6.37.6-0.5-desktop.gz -rw-r--r-- 1 root root 5294953 Apr 26 21:18 vmlinux-2.6.37.6-0.5-desktop.gz lrwxrwxrwx 1 root root 28 Jun 8 16:27 vmlinuz -> vmlinuz-2.6.37.6-0.5-desktop -rw-r--r-- 1 root root 4555328 Apr 26 21:03 vmlinuz-2.6.37.6-0.5-desktop -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c8 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |Bootloader AssignedTo|zypp-maintainers@forge.prov |jsrain@novell.com |o.novell.com | QAContact|qa@suse.de |jsrain@novell.com --- Comment #8 from Michael Andres 2011-07-06 13:01:21 CEST --- yes, in the zypp/history you find Perl-Bootloader messages indicating this problem when installing kernel-desktop: # Perl-Bootloader: 2011-06-08 16:27:30 ERROR: Core::ReadFiles: Failed to open /boot/grub/menu.lst # /boot directory is not mounted. If this is bad detection you can avoid it by 'export PBL_SKIP_BOOT_TEST=1' # warning: %postun(kernel-desktop-2.6.37.1-1.2.2.x86_64) scriptlet failed, exit status 1 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c9 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bluedzins@wp.pl --- Comment #9 from Steffen Winterfeldt 2011-07-07 13:51:11 CEST --- Well, without /boot a kernel update obviously can't work. But in comment 7 you mention someone asked you to mount it. Which program was that? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c11 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@novell.com AssignedTo|snwint@novell.com |lslezak@novell.com --- Comment #11 from Steffen Winterfeldt 2011-07-07 16:40:51 CEST --- I wasn't aware we have such a warning at all -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c13 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P2 - High Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | Severity|Minor |Major --- Comment #13 from Maciej Pilichowski 2011-07-08 12:27:01 UTC --- First of all let's straighten few things: * "unusual tweak" -- please give some statistics to back up "unusual", thanks * mounting partition -- there is /etc/mtab to check before doing any operation on partition, if it is mounted or not. This is not rocket science so please don't say, my setup is strange or unusual. This is Unix world * Yast is doing KERNEL update for Christ sake, if this is low priority operation so then what is high priority? Blindly going after non-existing files on non-existing (not-mounted) partition is terribly lack of imagination and terrible quality, I would not like to "accused" that it is my fault because I dared to unmount /boot partition

Um, so how would you update the kernel if /boot is not mounted or mounted in read-only mode?

"Dear user please mount /boot partition in read-write mode in order to update the kernel". Displaying messages is too hard?

And why do you have such setup?

Because it fit my needs.

That's really unusual and strange...

No, this is not strange. /boot partition for normal work is not needed at all. You can find a couple of reasons why it is wise to unmount it (and how to setup it) if you google for it.

I quickly went through all yast sources and I could not find any "not mounted" error, and in the logs I also didn't find anything. Could you be more specific? When exactly was the warning displayed? A screenshot would be very helpful...

a) I think there is problem with lack of the message, not with the message, so I would worry about the process which does NOT display it b) warning was displayed while restoring all selected rpms which I thought were causing the problems with the system c) screenshot would mean, repeating all the steps now -- which is pretty dangerous to my system, so sorry, but "no" for sure

Deltas contain only the difference from the original package to the updated version and thus cannot be used for downgrade (they don't contain the needed data) so in this case full RPMs are used. That's expected behavior.

I know, you asked what I did, so I explained.

(Decreasing the severity because of the unusual manual tweak...)

Setting it back, because of not statistically founded assumptions. Kernel is the core of the system, kernel update algorithm is lousy (every programmer will tell you that), incorrect update can cost user ALL the data and a lot of time. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c15 --- Comment #15 from Maciej Pilichowski 2011-07-08 13:47:07 UTC ---

I'd also say the setup is weird, at best.

http://www.linuxjournal.com/article/7743 (just an example) I have to write to LJ why they publish info about such weird setups then.

Anyway, if you say some program does already care about it, it would help if you narrowed down _which one_ that is. Maybe you could remember some more detail than just 'I downgraded somehow'.

Yeah, I remembered, and for the third time I write it -- Yast/Software Management. And I also remember and I WROTE IT (so please do not offend me) that I selected update unconditional in Yast/SM because I was downgrading packages.

Also, if you take this seriously, it's not about just /boot but any fs mounted somewhere that is touched by a new rpm.

I do take it VERY seriously and you are right, /boot partition is this case, but in general (and I wrote it just a few minutes before) there is /etc/mtab to check what partitions are mounted. Before file/partition operation program should always check if the target is available. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c17 Maciej Pilichowski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |WONTFIX --- Comment #17 from Maciej Pilichowski 2011-07-08 15:10:37 UTC --- WONTFIX? Why not, after all why I should care most? I am just a user. -- 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.