[opensuse] HEADS UP! for the adventurous
Milestone 0 if openSUSE 13.2 is now available but be VERY careful if you decide to install it on a multi-boot system! Your mileage may vary of course but for me it was a disaster. I downloaded the KDE Live iso and (just for a change :-) ) it actually booted into Live mode. So I decided to be very brave and actually install it. I did this on a laptop which already has 13.1 installed but I had left space to be able to install at least 2 more OSs if I chose to. I chose to install 13.2 M0 in one of the empty partitions. The installation went fine until it came to the first "reboot your computer" which is when the wheels fell off :-( . The reboot saw that there were multiple systems installed and.....went braindead and decided that it couldn't boot into any and so the whole lot defaulted to the laptop's built-in boot procedure (which knows nothing). Now I cannot boot into my existing 13.1 and, of course, 13.2 is not visible to complete the installation. I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 22 Mar 2014, Basil Chupin wrote:
The installation went fine until it came to the first "reboot your computer" which is when the wheels fell off :-( . The reboot saw that there were multiple systems installed and.....went braindead and decided that it couldn't boot into any and so the whole lot defaulted to the laptop's built-in boot procedure (which knows nothing). Now I cannot boot into my existing 13.1 and, of course, 13.2 is not visible to complete the installation.
What do you use as bootmanager? Is it a BIOS or EFI? Grub1, grub2, ...? What errors do you get? -dnh -- It's hard to be religious when certain people are never incinerated by bolts of lightning. -- Calvin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/03/14 17:54, David Haller wrote:
Hello,
On Sat, 22 Mar 2014, Basil Chupin wrote:
The installation went fine until it came to the first "reboot your computer" which is when the wheels fell off :-( . The reboot saw that there were multiple systems installed and.....went braindead and decided that it couldn't boot into any and so the whole lot defaulted to the laptop's built-in boot procedure (which knows nothing). Now I cannot boot into my existing 13.1 and, of course, 13.2 is not visible to complete the installation. What do you use as bootmanager? Is it a BIOS or EFI? Grub1, grub2, ...?
What errors do you get?
EFI is switched off so it is the BIOS which controls the boot process. I only use Grub2. And the error I get is, "Multiple active partitions" after which the only way out is to reboot the laptop (or press and hold the ON button). BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sun, 23 Mar 2014, Basil Chupin wrote:
On 22/03/14 17:54, David Haller wrote:
On Sat, 22 Mar 2014, Basil Chupin wrote:
The installation went fine until it came to the first "reboot your computer" which is when the wheels fell off :-( . The reboot saw that there were multiple systems installed and.....went braindead and decided that it couldn't boot into any and so the whole lot defaulted to the laptop's built-in boot procedure (which knows nothing). Now I cannot boot into my existing 13.1 and, of course, 13.2 is not visible to complete the installation. What do you use as bootmanager? Is it a BIOS or EFI? Grub1, grub2, ...?
What errors do you get?
EFI is switched off so it is the BIOS which controls the boot process. I only use Grub2.
And the error I get is, "Multiple active partitions" after which the only way out is to reboot the laptop (or press and hold the ON button).
Easy. Boot anything with 'fdisk' or 'gdisk'. The following is assuming a normal MBR, not a GPT partition table, but with gdisk, it's much the same (except that a protective GPT-MBR probably has no active partitions at all and I'm not sure if GPT even has the concept of an active partition). So: Use 'lsscsi' to find the device (sdX) you need to work on. Then: # fdisk /dev/sdX [..] Command (m for help): p ### you'll see two parts with * in ### the "Boot" column [..] Command (m for help): a ### toggle "active" flag on partition Partition number (1-x): 3 ### toggle that of the appropriate "wrongly" ### "active" partition Command (m for help): p ### you should see only one parts * in ### the "Boot" column, the one you ### boot (Winders) from Command (m for help): v ### verify Command (m for help): w ### write & quit # sync; sync # reboot Done. The problem is: I have no idea which partition should be active, as you've neglected to add the output of 'fdisk -l /dev/sdX' or somesuch (well, I did not ask, did I). BTW: do you remember a "makeactive" anywhere in the installation process (of the booting stuff)? That might be the root-cause. HTH, -dnh -- G'Kar [to Marcus]: "If you're going to be worried every time the universe doesn't make sense, you'll be worried every moment of every day for the rest of your life." -- Babylon 5, 4x02 - Whatever Happened to Mr. Garibaldi? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2014 06:15 AM, David Haller wrote:
Hello BTW: do you remember a "makeactive" anywhere in the installation process (of the booting stuff)? That might be the root-cause.
- a few words of gratitude : oS 13.1 LIVE on an usb stick is terrific rescue tool : ............. Start the rescue system. Find the disk root partition, then, assuming its hdxy (or probably sdxy): mount /dev/hdxy /mnt mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /mnt/dev chroot /mnt ....................... next : run yast & boot manager ............... best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 23/03/2014 03:18, Basil Chupin a écrit :
EFI is switched off so it is the BIOS which controls the boot process. I only use Grub2.
ok
And the error I get is, "Multiple active partitions" after which the only way out is to reboot the laptop (or press and hold the ON button).
I fear it's not the real problem, because AFAIR I already have had systems with several active partitions withj no problem. the active partition(*) are the one that are said to hold the boot system in windows. When grub is installed on an other place than MBR, the system have no way to know where if not set active. in "fdisk -l", for example, the active partitions are the ones with an "*". Easy to change in any fdisk (it's a toggle) to log into a faulty root system is a bit tricky, but I learned to do it some years ago and had to use it (to change root passwd) yesterday for the most recent time :-) boot rescue, it may not work is it's not the rescue disk of the installed system mount your root prefered partition on /mnt (for example), verify it's the good one (ls /mnt), then mount --bind the system folders (two dashes "--"): cd /mnt #important! mount --bind /proc proc mount --bind /dev dev mount --bind /sys sys using the keyboard history it's very fast then chroot . # don't forget the final dot. This mean I want to use the system located in ".", the present working directory. After that you are root in your installed (faulty) system. you can change any password with "passwd", launch YaST... Don't forget it's usually not possible to set as grub position a logical partition. If you don't have any windows, you can use the MBR jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 22/03/2014 04:28, Basil Chupin a écrit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch.
is this an EFI boot? if yes look at the bios jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, Am Samstag, 22. März 2014, 08:44:37 schrieb jdd:
Le 22/03/2014 04:28, Basil Chupin a écrit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch.
is this an EFI boot? if yes look at the bios
And if that doesn't help: Boot into rescue system, mount 13.1 and chroot into it. Reinstall bootlader. Greetings from Bremen hartmut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/03/14 19:35, Hartmut Meyer wrote:
Hi,
Am Samstag, 22. M�rz 2014, 08:44:37 schrieb jdd:
Le 22/03/2014 04:28, Basil Chupin a �crit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. is this an EFI boot? if yes look at the bios And if that doesn't help:
Boot into rescue system, mount 13.1 and chroot into it. Reinstall bootlader.
Greetings from Bremen hartmut
Having never used this 'chroot' I will probably have to spend some time experimenting on how to use it, but I will certainly try it before re-installing 13.1 (if need be) :-) . BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sun, 23 Mar 2014, Basil Chupin wrote:
On 22/03/14 19:35, Hartmut Meyer wrote:
Am Samstag, 22. M?rz 2014, 08:44:37 schrieb jdd:
Le 22/03/2014 04:28, Basil Chupin a ?crit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. is this an EFI boot? if yes look at the bios And if that doesn't help:
Boot into rescue system, mount 13.1 and chroot into it. Reinstall bootlader.
Having never used this 'chroot' I will probably have to spend some time experimenting on how to use it, but I will certainly try it before re-installing 13.1 (if need be) :-) .
Basically: # mount /dev/sdXY /mnt ### where /dev/sdXY is your /-dev for ### the "to be repaired" system, use ### lsssci/fdisk -l etc. to find the dev # mount --bind /dev /mnt/dev # mount --bind /proc /mnt/proc # mount --bind /sys /mnt/sys # cd /mnt # chroot /mnt [.. do stuff in the chroot like grub-install etc. ..] [in chroot]# exit [back in rescue] # umount /mnt/proc /mnt/sys /mnt/dev ### could be you have to split ### that up # sync; sync; ### just to be safe # umount /mnt And you should be done. HTH, -dnh --
Naja spiele ich halt wieder Frisbee mit der NT CD. Funktioniert nicht. Stürzt immer ab. -- Hans Pueschel in dasr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, Am Sonntag, 23. März 2014, 05:21:41 schrieb David Haller:
Basically:
# mount /dev/sdXY /mnt ### where /dev/sdXY is your /-dev for ### the "to be repaired" system, use ### lsssci/fdisk -l etc. to find the dev # mount --bind /dev /mnt/dev # mount --bind /proc /mnt/proc # mount --bind /sys /mnt/sys # cd /mnt # chroot /mnt [.. do stuff in the chroot like grub-install etc. ..]
Including: mount -a # to make sure the boot partition is mounted - if /boot is on a # separate partition
[in chroot]# exit [back in rescue] # umount /mnt/proc /mnt/sys /mnt/dev ### could be you have to split ### that up # sync; sync; ### just to be safe # umount /mnt
And you should be done.
Schöne Grüße aus Bremen hartmut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/03/14 15:21, David Haller wrote:
Hello,
On Sun, 23 Mar 2014, Basil Chupin wrote:
On 22/03/14 19:35, Hartmut Meyer wrote:
Am Samstag, 22. M?rz 2014, 08:44:37 schrieb jdd:
Le 22/03/2014 04:28, Basil Chupin a ?crit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. is this an EFI boot? if yes look at the bios And if that doesn't help:
Boot into rescue system, mount 13.1 and chroot into it. Reinstall bootlader. Having never used this 'chroot' I will probably have to spend some time experimenting on how to use it, but I will certainly try it before re-installing 13.1 (if need be) :-) . Basically:
# mount /dev/sdXY /mnt ### where /dev/sdXY is your /-dev for ### the "to be repaired" system, use ### lsssci/fdisk -l etc. to find the dev # mount --bind /dev /mnt/dev # mount --bind /proc /mnt/proc # mount --bind /sys /mnt/sys # cd /mnt # chroot /mnt [.. do stuff in the chroot like grub-install etc. ..] [in chroot]# exit [back in rescue] # umount /mnt/proc /mnt/sys /mnt/dev ### could be you have to split ### that up # sync; sync; ### just to be safe # umount /mnt
And you should be done.
HTH, -dnh
To you David and others, sorry if I haven't responded to your suggestions but will as soon as I am able. I haven't yet tried the suggestions given. The recovery of oS on the laptop has taken second priority for the moment because my wife wants a new kitchen so we have been 'frolicking' around with consultants, kitchen companies, appliance stores...... At day's end the laptop is the last thing I want to tackle :-) . BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/03/14 15:21, David Haller wrote:
Hello,
On Sun, 23 Mar 2014, Basil Chupin wrote:
On 22/03/14 19:35, Hartmut Meyer wrote:
Am Samstag, 22. M?rz 2014, 08:44:37 schrieb jdd:
Le 22/03/2014 04:28, Basil Chupin a ?crit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. is this an EFI boot? if yes look at the bios And if that doesn't help:
Boot into rescue system, mount 13.1 and chroot into it. Reinstall bootlader. Having never used this 'chroot' I will probably have to spend some time experimenting on how to use it, but I will certainly try it before re-installing 13.1 (if need be) :-) . Basically:
# mount /dev/sdXY /mnt ### where /dev/sdXY is your /-dev for ### the "to be repaired" system, use ### lsssci/fdisk -l etc. to find the dev # mount --bind /dev /mnt/dev # mount --bind /proc /mnt/proc # mount --bind /sys /mnt/sys # cd /mnt # chroot /mnt [.. do stuff in the chroot like grub-install etc. ..] [in chroot]# exit [back in rescue] # umount /mnt/proc /mnt/sys /mnt/dev ### could be you have to split ### that up # sync; sync; ### just to be safe # umount /mnt
And you should be done.
HTH, -dnh
Well, I finally found the necessary time to try out your and Hartmut's suggestions about recovering my existing and working 13.1 after trying to install 13.2 M0 on another partition on the laptop. All were failures - including using the Boot Rescue Disc which I found and used while playing around with Ubuntu some many months ago. I followed all the instructions given to the letter at least 3X just to make sure that I had not missed something but- alas, alack! the grub2 menu would not appear and instead I would get on the screen "Multiple active partitions", and "that's all folks". The only problem here was that, using fdisk (and even gdisk) there were NO active partitions to be seen! During this exercise I learnt that the HDD is formatted in GPT - the HDD originally had Windows 8 installed when I bought the laptop. But I had no problems in installing 13.1 after I zapped W8/8.1. 13.1 went right in, "just like Flynn", and worked perfectly. I then tried to install 13.2 M0 into an empty partition (deliberately created when I installed 13.1) and which is when the wheels fell off - as you would know from earlier posts. Following the above failures to restore the bootloader I decided that because I was getting nowhere and therefore had to re-install 13.1 what would happen if I did the following before re-installing 13.1.......... since 13.1 installed perfectly into the *FIRST* available partition[#] formatted in ext4 (ie SDA3) and attempting to install 13.2 into the *second* partition (ie SDA4) was a failure, what would happen if I now installed 13.2 M0 into the *first* partition (SDA3) and then later installed 13.1 into the second partition (SDA4)? So this is what I did - I installed M0 into SDA3 and it all went in without a hitch. Working perfectly thank you. (But I haven't yet tried to install 13.1 - which, I suspect, might bring back the whole nightmare.) Now, when installing 13.2 M0 I did get the message from the installer when using the Partitioner that grub2 will not work because there is no some partition which is necessary for GPT formatted HDDs - and I was asked if I still wanted to continue the installation without this special partition. I chose "Continue" and..... 13.2, as I said, was installed and working. I don't recall getting this message when I was installing 13.1. But my memory is not perfect. To pre-empt the person or persons who will no doubt post a reply here which will state something along the lines of, "Well you ought to know better and why didn't you create this special partition?!", I'll say this:- "I am a brainless Windows user who just heard about this great new system called Linux and openSUSE and I wanted to try it out and I was told to download an iso of openSUSE and install it - but during the installation it came up with this stupid statement that some stupid partition did not exist and that openSUSE therefore would not boot using some silly insect called grub2." Get the message? [#] Sda1 btldr (to hold bootloader for multiple systems) Sda2 Swap Sda3 openSUSE 13.1 (ORIGINALLY - now has 13.2 M0) Sda4 Spare for another OS Sda5 Spare for another OS Sda6 Data formatted in ext4 Sda7 Data1 formatted in ext4 The above is what the YaST Partitioner sees. Gdisk sees the above as Microsoft basic, Linux swap, EFI system, EFI system, Microsoft basic, Microsoft basic, Microsoft basic, respectively. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/03/14 18:44, jdd wrote:
Le 22/03/2014 04:28, Basil Chupin a �crit :
I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch.
is this an EFI boot? if yes look at the bios
jdd
See my response to David. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Basil Chupin -
David Haller -
ellanios82 -
Hartmut Meyer -
jdd