DebianThis forum is for the discussion of Debian 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'm running Debian testing on my laptop, which also have a periodic HW error. The error have frozen the system, forcing me to kill the power. I believe that have messed up my filesystem and when I boot get a kernel panic, even in single mode. The system is setup with a separate /boot partiion and then a LVM partition, split into root, home and misc partition.
I would prefer to recover the whole system, but I would settle gain access to the /home on the lvm partition.
*) to boot on a Debian CD in rescue mode and hoped to run shell in the root partition. In other cases I'd luck with rescuing a system, but it fails.
*) to boot up on the newest Knopppix Cd, running pvscan and vgimport. But because the Volume Group isn't exported and fails. The vgimport command doesn't support --force as suggested elsewhere. I've tried with a Ubuntu 8.x, but it didn't supported lvm.
My next ideas is to try with live-cd, where the vgimport supports --force, if anyone can confirm that it works. Otherwise try some sort of filesystem tool-cd and check the filesystem. But I'm afraid to make a even bigger mess.
ReiserFs: warning: is_leaf: item location seems wrong (second one): *3.6* [197 1226 0x1 IND], item_len 156, item_location 1388, free_space(entry_count) 0
ReiserFs: dm-1: warning: vs-5150: search_by_key: invalid format found in block 520574. Fsck?
ReiserFs: dm-1: warning: vs-13070: reiser_read_locked_inside: i/o failure occurred trying to find stat data of [197 532 0x0 SD]
run-init: /sbin/init: Permission denied
Kernel paninc - not syncing: Attempted to kill init!
Boot with a live-cd and do an fsck
I believe it's 'reiserfsck [device/partition]' for reiserfs.
Just make sure you've got the right partition and that it's not mounted:
To see which one it is.
- Between distributions an ide disk might show up as hdx, on others as sdx - so check again from the live cd!
to make sure it's not mounted.