SUSE 9.1 boot disk problems

[ludwig1]

After unsuccessfully trying to install 9.1 from the ISO's ,I thought I'd try to do an ftp install from the boot disk. However, I’m getting the same problem that I had before with the ISO installs:


I put the boot disk in and this is what happens;
1. I get the welcome screen and then am asked how I want to boot ( installation, from the hard drive etc)
2. I choose ‘ installation’ and then it says its loading the linux kernel (which takes about 5 secs)
3. Then the system tries to boot with the option to press F2 to see what exactly is happening.
4.After 30 secs a list is displayed on the screen as if I had pressed F2 showing why the system can't boot.

The relevant bit is at the end where it says:


RAMDISK : compressed image found at block 0
crc error VFS cannot open root device "NULL" or unknown block(8,5)

Please append a correct "root"=boot option
Kernel panic :VFS unable to mount root fs on unknown-block(8,5)

I have burned the boot disk many times and still get the same result. Same thing with the ISO images.

I am wondering if it has something to do with the fact that I have a copy of Windows XP already on the HDD. In fact I have Windows XP on C, I have another NFTS partition on D (for storage) and I created a Linux ext3 partition prior to trying to install Suse 9.1 as well as a swap partition.

Could these partitions be causing the problems?

[Choozo]

I guess this is the same illegally obtained copy from your other - now locked - thread?

Having WinXP already installed (or any Win flavor) does not matter at all.

Have you tried an FTP install yet?

[ludwig1]

Have you tried an FTP install yet?

Have you read my post at all? :rolleyes:

[Choozo]

Shoot! ..... a lowercase ftp there that got garbled in my ugly Firefox fonts ..... :D

Anyway, existing Win installations should not stop you from installing any Linux flavor.
Did you make the boot disk from the CD's, or did you download a new boot image from one of the SUSE mirrors?

[ludwig1]

Hi,

I DL-ed the Boot image from a SUSE mirror.
In fact i've DL-ed several boot images from SUSE mirrors and burned them all with the same result.
I've also deleted the Linux ext3 and swap partitions.
Still no go.

BTW: SUSE 9.0 installs fine.

[ludwig1]

Also, checked the MD5sum for the boot iso and it's fine.

[ludwig1]

Hi Webwolf,

Yes, I chose manual install.
In fact I've tried all the options and still get the same result.

[ludwig1]

Initially I had a few partitions.But now I've deleted them all except the NTFS windows partition in an attempt to get Suse to load.

[ludwig1]

As I think I mentioned aerlier, I put Suse 9.0 cd 1 in and it began to install no problems.Same with RH9.

I did see on another forum some guy had a similar problem to mine, but no one posted a solution.

[ludwig1]

thanks for all your help, Webwolf.
Much appreciated.

[JohnT]

crc error This usually means a memory error of some sort or media error.. You might try passing "mem=<amt of ram>" at "boot". If that doesn't work try shifting or removing some of your ram modules. Check you media checksums...might be a bad burn.

[ludwig1]

My guess is it's a bad burn. I'm going to borrow a CDRW tomorrow and try and do another burn

[mdwatts]

Originally posted by ludwig1
Have you read my post at all? :rolleyes:

Great attitude when someone is attempting to assist you. :(

[ludwig1]

I take it you're using the word 'assist' sarcastically.
How on earth can anyone 'assist' you when they can't even be bothered to read your post properly cos they're so intent on trying to make some invalid point on illegal software.

Anyway, Mdwatts, thanks for your help.
It was really, really helpful to have that pointed out.
:rolleyes:

[JohnT]

He,he,....:D

[ludwig1]

JohnT: you (and a few other people) were right.
It was a bad burn...or to be more specific, a bad burner.
I think my burner must have lunched itself .It can burn data till the cows come home, but boot images it refuses to burn properly. Borrowed a friends CRRW drive today and burned the * ..ahem* boot disk (not the illegal iso's) and it worked a treat.

[JohnT]

Good, that you found the problem...bad it was your hdw.:(