Suse/NovellThis 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 can't help you make the disk boot and work again but if you want to get the data of the disk I sujest you remove the disk place it in a external usb caseing and use either of those live cds to boot some other computer with the usb disk attached. You could probebly even use a windows system or any other system which automatically mounts usb disk. This should give some access to the files on the disk at least the ones that are not corrupted.
It could just be that you might need to delete the corrupted file, ie a confiuration file and recreate it in the same directroy with the correct set up info in it. Some systems might automatically create cirtain files. As you dont have enough access to the disk to be able to tell say what the actuall problem is these are just some things you could look at trying.
I have personally recovered data of drives that did not boot buy pluging them into an exteranl usb hard drive caseing.
Just a doubt: why USB? Why not simply change the boot to the secondary IDE bus? Could I mount the its partitions in such a location if boot the box with a LiveCD? Even more, if I leave the troubled disk as boot one and boot from a LiveCD, could I mount the partitions one the system is up and running?
I've not an available USB box, but it is not big deal to move the disk to the secondary IDE bus.
I've already tried to do that, but I don't know how to mount the partition.