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!
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.
Hey, I recently broke my Debian kernel. I'm missing libraries. However, to put these libraries back where they belong I need some sort of a live CD or some guidance from a pro. Does such a thing exist?
--I have tried Ubuntu 10.04 LTS 32-bit, Knoppix 6.7 and GParted Live. The most success I have had is with Knoppix, I get three drives that are not right (with mdadm --configure --scan) and they are /dev/md126, /dev/md127 and /dev/md128. Note that /dev/md127 is the boot directory housing /grub and the kernel only.
Do I have hope?
Raid card is an Adaptec SCSI RAID adapter 39160
Motherboard: TYAN S4882 Thunder K8
CPU: 4 Opteron 850s
RAM: 8GB Kingston HyperX DDR ECC
Drives: 8 SCSI drives, assorted make and model, 73GB each
Last edited by Facepalm41; 11-10-2011 at 06:13 PM.
If you had debian then I'd have started with the debian live cd and recreate or try to fix the array.
Or find a debian live more similar than current stable that is equal to your originally working version.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
If you have a recent Debian installation, you can download the live-USB stick with the same version and kernel as your current installation.
Boot with the USB, your RAID will assemble (1). Mount the directory tree under the mount point on the USB stick. If you have multiple partitions, mount / first, then the other directories below /.
Excecute chroot into the / of the RAID (where you mounted it on the USB stick). If that was succesful, take it from there and re-install your things.
A cdrom is likely to work as well, but USB is more 2011-like.
(1): I know this sounds almost unbelievable, but it does assemble the RAID although your USB sticks doesn't know anything about that you intend to use a RAID. In case it is not assembling, use the mdadm tools to assemble it. I forgot the commands, but you can have mdadm discover and rebuild etc. Don't try to mount a single disk (unRAIDED) though as that will ruin the array when you write on it.
Edit: you'll need the rescue version in order to have mdadm included.
Okay, sorry for long time no reply! I've got the same Debian live CD as the original OS and I've also got the same kernel. However, it does not want to assemble the RAID array. It says that my RAID5 array is RAID1 and gives the following error:
md: md0 stopped.
md: sdc1 has same UUID but different superblock to sdb1
md: sdc1 has different UUID to /dev/sdb1
mdadm: failed to add /dev/sdc1 to /dev/md0: Invalid argument
I get this same error for all of these drives (all in the array):
I would do that, but there's the problem - I can't get to the data. I can only get the kernel and the boot directory, and I have that already. The rest of the stuff is on the RAID array that won't mount.
Probably not, because the RAID controller is not that fancy. There are no options in its BIOS for setting up RAID, besides when kernels look at it they see all of the individual drives and don't bother with the "Linux_raid_autodetect" partitions.
Wild idea: Would it be possible to rebuild my kernel so that it looks for the missing libs on a CD, while booting from the RAID array? My kernel is vmlinuz-184.108.40.206-amd64. If I can do that, then I get a rudimentary OS that actually loads the array, and I can copy the libs and the old kernel over.
Might wish to post that as a single question on a new post. I think you could link any file to suite.
My question is how did you get this thing working originally. If you just put in a cd and when then the live cd ought to recover it enough to see the files. Why can't we just access the array?
I looked that up. It should be a real hardware array adapter. Did you create the array with the scsi bios and utilities? I never heard of a software array from adaptec. Also it is possible you didn't use it to create the array, that would not have made sense.
A friend of mine set it up with mdadm on a Debian server distro a few years back on the then-new Aberdeen server.
Anyways, onto your idea, the problem I have now is that I don't seem to be able to see the rest of the array. When I used my Knoppix CD and followed the mdadm MAN file, I was only able to get one drive going - the boot 'array'. That had the kernel and grub, that's it. Problem is, I know where the superblocks are, but I don't know the drive configuration. How would I go about finding it out?