[opensuse-factory] systemd status in Factory : WAIT BEFORE UPGRADING TO CURRENT FACTORY
Hi all, as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade. Those bugs are due to both systemd and udev being moved to /usr. What does it means for packagers : - systemd will continue to check its .service from /lib/systemd/system, in addition to /usr/lib/systemd/system (and /etc/systemd/system) but packagers should change their package to use the new location for Factory (an rpmlint rule to detect that will be enabled soon) - udev will only check /usr/lib/udev/rules.d. The udev package has been modified to migrate /lib/udev/ to /usr/lib/udev and replace /lib/udev by a symlink to /usr/lib/udev. So, packages installing rules in /lib/udev should still be ok but they should be fixed to use the new rules (I've fixed all known broken packages in Factory already). Again, an rpmlint rule for this will be enabled soon in Factory - RUN+="socket:..." rules are not longer supported by udev 195. The only remaining package using it is multipath and Hanne is fixing it. Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon. Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION. Thanks. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Frederic Crozat <fcrozat@suse.com> [11-05-12 05:43]:
as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade.
Those bugs are due to both systemd and udev being moved to /usr.
Yes, resulting in a non-bootable system :^(
What does it means for packagers :
What does it mean for testers who have attempted upgrade before your announcement?
Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon.
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit :
* Frederic Crozat <fcrozat@suse.com> [11-05-12 05:43]:
as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade.
Those bugs are due to both systemd and udev being moved to /usr.
Yes, resulting in a non-bootable system :^(
What does it means for packagers :
What does it mean for testers who have attempted upgrade before your announcement?
Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon.
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me). Otherwise come on irc (#opensuse-factory) for getting help. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Frederic Crozat <fcrozat@suse.com> [11-05-12 09:24]:
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit : ...
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me).
Otherwise come on irc (#opensuse-factory) for getting help.
Machine is not available atm, but will try and, if needbe, see you on irc. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [11-05-12 09:35]:
* Frederic Crozat <fcrozat@suse.com> [11-05-12 09:24]:
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit : ...
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me).
Otherwise come on irc (#opensuse-factory) for getting help.
Machine is not available atm, but will try and, if needbe, see you on irc.
Did not work, will try IRC tonite or tomorrow. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 05/11/12 19:13, Patrick Shanahan escribió:
* Patrick Shanahan <paka@opensuse.org> [11-05-12 09:35]:
* Frederic Crozat <fcrozat@suse.com> [11-05-12 09:24]:
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit : ...
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me).
Otherwise come on irc (#opensuse-factory) for getting help.
Machine is not available atm, but will try and, if needbe, see you on irc.
Did not work, will try IRC tonite or tomorrow.
Upgrade should work now.. chroot to the broken system and run zypper dup. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-11-05 23:33 (GMT-0300) Cristian Rodríguez composed:
Upgrade should work now.. chroot to the broken system and run zypper dup.
Booted successfully to prior kernel, I started dup 22 minutes after you sent, 340 total packages. Filesystem installation failed yet again. Fresh initrd works. :-) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Cristian Rodríguez <crrodriguez@opensuse.org> [11-05-12 21:37]:
El 05/11/12 19:13, Patrick Shanahan escribió:
* Patrick Shanahan <paka@opensuse.org> [11-05-12 09:35]:
* Frederic Crozat <fcrozat@suse.com> [11-05-12 09:24]:
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit : ...
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me).
Otherwise come on irc (#opensuse-factory) for getting help.
Machine is not available atm, but will try and, if needbe, see you on irc.
Did not work, will try IRC tonite or tomorrow.
Upgrade should work now.. chroot to the broken system and run zypper dup.
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed: Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
yast bootloader doesn't err but reboot still fails with grub2 rescue command line. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
* Cristian Rodríguez <crrodriguez@opensuse.org> [11-05-12 21:37]:
El 05/11/12 19:13, Patrick Shanahan escribió:
* Patrick Shanahan <paka@opensuse.org> [11-05-12 09:35]:
* Frederic Crozat <fcrozat@suse.com> [11-05-12 09:24]:
Le lundi 05 novembre 2012 à 09:01 -0500, Patrick Shanahan a écrit : ...
And how to recover? Or should I just wait for m1 and make a new install? I have system access via a live cd but initrd is trashed, and mkinitrd in a chroot fails noting missing device map and cannot find match for hd0.
Did you try running yast bootloader in the chroot (after bind mounting /dev, /sys and /proc in the chroot) ? It should be able to restore bootloader properly (at least it did for me).
Otherwise come on irc (#opensuse-factory) for getting help.
Machine is not available atm, but will try and, if needbe, see you on irc.
Did not work, will try IRC tonite or tomorrow.
Upgrade should work now.. chroot to the broken system and run zypper dup.
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition? Thanks, Michael
yast bootloader doesn't err but reboot still fails with grub2 rescue command line.
tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Michael Chang <mchang@suse.com> [11-06-12 04:13]:
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition?
/boot *is* on lvm. Install from m0 net cd, used suggested lvm install but not btfs. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 6 Nov 2012 18:06:54 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Michael Chang <mchang@suse.com> [11-06-12 04:13]:
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Not mkinitrd, update-bootloader :)
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition?
/boot *is* on lvm.
In this case you must embed GRUB2 core.img (so LVM driver is available to access /boot) and the only way to do it in GRUB2 is to install in MBR or on btrfs partition. You need enough space, classical 62 post-MBR sectors may not be enough.
Install from m0 net cd, used suggested lvm install but not btfs.
It would be nice if YaST understood GRUB2 rules and would not suggest bootloader location GRUB2 does not support. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
В Tue, 6 Nov 2012 18:06:54 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Michael Chang <mchang@suse.com> [11-06-12 04:13]:
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Not mkinitrd, update-bootloader :)
And a similar err, that ext2 doesn't support embedding.
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition?
/boot *is* on lvm.
In this case you must embed GRUB2 core.img (so LVM driver is available to access /boot) and the only way to do it in GRUB2 is to install in MBR or on btrfs partition. You need enough space, classical 62 post-MBR sectors may not be enough.
Install from m0 net cd, used suggested lvm install but not btfs.
It would be nice if YaST understood GRUB2 rules and would not suggest bootloader location GRUB2 does not support.
so what do I do. Reinstall?? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
В Tue, 6 Nov 2012 18:06:54 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Michael Chang <mchang@suse.com> [11-06-12 04:13]:
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Not mkinitrd, update-bootloader :)
And a similar err, that ext2 doesn't support embedding.
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition?
/boot *is* on lvm.
In this case you must embed GRUB2 core.img (so LVM driver is available to access /boot) and the only way to do it in GRUB2 is to install in MBR or on btrfs partition. You need enough space, classical 62 post-MBR sectors may not be enough.
Install from m0 net cd, used suggested lvm install but not btfs.
It would be nice if YaST understood GRUB2 rules and would not suggest bootloader location GRUB2 does not support.
so what do I do. Reinstall??
Just install GRUB2 in MBR: /usr/sbin/grub2-install /dev/sda (or what is your boot drive). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 10:29]:
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
so what do I do. Reinstall??
Just install GRUB2 in MBR:
/usr/sbin/grub2-install /dev/sda
(or what is your boot drive).
linux:/# /usr/sbin/grub2-install /dev/sda1 /usr/sbin/grub2-bios-setup: warning: File system `ext2` doesn't support /embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is /equired for RAID and LVM install. same/simmilar error ??? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Wed, 7 Nov 2012 13:49:22 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 10:29]:
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
so what do I do. Reinstall??
Just install GRUB2 in MBR:
/usr/sbin/grub2-install /dev/sda
(or what is your boot drive).
linux:/# /usr/sbin/grub2-install /dev/sda1
sda1 != sda
/usr/sbin/grub2-bios-setup: warning: File system `ext2` doesn't support /embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is /equired for RAID and LVM install.
same/simmilar error ???
tks,
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 14:21]:
В Wed, 7 Nov 2012 13:49:22 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 10:29]:
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
so what do I do. Reinstall??
Just install GRUB2 in MBR:
/usr/sbin/grub2-install /dev/sda
(or what is your boot drive).
linux:/# /usr/sbin/grub2-install /dev/sda1
sda1 != sda
It certainly is not and thankyou much. That did the job. Now running: Linux oSFact 3.6.0-rc7-1-desktop #1 SMP PREEMPT Tue Sep 25 20:30:44 UTC 2012 (91c0ddc) x86_64 x86_64 x86_64 GNU/Linux another question but another thread/subject. tks again -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Wed, 7 Nov 2012 17:46:25 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 14:21]:
В Wed, 7 Nov 2012 13:49:22 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 10:29]:
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
so what do I do. Reinstall??
Just install GRUB2 in MBR:
/usr/sbin/grub2-install /dev/sda
(or what is your boot drive).
linux:/# /usr/sbin/grub2-install /dev/sda1
sda1 != sda
It certainly is not and thankyou much. That did the job. Now running: Linux oSFact 3.6.0-rc7-1-desktop #1 SMP PREEMPT Tue Sep 25 20:30:44 UTC 2012 (91c0ddc) x86_64 x86_64 x86_64 GNU/Linux
OK, but the question is - how is your boot device set in YaST? Otherwise next time running update-bootloader you may get the same issue. bor@opensuse:~> grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION="" Empty loader location should default to MBR, unless there were some changes in factory recently. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2012-11-08 07:15 (GMT+0400) Andrey Borzenkov composed:
bor@opensuse:~> grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION=""
Empty loader location should default to MBR, unless there were some changes in factory recently.
I disagree about "should"[1]. First of all, it *should* never be empty, even though it seems it always is. Better it should not exist than be empty. Next, it should contain whatever loader location was selected during installation, and stay that way, unless post-installation the desired location was changed. [1] http://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Wed, 07 Nov 2012 22:34:17 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
On 2012-11-08 07:15 (GMT+0400) Andrey Borzenkov composed:
bor@opensuse:~> grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION=""
Empty loader location should default to MBR, unless there were some changes in factory recently.
I disagree about "should"[1].
Sorry for my English. I meant "is supposed to". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 22:17]:
В Wed, 7 Nov 2012 17:46:25 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 14:21]:
В Wed, 7 Nov 2012 13:49:22 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-07-12 10:29]:
В Tue, 6 Nov 2012 23:13:02 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrey Borzenkov <arvidjaar@gmail.com> [11-06-12 22:23]:
so what do I do. Reinstall??
Just install GRUB2 in MBR:
/usr/sbin/grub2-install /dev/sda
(or what is your boot drive).
linux:/# /usr/sbin/grub2-install /dev/sda1
sda1 != sda
It certainly is not and thankyou much. That did the job. Now running: Linux oSFact 3.6.0-rc7-1-desktop #1 SMP PREEMPT Tue Sep 25 20:30:44 UTC 2012 (91c0ddc) x86_64 x86_64 x86_64 GNU/Linux
OK, but the question is - how is your boot device set in YaST? Otherwise next time running update-bootloader you may get the same issue.
bor@opensuse:~> grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION=""
Empty loader location should default to MBR, unless there were some changes in factory recently.
osFact:~ # grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub2" LOADER_LOCATION="" tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2012-11-07 04:20, Andrey Borzenkov wrote:
/boot *is* on lvm.
In this case you must embed GRUB2 core.img (so LVM driver is available to access /boot) and the only way to do it in GRUB2 is to install in MBR or on btrfs partition. You need enough space, classical 62 post-MBR sectors may not be enough.
If the system was installed with a reasonably new util-linux, there will be 4095 sectors (when fdisk puts the start of the 1st partition at 2M). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2012/11/7 Andrey Borzenkov <arvidjaar@gmail.com>:
В Tue, 6 Nov 2012 18:06:54 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Michael Chang <mchang@suse.com> [11-06-12 04:13]:
2012/11/6 Patrick Shanahan <paka@opensuse.org>:
did so and upgrade was successfully installed. Did 2nd zypper dup and got new kernel but mkinitrd failed:
Not mkinitrd, update-bootloader :)
Perl-Bootloader: 2012-11-06 00:08:09 <3> pbl-0385.2 Core::RunCommand.1662: Error: Command '/usr/sbin/grub2-install --force --skip-fs-probe "(hd0,1)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
Did your /boot is in on lvm or raid partition?
/boot *is* on lvm.
In this case you must embed GRUB2 core.img (so LVM driver is available to access /boot) and the only way to do it in GRUB2 is to install in MBR or on btrfs partition. You need enough space, classical 62 post-MBR sectors may not be enough.
Absolutely correct.
Install from m0 net cd, used suggested lvm install but not btfs.
It would be nice if YaST understood GRUB2 rules and would not suggest bootloader location GRUB2 does not support.
Yes. In fact YaST installation doesn't support /boot on lvm, there's no proposed bootloader in this case and will display error message instead. This rule is shared with grub and we should change it as grub2 is ready and supports the scenario . Of course MBR will be the proposed location. I'm just curios how the installation could success, it should fail in YaST in the first place. :\ Thanks, Michael
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Frederic Crozat <fcrozat@suse.com> [2012-11-05 11:42]:
Hi all,
as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade.
Those bugs are due to both systemd and udev being moved to /usr.
What does it means for packagers : - systemd will continue to check its .service from /lib/systemd/system, in addition to /usr/lib/systemd/system (and /etc/systemd/system) but packagers should change their package to use the new location for Factory (an rpmlint rule to detect that will be enabled soon) - udev will only check /usr/lib/udev/rules.d. The udev package has been modified to migrate /lib/udev/ to /usr/lib/udev and replace /lib/udev by a symlink to /usr/lib/udev. So, packages installing rules in /lib/udev should still be ok but they should be fixed to use the new rules (I've fixed all known broken packages in Factory already). Again, an rpmlint rule for this will be enabled soon in Factory - RUN+="socket:..." rules are not longer supported by udev 195. The only remaining package using it is multipath and Hanne is fixing it.
Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon.
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Nov 5, 2012 at 11:37 AM, Guido Berhoerster <gber@opensuse.org> wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
How can someone possibly know that beforehand? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Claudio Freire <klaussfreire@gmail.com> [2012-11-05 15:43]:
On Mon, Nov 5, 2012 at 11:37 AM, Guido Berhoerster <gber@opensuse.org> wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
How can someone possibly know that beforehand?
E.g. replacing pm-utils is likely to break all packages installing hooks there as they are not run anymore. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Guido Berhoerster <gber@opensuse.org> [11-05-12 10:26]:
* Claudio Freire <klaussfreire@gmail.com> [2012-11-05 15:43]:
On Mon, Nov 5, 2012 at 11:37 AM, Guido Berhoerster <gber@opensuse.org> wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
How can someone possibly know that beforehand?
E.g. replacing pm-utils is likely to break all packages installing hooks there as they are not run anymore.
And, surely, someone tested for breakage (ie: busting initrd) before committing to factory????? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 05 novembre 2012 à 10:32 -0500, Patrick Shanahan a écrit :
* Guido Berhoerster <gber@opensuse.org> [11-05-12 10:26]:
* Claudio Freire <klaussfreire@gmail.com> [2012-11-05 15:43]:
On Mon, Nov 5, 2012 at 11:37 AM, Guido Berhoerster <gber@opensuse.org> wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
How can someone possibly know that beforehand?
E.g. replacing pm-utils is likely to break all packages installing hooks there as they are not run anymore.
And, surely, someone tested for breakage (ie: busting initrd) before committing to factory?????
Of course, not, I didn't spend weeks on getting systemd + udev 195 updated and tested before pushing to Factory... Bugs happen, despite all our efforts to minimize their occurrence, which is why there is Factory to try to find them before we do release. So, could we move back to something more productive, like fixing those bugs (and this will be my last mail on this topic, I prefer to spend my time in fixing your bugs than discussing about them..). -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Guido Berhoerster <gber@opensuse.org>:
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
Guido, I suggest you subscribe to the opensuse-commit mailing list; then you're informed about all checkins to Factory. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Dominique Leuenberger a.k.a DimStar <DimStar@openSUSE.org> [2012-11-05 15:57]:
Quoting Guido Berhoerster <gber@opensuse.org>:
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
Guido,
I suggest you subscribe to the opensuse-commit mailing list; then you're informed about all checkins to Factory.
I was thinking about something more specific which is relevant for other developers, e.g. stuff like udev paths moving around, systemd replacing partly pm-utils requiring adaptations. Filtering out the relevant bits and their implications from the .changes is not that straightforward. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 05 novembre 2012 à 15:37 +0100, Guido Berhoerster a écrit :
* Frederic Crozat <fcrozat@suse.com> [2012-11-05 11:42]:
Hi all,
as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade.
Those bugs are due to both systemd and udev being moved to /usr.
What does it means for packagers : - systemd will continue to check its .service from /lib/systemd/system, in addition to /usr/lib/systemd/system (and /etc/systemd/system) but packagers should change their package to use the new location for Factory (an rpmlint rule to detect that will be enabled soon) - udev will only check /usr/lib/udev/rules.d. The udev package has been modified to migrate /lib/udev/ to /usr/lib/udev and replace /lib/udev by a symlink to /usr/lib/udev. So, packages installing rules in /lib/udev should still be ok but they should be fixed to use the new rules (I've fixed all known broken packages in Factory already). Again, an rpmlint rule for this will be enabled soon in Factory - RUN+="socket:..." rules are not longer supported by udev 195. The only remaining package using it is multipath and Hanne is fixing it.
Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon.
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Can you regularly send a heads-up to opensuse-factory@ when submitting new systemd releases to Factory, ideally with a hint of what it possibly breaks?
I was planning to (and it wasn't supposed to break) but I failed due to too many things to do on my schedule.. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/05/2012 11:42 AM, Frederic Crozat wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Hi, I tried in a VM though. Installing systemd 195 kills process 1 (init) which indeed causes a panic: Installing: systemd-195-4.1 ....................................<100%> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQmhc4AAoJEL0lsQQGtHBJmpoQAIM0fH6eoSeKYPe0LuMCmHL0 g6w8VsM7AO7T8XNUXcmV1jLWpoFBdfK13HzTeWTE3t5T95sb4rh0TOwuJYcwiYJ3 WAt53+gICIq8vygCKeqYSmGoNdPRYnXRJSi3+3MCjOimO6W756wkzXaSCCphIupX 88O7l9b3e9u+fJN3JuJtZvsOP8wDe6EnpXwXScRvbWA7HLFayfj5+A27vb2b97Kq xcdYVDeuy6q6KmTRzw29ZmVw0CZFzD4uhcqfMqc2B2I3YJbUSgrW/AahxlQKumkC awoxEeO+Th34l38akjozqn3+5fqGo1S/AMsDwSBdoE4aRqViMZZ1RI7iBsaDCkv2 +ppxBADwYraFahkq4H736w8f8TmpdoFcLXdqEERFCraMuvcbeAtJkS9Ffbvug7te Z7q97ZGcVzfxFugZJ9Fo9w/rXmnUP2s5uXRqtqC8z5A4IRaeOmpSTR6h6cyRrufd /yMc2ee7wWdDB4VdT6jWt9MUsAOzywY734Db6LsPOieRrVdXJUWA8dhIV9zn+jdm lF9BCbpfWqXgrpVBQQc3pymx5teqC1xgK65dqdu0HgHA5vTPIhff7GaKOVttKRAD ALXT8vo3lP/vwZnURMUUydCDvh5MS+wIuWj5lNgc371XIBX/DAtKxkiWJSzBu3q8 OqAZ1yJX50YUCR/TYa/L =9nnh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (11)
-
Andrey Borzenkov -
Claudio Freire -
Cristian Rodríguez -
Dominique Leuenberger a.k.a DimStar -
Felix Miata -
Frederic Crozat -
Guido Berhoerster -
Jan Engelhardt -
Jiri Slaby -
Michael Chang -
Patrick Shanahan