Trying to dd a server with LVM to another ext HD, then to another server
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.
interesting, I trued to change my /boot/menu.lst but my boot directory is empty. I rebooted from the CD and entered rescue mode, then mounted sda1 (which is my boot directory) and everything was there.
I modified the menu.lst then reboted from the hard disk, same error..
checked my boot directory and it is again empty. checked /home just to see if all was well there and it was.
Your "2 sda's" are just two names for the same drive, one being its name in the SCSI subsystem and the other being its "world wide name" which should be independent of what kernel driver chain is handling it. Note that only the "scsi" vs. "wwn" prefix is different.
What should work is replacing each ocurrence of "36001ec90d41dbf001b760b72e504ab06" with "36001e4f01b782a001c5a5e084d3ac69f" in /etc/fstab. I don't know of any reason besides a typo for this not to work for you.
Oops, yes, the GRUB menu will have to be changed too.
Your RAID controller won't care about drive serial numbers. It either uses whatever is attached to it or searches all attached drives for the RAID headers.
Last edited by rknichols; 01-29-2015 at 12:17 PM.
Reason: add oops,... and RAID comment
^ i just realized that "36001ec90d41dbf001b760b72e504ab06" and "36001e4f01b782a001c5a5e084d3ac69f" are different so my response #23 is wrong. still not sure what these uuid's refer to and why they are not listed by blkid ?
what happens to the ID's if one of the drives in the RAID array dies and is replaced with a new drive?
id the ID on the drive itself or the RAID card?
See #32. The drive serial number is in flash memory on the drive along with the drive's firmware. It is not written on the platters, or at least not anywhere that can be accessed through the normal interface.
Looking at your fstab, the only things you are accessing by those lengthy ID strings are /boot and swap. The drive that shows up as /dev/sda is actually the RAID controller, right? If so, those numbers are probably generated by the RAID controller itself, and don't relate to any individual drive in the array. I'm guessing a bit here. I didn't fully take the RAID controller into account before. Sorry.