Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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 have a sata drive used for storing music and videos formated with jfs that is somehow corrupted. I can boot the pc with the drive connected using a Slax CD but can not boot using my Slackware install with kernel 184.108.40.206. I can only boot Slackware with this sata drive disconnected
I want to try and recover the music and videos on this hd with jfsrec.
Is there a way to force the boot process with the cabling connected to this drive?
Or see if your problem is that your fstab is asking for a file system check on the drive at the wrong physical address. If so, try changing it to use a UUID= or LABEL= form or just change the boot-time check options (at the end of the device description line) to "0 0". Perhaps a noauto in the options field might also help, although the "noauto" is ignored when a fsck is implied by nonzero check option values. (You should be able to do this using the Slack CD.)
Or see if your problem is that your fstab is asking for a file system check on the drive at the wrong physical address
Thanks for the suggestion but the drive is not even listed in /etc/fstab. I could always mkdir somwhere and mount the dev later but the problem is that the system will not even get through a boot without a kernel panic. Something is seriously odd on that disk. I can not even run /sbin/lilo without errors when that sata drive is connected. I couldn't figure out what was wrong with my install of slack current 2 days ago. I was getting big EBDA errors and such at boot until I figured out it was this drive that was causing all the grief.
This is going to be a forever job as I'm only scannong for mp3's and ISO's this cycle since the bad drive is 230gb and the target recup drive is only 80 gb. Photorec says 6 hours plus and counting.
OK, here's another suggestion: One of my (older) systems failed this morning with a "kernel panic" during the boot (which was the first time it had been booted in several months). After a while, I figured out that the drive cable had failed (from age, I guess, since it wasn't being used). I replaced it with a spare, and I'm now using that system to send this note (while downloading updates to make the system current).
Last edited by PTrenholme; 05-02-2010 at 12:50 PM.