Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently installed SUSE 9.3 (non PRO) and had to see that it did not start on its own. There is no other OS installed. The only partitions are the SWAP and linux partition.
Using the start DVD and choosing "INSTALL -> BOOT INSTALLED SYSTEM"
linux came alive.
So I decided to change grub configuration with YAST. But afterwards the saving process aborted at 50%. I had to kill it.
This saving problem appeared always no matter which feature I changed. Even trying to use LILO, YAST denied to do so.
thanks for reading [ and answering ]
P.S.: I read many bootloader threads but I think none fits with my problem. But if you know one, please show it to me.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
md5sum creates a unique hash value for a file or device (your DVD in this case). You can check its data-integrity with that, but you have to know the correct md5sum value to compare to what you get from your DVD.
Code:
man md5sum ;)
For a complete SuSE it will be time consuming though.
When you start the DVD and select "install manually" your old installation will be detected and you'll be offered several repair options. One of them should be sonmething like "install a new boot loader"...
Can't see anything frightening for old SuSE in your hardware...
I started the installation again and chose the repair option. You were right. YaST2 contained mistakes, grub too. The configuration was saved now. But in the end it turned out to be the same problem.
So I checked my DVD using the SUSE Media Check in YaST. It revealed no errors.
Is it possible that my hard disk has an defect yust at the MBR?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Quote:
Originally posted by fremder ...YaST2 contained mistakes, grub too. The configuration was saved now. But in the end it turned out to be the same problem...
Well, now that is funny (well, not really). In the light of your next statement:
Quote:
Originally posted by fremder ...So I checked my DVD using the SUSE Media Check in YaST. It revealed no errors.
That's a nice contradiction: The repair funcionality finds errors on your hard disk, the media check finds none on your DVD, yet you copied the data from your DVD to your hard disk ... well.
Lets reason this through. Assuming that there are no errors on your DVD but a failed installation on your hard disk could mean either of these:
Data-transfer from DVD to disk is faulty -- but in a intermittent way, since you could determine data integrity on the DVD okay (at least for the sake of argument) while they are corrupted when you try to work with them. Possible, but not probable in my eyes.
The other possibility I can see would be instable memory (RAM), since most of the program-packages come in a compressed form and have to be decompressed before installation. Something could have gone wrong there, and the most suspect component would be your RAM. I'd suggest you google for a program to check your RAM-integrity under load (maybe even YAST offers something like that in its hardware module).
Quote:
Originally posted by fremder ...Is it possible that my hard disk has an defect yust at the MBR?
Anything is possible and then some more .
But it is improbable from the symptoms you describe. The MBR contains the first stage (in your case of GRUB) for boot loading from hard disk. Should that be corrupt, you couldn't start your 'puter from the hard disk at all. Also, while some code of GRUB is written to the MBR (and was re-written when you repaired it), there is lots more in /boot ...
thanks for thinking about it but this sounds not convincing to me. Before I started my testing in Linux my PC worked fine with Windows XP. So the RAM should be okay.
But there is another weak link in the chain:
To keep my data secure I pugged a new (old) hard disk in my PC took the old one out. So I really think all this has something to do with the old hard disk. To check whether I'm right or not I will buy a new hard disk (there is never enough space ) and repeat the installation again.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Oops.
"That's a nice contradiction: The repair funcionality finds errors on your hard disk, the media check finds none on your DVD, yet you copied the data from your DVD to your hard disk ... well."
Suspicious. Maybe it's cheaper when you just pull out the cable and put it securely back in for the hd you're just using now ... after all, you plugged it in in place of your other one -- could just be a weak connection.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.