I have just tried to install opensuse 11.0. I selected the defaults for the disk partitioning as I wanted to retain opensuse 10.3 and a dos partition. Things seemed to be going fine until until we arrived at the bootloader stage again I left the defaults and got a message:
‘error 21 selected disk does not exist’
I did notice that the installation divided my small dos partition which was entirely fat32 and now approximately half of it is linux native which to me seemed a bit odd.
I now find that when the computer is turned on I get a blank screen and the no signal message and do not even get to the bios screen. I tried my grub boot cd with no effect.
The bios problem has been resolved now. The computer had not been used for some time, so I have left in turned on for a while and pressed reset from time to time and the bios has just come back so this does seem to be a battery problem.
Anyhow I have a pre boot screen that tells me that there is no operating system. I have put the live cd in the drive and this works ok. I have gone into the disk partitioning tool and all the partitions that I would expect are there just the problem with the shared fat 32 & linux native partition.
On 2008-08-02, oldcpu <oldcpu@no-mx.forums.opensuse.org> wrote:
>
> percy_vere_uk;1849815 Wrote:
>> Hi
>>
>> I have just tried to install opensuse 11.0. I selected the defaults for
>> the disk partitioning as I wanted to retain opensuse 10.3 and a dos
>> partition. Things seemed to be going fine until until we arrived at the
>> bootloader stage again I left the defaults and got a message:
That seems like a bit of a contradiction. The defaults are, of course,
rather prudent. Bot to suppose they would leave everything alone? The least
that procedure has to do (on most machines) is to reduce existing
partitions, to make room for another.
Allways read the list of proposed actions, before accepting it.
Why not boot the DVD, and look at the current situation, partition-wise?
Post the list.
>> ‘error 21 selected disk does not exist’
>>
>> I did notice that the installation divided my small dos partition which
>> was entirely fat32 and now approximately half of it is linux native
>> which to me seemed a bit odd.
>>
>> I now find that when the computer is turned on I get a blank screen and
>> the no signal message and do not even get to the bios screen. I tried my
>> grub boot cd with no effect.
> This looks to me like a hardware failure in your PC that has nothing to
> do with openSUSE.
Probably. Unless the bios resources where on a (hidden) partition that got
reduced, too.
–
The sand remembers once there was beach and sunshine
but chip is warm too
– haiku from Effector Online, Volume 1, Number 6
As I was not too concerned about keeping 10.3 and the dos partition on the hard drive I thought it would be a good idea
to re-format the hard drive and clean install 11.0 on the whole disk. This I have done but the outcome is the same as
before which is the install seems to go ok up to the point that it tries to install the boot manager, then I get the error:
‘grub>setup—stage2=/boot/grub/stage2 (hd0) (hd0,1)
error 21:Selected disk does not exist.
grub>quit’
I have then gone into the Expert Partitioner the output of which is printed below. I hope its legible as I can’t seem to get the formating right.
> As I was not too concerned about keeping 10.3 and the dos partition on
> the hard drive I thought it would be a good idea
> to re-format the hard drive and clean install 11.0 on the whole disk.
> This I have done but the outcome is the same as
> before which is the install seems to go ok up to the point that it
> tries to install the boot manager, then I get the error:
>
> ‘grub>setup—stage2=/boot/grub/stage2 (hd0) (hd0,1)
> error 21:Selected disk does not exist.
> grub>quit’
>
> I have then gone into the Expert Partitioner the output of which is
> printed below. I hope its legible as I can’t seem to get the formating
> right.
>
> Any advice please.
>
> percy
>
> …
> Device Size Type
> Mount Mount By Start End
>
> /dev/mapper/pdc_ejaabehfg 152.6GB BIOS RAID pdc_ejaabehfg
> 0 19928
> /dev/mapper/pdc_ejaabehfg_part1 1.9GB DM Raid
> /mnt/windows/C K 0 260
> /dev/mapper/pdc_ejaabehfg_part2 150.6GB DM Raid
> 261 19928
> /dev/mapper/pdc_ejaabehfg_part5 70.5MB DM Raid
> /mnt/boot K 261 269
> /dev/mapper/pdc_ejaabehfg_part6 2.0GB DM Raid
> swap K 270 531
> /dev/mapper/pdc_ejaabehfg_part7 20.0GB DM Raid
> /mnt K 532 3142
> /dev/mapper/pdc_ejaabehfg_part8 128.5GB DM Raid
> /mnt/home K 3143 19928
> /dev/sda 152.6GB Maxtor-6Y160MO
> 0 19928
> /dev/mapper/pdc_ejaabehfgp1 1.9GB DM
> /dev/mapper/pdc_ejaabehfgp2 150.6GB DM
> /dev/mapper/pdc_ejaabehfgp5 70.5GB DM
> /dev/mapper/pdc_ejaabehfgp6 2.0GB DM
> /dev/mapper/pdc_ejaabehfgp7 20.0GB DM
> /dev/mapper/pdc_ejaabehfgp8 128.5GB DM
> …
You might have warned us you where using RAID.
Sorry I can’t help you there, so far I’ve allways steered clear of it.
But I’m sure other people will be able to use that info to help you.
Good luck !
–
The sand remembers once there was beach and sunshine
but chip is warm too
– haiku from Effector Online, Volume 1, Number 6
How many partitions on your drive? The openSUSE libata implementation is limited to some number around 15, and it looks like you are very close to that number.
I had no idea I was using raid and the implications of doing so it was either put there by the OEM or because Win xp had been on this disk which I thought I had completely removed.
Anyhow I have now carried out a full disk dos format using the /u option (2.5 hours) and then re-installed suse 11.0, but just same bootloader problem as above same partitioning setup.
Soooooooooo I have just installed Fedora 9. It sailed through the installation no problems at all. I have kept 70GB of my disk back just in case in future someone can offer a solution because there clearly is a problem here.
I am still use suse 10.3 on my laptop and am not yet a fedora convert.
I just started my first steps with linux and I got the same problem:
Just after installing Suse11.0 you can enter the system, but when you shut down once, it doesnt find the OS any more.
My bios has a own boot-manager option. First it was activated and I thougth, that might be the problem, but I got the same behaviour with the deactivated boot-manager?!
I still think it could have something to do with this bios-option.
Do you have such a feature too?
You don’t have a RAID array. But I strongly suspect you have a RAID device on the motherboard which, when not activated for RAID, acts as a standard IDE controller. The Fedora install detected that device and loaded a driver for it. openSUSE also detected the device and initially loaded the driver (or it could not have mounted the disk), but ran into some problem later, possibly in the creation of the initrd. There are several ways this problem could be solved.