[opensuse] Harddisk serial number (SuSE10.3), cloning disks
Hi list, - reported by a friend of mine, when cloning (ghosting) a 10.3 disk in its entirety, the cloned disk will not boot due to the serial numbers of the cloned disk doesn't match the serial of the original disk. - apparently this serial is written somewhere in the conf files of GRUB. - I've not seen this as I've not been to his place (quite far from here, trying to solve the matter through e-mail...), can this be true?? - I mean, really? :-) -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tirsdag 06 november 2007 08:42 kvad Verner Kjærsgaard:
- reported by a friend of mine, when cloning (ghosting) a 10.3 disk in its entirety, the cloned disk will not boot due to the serial numbers of the cloned disk doesn't match the serial of the original disk.
- apparently this serial is written somewhere in the conf files of GRUB.
- I've not seen this as I've not been to his place (quite far from here, trying to solve the matter through e-mail...), can this be true??
- I mean, really? :-)
I don't know, since I'm staying put with 10.2. However, if 10.3 has started using UUIDs in stead of /dev/<device>, then yes. If that is the case, it should be easily fixed. Once the clone is in place, he boots a rescue cd, and runs blkid /dev/<device> That will tell him the device's UUID, which he then puts into menu.lst Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Verner Kjærsgaard wrote:
Hi list,
- reported by a friend of mine, when cloning (ghosting) a 10.3 disk in its entirety, the cloned disk will not boot due to the serial numbers of the cloned disk doesn't match the serial of the original disk.
- apparently this serial is written somewhere in the conf files of GRUB.
- I've not seen this as I've not been to his place (quite far from here, trying to solve the matter through e-mail...), can this be true??
- I mean, really? :-)
Sort of I ran into this problem Instead of using something like /dev/sda2 as the root device in grub it has /disk/id-by-xxxxxxx or similar which it uses to identify the hard drive, so if this changes it screws up the initrd, if you edit the boot loader and create a new initrd it works fine from the rescue console. Not sure why it changed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tirsdag 06 november 2007 10:01 skrev Matthew Stringer:
Verner Kjærsgaard wrote:
Hi list,
- reported by a friend of mine, when cloning (ghosting) a 10.3 disk in its entirety, the cloned disk will not boot due to the serial numbers of the cloned disk doesn't match the serial of the original disk.
- apparently this serial is written somewhere in the conf files of GRUB.
- I've not seen this as I've not been to his place (quite far from here, trying to solve the matter through e-mail...), can this be true??
- I mean, really? :-)
Sort of
I ran into this problem
Instead of using something like /dev/sda2 as the root device in grub it has /disk/id-by-xxxxxxx or similar which it uses to identify the hard drive, so if this changes it screws up the initrd, if you edit the boot loader and create a new initrd it works fine from the rescue console.
Not sure why it changed.
THANKS to all!! -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/6/07, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Tirsdag 06 november 2007 10:01 skrev Matthew Stringer:
Verner Kjærsgaard wrote:
Hi list,
- reported by a friend of mine, when cloning (ghosting) a 10.3 disk in its entirety, the cloned disk will not boot due to the serial numbers of the cloned disk doesn't match the serial of the original disk.
- apparently this serial is written somewhere in the conf files of GRUB.
- I've not seen this as I've not been to his place (quite far from here, trying to solve the matter through e-mail...), can this be true??
- I mean, really? :-)
Sort of
I ran into this problem
Instead of using something like /dev/sda2 as the root device in grub it has /disk/id-by-xxxxxxx or similar which it uses to identify the hard drive, so if this changes it screws up the initrd, if you edit the boot loader and create a new initrd it works fine from the rescue console.
Not sure why it changed.
THANKS to all!!
One of guys hit this issue too. I don't know what he had to fix in grub's menu, but I know the final fix wa in /etc/fstab, so don't forget to have your friend update that as well. We actually do a lot of cloning of our lab machines. We edited the grub/fstab fields to go back to /dev/sda, etc. prior to making the clone. Our machines are similar enough that it works for us. If there is a better way, we're all ears. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
One of guys hit this issue too. I don't know what he had to fix in grub's menu, but I know the final fix wa in /etc/fstab, so don't forget to have your friend update that as well.
We actually do a lot of cloning of our lab machines. We edited the grub/fstab fields to go back to /dev/sda, etc. prior to making the clone. Our machines are similar enough that it works for us.
If there is a better way, we're all ears.
Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
My installation of 10.3 showed that both menu.lst (GRUB) and fstab uses the ID of the disk (is that called the UUID?). Understandably, you need to edit both menu.lst and fstab to get the clone working properly. The former will allow you to start the kernel whereas the latter lets you mount the disk. IIRC, during the installation, there is an option under the advanced section for partitioning for you to choose whether you want to use the ID or the device name (e.g. /dev/sda). If you were to install a new OS, take a look at the advanced options for partitioning. Regardless, even after changing both menu.lst and fstab to use, say, /dev/sda1, you will need to ensure that the cloned disk is recognised in the same order when its placed into a new system. i.e. the BIOS recognises it as /dev/sda and not /dev/sdb. Cos if the order is wrong, the entry in menu.lst/fstab will be incorrect as well. Any other input? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dienstag, 6. November 2007 Chee How Chua:
IIRC, during the installation, there is an option under the advanced section for partitioning for you to choose whether you want to use the ID or the device name (e.g. /dev/sda).
Oops, this I missed. It shouldn't be hiding in advanced though. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dienstag, 6. November 2007 Greg Freemyer:
We actually do a lot of cloning of our lab machines. We edited the grub/fstab fields to go back to /dev/sda, etc. prior to making the clone. Our machines are similar enough that it works for us.
If there is a better way, we're all ears.
yast -> system -> partitioning -> select partition -> edit -> fstab options. Choosing "device name" would give you the old "/dev/sd*" names. A chinese prosecutor might want to differ but I think opensuse's choice to default to a storage device's serial number sucks badly. Ok, so the world is not that simple. Still: Why not ask people during installation? Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Nov 6, 2007 12:54 PM, Wolfgang Woehl <tito@rumford.de> wrote:
A chinese prosecutor might want to differ but I think opensuse's choice to default to a storage device's serial number sucks badly. Ok, so the world is not that simple. Still: Why not ask people during installation?
The prosecutor steps in :) The device name will differ if you use the old PATA drivers to access IDE drives (/dev/hdx) and the new SATA drivers, which create /dev/sdx. As far as you can boot either way (providing the right boot options), hard-coding the device names is going to be mess. Same applies for future upgrades (with unknown yet driver/naming scheme), or swapping the drives in the machine, or moving the drive in another machine. The problem you see appears only if you clone the drive to another one. Then you only have to change the id in menu.lst and fstab. Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-11-06 at 16:38 -0600, Sunny wrote: ...
The problem you see appears only if you clone the drive to another one. Then you only have to change the id in menu.lst and fstab.
In which case you could use "labels" instead of uuids. Or "ids", perhaps - no, that one depends on the HD make and serial. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHMR4itTMYHG2NR9URAol0AJ9+WwJwd4kFtH6y91RsKLYFUo6mPwCfS34m owvx5+aQKlYYh496n7RuBbY= =319C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dienstag, 6. November 2007 Sunny:
The prosecutor steps in :)
The device name will differ if you use the old PATA drivers to access IDE drives (/dev/hdx) and the new SATA drivers, which create /dev/sdx.
People clone for a tight spec range. They will not mix pata and sata boards and expect things to work. Motion denied.
As far as you can boot either way (providing the right boot options), hard-coding the device names is going to be mess.
Look at /etc/fstab. There's your hard-coded device nomenclature. Be it by path, id, device name. It's not a mess, it's how it works. I'm afraid this motion has to be denied :) Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Nov 7, 2007 12:03 PM, Wolfgang Woehl <tito@rumford.de> wrote:
People clone for a tight spec range. They will not mix pata and sata boards and expect things to work. Motion denied.
As far as you can boot either way (providing the right boot options), hard-coding the device names is going to be mess.
Look at /etc/fstab. There's your hard-coded device nomenclature. Be it by path, id, device name. It's not a mess, it's how it works. I'm afraid this motion has to be denied :)
Yeah, we do not live in a perfect world. Only the judges have the power to deny a motion, and as we know, they are not the best example of technical competency :-P ;-) Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Carlos E. R. -
Chee How Chua -
Greg Freemyer -
Johnny Ernst Nielsen -
Matthew Stringer -
Sunny -
Verner Kjærsgaard -
Wolfgang Woehl