SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was wondering if someone could shed a little light on a boot problem i'm having. I have recently installed SuSE 9.1 Pro and was searching checking out the system when I noticed that the DMA settings where lower than I expected.
I adjusted the DMA settings with YAST, changing from DMA 66 to UDMA 100, which I knew my HD was capable of. Everything seemed fine until I rebooted the machine and now it will not boot.
When booting there are a load of errors, after Linux has been selected in GRUB. These errors are along the lines of:
/sbin/mingetty: /sbin/mingetty: cannot execute binary file
INIT: Id "X" respawning too fast: disabled for 5 minutes
INIT: no more processes left in run level
Looking for a solution on the web provided an idea to use the install DVD to try and repair the previous installation, I had hoped this would reset the changes I had made, but this didn't work.
Choosing Failsafe in GRUB produces the same errors.
The system is a dual boot Win 2K/SuSE 9.1 Pro machine, and Win 2K still boots fine. But I don't care about anything on the Win 2K partition. There is however some data on Suse that I would like to save preferably.
Is there anyway of fixing the problem, and if not how can I back up the data from SuSE without being able to boot? I have space on another computer on my network, a Win XP Pro machine. Is there a way I could reinstall Suse and leave the data intact? Or could I use the live SuSE to copy the files I want to the Win XP machine over the network? I would just try this but I don't want to corrupt the data an would like someone more knowledgeable than myself to reassure me that I won't lose everything.
I have been enjoying SuSE up until now but this has thrown a bit of a spanner in the works!
I am quite new to linux and would appreciate any help you can offer.
You could try it with the Suse pro dvd and then select automatic repair. That works fine with me when i have a problem like that. When this doesn't work you can try the live cd, but i don't have any experience with that, so i'm not sure.
When these two options don't work you can perform a upgrade installation, this will leave your data as it is.
Maybe there are some other options in text mode, but i don't know any right now.
Thanks for you response Cabletalk, unfortunately I've already tried the automatic repair which stopped booting in the same way as the original problem.
I've just tried the live cd, after reading that it definately wouldn't do anything to the data, but unfortunately this has failed to boot too. This time the error messages are different, a series of errors is produced:
cloop: Read and -3 uncompressing block errors
buffer I/O error device cloop0 errors
finally ending in
Kernal Panic: attempting to kill init!
If anyone can tell me how to get a direct copy of these errors that would be helpful too, i.e. where and how can I get to the logs which would store these errors.
Thanks for clearing things up about the upgrade installation too. On a side point could I upgrade to 9.2 Pro at the same time? I have a downloaded copy of this now.
Sorry to hear this didn't work. How far does it boot with the cd/dvd? If the boot sequence in the bios is set right you should be able to boot from cd/dvd without problems.
It makes no difference for your data if you make an upgrade to 9.1 or 9.2. It will leave your data untouched.
I'm a unsure as to which method of booting you were refering to.
With the Live CD: the problems seem to start occuring when it tries to mount the root partition. There are three partitions, as far as i can make out Win 2K, Swap and root. From what i've read the live cd tries to mount all exisiting partions as read only. Please correct me if i'm wrong about this. This is where it stops and just freezes up.
I also tried the Update Installation, this seemed to be going okay untill the following error appeared:
Then after I hit okay on this dialog box, another error cam up:
can't read pwd for user id 0
Then it frooze.
Thinking that a corrupted root partition could be the source of the problem I tried the installation repair again. The installation repair got further this time and told me that the root partition and filesystem had been corrupted. These were repaired okay, except that the repairs don't seem permanent. Next errors in the boot loader were detected, I'm working on this at the moment. I'll keep updating here untill I get a solution.
Been working on reinstalling the boot loader, using methods found on this and other forums as well as the net. When I try to install the bootloader it keeps freezing up whilst saving the new bootloader. I've tried a number of ways that i have found but all have failled in the same way. With no explanation, that I can see, as to why the boot loader won't reinstall (i.e. no error messages) i'm quite stuck.
I'd really like to hear from someone whom can offer some advice about how to fix/reinstall the bootloader, since the methods I have found haven't worked. I'd also like to know if i'm on the right lines to fixing the problem or if anyone can help me understand what i've done wrong. Please, if you can help in anyway with this I would really appreciate it.
If I don't get any other suggestions, I'm gona try and tackle this from a different angle. I have a spare hard disk (actually identical to this one). I was going to use it for something else, but figure I can install Win2K and SuSE on to it as before, then using the new hard drive and working SuSE, get access to my data by trying mounting the corrupted partitions. I'd appreciate any suggestions about the purposed solutions and if there are any gapping flaws in them.