Hi,
To my knowledge, I successfully make a copy of my hard drive to an image file for a OpenSUSE 11.1 install, via clonezilla live CD. (no errors)
I also was able to restore that same image to a new identical hard drive, no errors from CloneZilla.
The issue is that when I boot from this freshly restored new HDD, OpenSUSE won't load because the GRUB bootloader is set at looking for the root at this location:
/dev/disk/by-id/ataWDC_WD1600BEVT-00ZCT0_WD-WXE409K111111-part2
The above names the serial number (i guess) of the old HDD.
So, being smarter then the average bear I edit Grub to use the new Serial Number:
/dev/disk/by-id/ataWDC_WD1600BEVT-11ZCT0_WD-WXE309U444444-part2
(also tried using only /dev/sda2 but same issues as per below)
But that gets me only to the rescue system... it says it can not locate the old drive name "-part3".
It is looking for this (the old name of the drive):
/dev/disk/by-id/ataWDC_WD1600BEVT-00ZCT0_WD-WXE409K111111-part3
When it should really be looking for this (the new name of the drive):
/dev/disk/by-id/ataWDC_WD1600BEVT-11ZCT0_WD-WXE309U444444-part3
I ran mkinitrd for fun and that didn't solve anything.
How can I fix it so it always looks at the new HDD name and not the old one?
Note: Although, I can open Yast, I can not do anything on it... I see the menu, but selecting anything does nothing.
My issue with the above, is I have to restore my one image to 20 hard drives... Is there an automated way, or maybe even an option in CloneZilla that allows you to change that HDD name/serial? Or what are the steps I need to take for each hard drive restoration?
Although the above relates more on the OpenSUSE / Grub side of things, I am hoping to find someone who ran into the same/similar scenario.
Thank you for any hints/tips.
Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it's easier to modify /etc/fstab as /dev/sdx style, or use UUID or LABEL of partition, not use the serial number of hard drive, since you are cloning the file system. UUID and LABEL can be cloned, but not the hard drive serial number, which is different for different hard drive. It's sticky to hardware.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-12-02
Hello!
I just ran into a very similar scenario when trying to clone a multi-boot system -coincidentally with openSUSE as the first OS loaded (having grub in MBR). My message is same albeit "Waiting for device … to appear …-Maxtor_98196H8_V80HATWC-part2" when it should be "…-Maxtor_98196H8_V80H9VPC-part2" for the new drive. (Note last four digits of new drive, and that my drives are exactly the same otherwise.) I think Clonezilla should NOT be looking at the last portions of the hard drive ID, if any of it -otherwise it should of course do it all right. Although there may be other factors behind this elusive issue- beyond openSUSE -as may begin to be revealed w/ below-outlined diagnostics. Please advise on any advancements to this issue.
Thanks.
Al
Add'l diagnostics:
1) I have hda w/ three OSs: hda1=swap, hda2=openSUSE 11.2(w/ grub in MBR), hda3=(mirror), hda4=Mandriva 2010, and hda5=simplyMEPIS 8.0.12.
2) My 80GB Maxtor Hard drives (original) "hda" & (copy) "hdb" have the exact same parameters.
3) *** The only difference between OSs on hda drive is that MEPIS is ext4 while the others are reiserfs. i.e.: Could it be that Clonezilla has an issue mixing reiserfs…? ***
4) When I try booting the cloned system, I get a text-based menu instead of the nice GUI 'splash' style screen w/ menu.
5) I encounter your mentioned error when booting into (hdb) openSUSE re. drive identification. (…409K111111-part3 v. …309U444444-part3, HOWEVER…
6) When selecting Mandriva from the (hdb text-based) grub menu it almost immediately locks' the system unlike w/ openSUSE with statement on screen, "Filesystem type is ext2fs, partition type 0x83 configfile /boot/grub/menu.lst" -i.e.: not sure it's recognizing the (reiserfs) filesystem, AND…
7) Although, when selecting simplyMEPIS from the (hdb text-based) grub menu it boots into MEPIS just fine.*
8) Hooking up original (hda) disk and booting into either of these systems works just fine and, given 3-second delays for each menu, switching to/from each OSs boot menus is a 'breeze'.
9) Note: After 3 unsuccessful attempts, I also then ran a low-level format on my "copy" hdb drive to assure there was nothing wrong there. (My 4th attempt also failed with same conditions.)
10) I also already used 'expert' conditions for 2nd thru 4th attempts, toggling ON perhaps relevant items.
* Note MEPIS' KDiskFree output:
Device Type Size MountPoint Free Full%
/dev/sda2 reiserfs N/A /mnt/sda2 0 B N/A
/dev/sda4 reiserfs 11.6GB / 9.2GB 20.2%
/dev/sda5 ext4 N/A /mnt/sda5 0 B N/A
/dev/sr0 udf,iso9660 N/A /media/cdrom 0 B N/A
/dev/sr1 udf,iso9660 N/A /media/cdrom1 0 B N/A
tmpfs ? 505MB /lib/init/rw 505 M 0.0%
udev ? 10.0MB /dev 7.3MB 27.5%
Thoughts: (Now, realize that I'm a 'newbie' to linux…)
1) Perhaps Clonzilla has issues w/ reiserfs, at least mixed w/ other fs's.
2) Clonzilla is not handling recognition of new drives, although perhaps this is an issue w/ some systems grub functions.
3) Some, perhaps many, linux OS-derived grubs are too particular (recording,,, full drive IDs when they shouldn't). i.e.: MEPIS apparently may not be doing this so has no problem booting in this scenario.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-12-02
Hello again!
Okay, one small correction to above initial issue description in two parts: (I had Mandriva and MEPIS spec’s crossed…)
Diagnostic # 1 where reads "hda4=Mandriva 2010, and hda5=simplyMEPIS 8.0.12" should be "hda4=simplyMEPIS 8.0.12, and hda5=Mandriva 2010",
Diagnostic # 3 where reads "MEPIS is ext4" should be "Mandriva is ext4", and
Diagnostic # 6 where reads "not sure it's recognizing the (reiserfs) filesystem" should be "not sure it's recognizing the (ext4) filesystem".
UPDATE: I was able to resolve booting into openSUSE with the subsequent resolutions describing changing hard drive IDs to "sda#" in /boot/grub/menu.lst and /etc/fstab accordingly. (I had not seen these resolutions posted until recently.) i.e.: Most everything appears to work regarding reiserfs environments.
However, I still cannot get the Mandriva partition to boot, and now I suspect Clonezilla is not correctly reading/cloning Mandriva's ext4 file system. (Attempting similar/same resolutions toward Mandriva as done with openSUSE do not resolve anything.)
Please advise re. ext4 and Clonezilla.
Thanks.
Al
Revised thoughts:
1) Perhaps Clonzilla has issues w/ ext4, at least mixed w/ other fs's (?) ref. above # 6: When booting into Mandriva (ext4), … (error) “Filesystem type is ext2fs, partition type 0x83 configfile /boot/grub/menu.lst" -i.e.: not sure it's recognizing the (ext4) filesystem.
2) Clonzilla is not handling recognition of new drives- integrating new drive IDs -although perhaps this is an issue w/ some systems grub functions (?)
3) Some, perhaps many, linux OS-derived grubs are too particular (recording,,, full drive IDs when they shouldn't). i.e.: MEPIS apparently may not be doing this so has no problem booting in this scenario.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, for OpenSuSE, you have to change /etc/fstab and grub config by yourself, since the defaut settings from OpenSuSE is related to hardware, which can not be cloned.
Did you run fsck.ext4 on your mandriva partition to make sure its integrity is OK?
For new hard drive, maybe the issue is on kernel. If so, give clonezilla live 20091127-karmic a try.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
To my knowledge, I successfully make a copy of my hard drive to an image file for a OpenSUSE 11.1 install, via clonezilla live CD. (no errors)
I also was able to restore that same image to a new identical hard drive, no errors from CloneZilla.
The issue is that when I boot from this freshly restored new HDD, OpenSUSE won't load because the GRUB bootloader is set at looking for the root at this location:
/dev/disk/by-id/ataWDC_WD1600BEVT-00ZCT0_WD-WXE409K111111-part2
The above names the serial number (i guess) of the old HDD.
So, being smarter then the average bear I edit Grub to use the new Serial Number:
/dev/disk/by-id/ataWDC_WD1600BEVT-11ZCT0_WD-WXE309U444444-part2
(also tried using only /dev/sda2 but same issues as per below)
But that gets me only to the rescue system... it says it can not locate the old drive name "-part3".
It is looking for this (the old name of the drive):
/dev/disk/by-id/ataWDC_WD1600BEVT-00ZCT0_WD-WXE409K111111-part3
When it should really be looking for this (the new name of the drive):
/dev/disk/by-id/ataWDC_WD1600BEVT-11ZCT0_WD-WXE309U444444-part3
I ran mkinitrd for fun and that didn't solve anything.
How can I fix it so it always looks at the new HDD name and not the old one?
Note: Although, I can open Yast, I can not do anything on it... I see the menu, but selecting anything does nothing.
My issue with the above, is I have to restore my one image to 20 hard drives... Is there an automated way, or maybe even an option in CloneZilla that allows you to change that HDD name/serial? Or what are the steps I need to take for each hard drive restoration?
Although the above relates more on the OpenSUSE / Grub side of things, I am hoping to find someone who ran into the same/similar scenario.
Thank you for any hints/tips.
Steve
Solution was found here:
http://forums.opensuse.org/install-boot-login/421431-cloning-hdd-hdd-issue-hdd-names.html
Yes, it's easier to modify /etc/fstab as /dev/sdx style, or use UUID or LABEL of partition, not use the serial number of hard drive, since you are cloning the file system. UUID and LABEL can be cloned, but not the hard drive serial number, which is different for different hard drive. It's sticky to hardware.
Steven.
Hello!
I just ran into a very similar scenario when trying to clone a multi-boot system -coincidentally with openSUSE as the first OS loaded (having grub in MBR). My message is same albeit "Waiting for device … to appear …-Maxtor_98196H8_V80HATWC-part2" when it should be "…-Maxtor_98196H8_V80H9VPC-part2" for the new drive. (Note last four digits of new drive, and that my drives are exactly the same otherwise.) I think Clonezilla should NOT be looking at the last portions of the hard drive ID, if any of it -otherwise it should of course do it all right. Although there may be other factors behind this elusive issue- beyond openSUSE -as may begin to be revealed w/ below-outlined diagnostics. Please advise on any advancements to this issue.
Thanks.
Al
Add'l diagnostics:
1) I have hda w/ three OSs: hda1=swap, hda2=openSUSE 11.2(w/ grub in MBR), hda3=(mirror), hda4=Mandriva 2010, and hda5=simplyMEPIS 8.0.12.
2) My 80GB Maxtor Hard drives (original) "hda" & (copy) "hdb" have the exact same parameters.
3) *** The only difference between OSs on hda drive is that MEPIS is ext4 while the others are reiserfs. i.e.: Could it be that Clonezilla has an issue mixing reiserfs…? ***
4) When I try booting the cloned system, I get a text-based menu instead of the nice GUI 'splash' style screen w/ menu.
5) I encounter your mentioned error when booting into (hdb) openSUSE re. drive identification. (…409K111111-part3 v. …309U444444-part3, HOWEVER…
6) When selecting Mandriva from the (hdb text-based) grub menu it almost immediately locks' the system unlike w/ openSUSE with statement on screen, "Filesystem type is ext2fs, partition type 0x83 configfile /boot/grub/menu.lst" -i.e.: not sure it's recognizing the (reiserfs) filesystem, AND…
7) Although, when selecting simplyMEPIS from the (hdb text-based) grub menu it boots into MEPIS just fine.*
8) Hooking up original (hda) disk and booting into either of these systems works just fine and, given 3-second delays for each menu, switching to/from each OSs boot menus is a 'breeze'.
9) Note: After 3 unsuccessful attempts, I also then ran a low-level format on my "copy" hdb drive to assure there was nothing wrong there. (My 4th attempt also failed with same conditions.)
10) I also already used 'expert' conditions for 2nd thru 4th attempts, toggling ON perhaps relevant items.
* Note MEPIS' KDiskFree output:
Device Type Size MountPoint Free Full%
/dev/sda2 reiserfs N/A /mnt/sda2 0 B N/A
/dev/sda4 reiserfs 11.6GB / 9.2GB 20.2%
/dev/sda5 ext4 N/A /mnt/sda5 0 B N/A
/dev/sr0 udf,iso9660 N/A /media/cdrom 0 B N/A
/dev/sr1 udf,iso9660 N/A /media/cdrom1 0 B N/A
tmpfs ? 505MB /lib/init/rw 505 M 0.0%
udev ? 10.0MB /dev 7.3MB 27.5%
Thoughts: (Now, realize that I'm a 'newbie' to linux…)
1) Perhaps Clonzilla has issues w/ reiserfs, at least mixed w/ other fs's.
2) Clonzilla is not handling recognition of new drives, although perhaps this is an issue w/ some systems grub functions.
3) Some, perhaps many, linux OS-derived grubs are too particular (recording,,, full drive IDs when they shouldn't). i.e.: MEPIS apparently may not be doing this so has no problem booting in this scenario.
Hello again!
Okay, one small correction to above initial issue description in two parts: (I had Mandriva and MEPIS spec’s crossed…)
Diagnostic # 1 where reads "hda4=Mandriva 2010, and hda5=simplyMEPIS 8.0.12" should be "hda4=simplyMEPIS 8.0.12, and hda5=Mandriva 2010",
Diagnostic # 3 where reads "MEPIS is ext4" should be "Mandriva is ext4", and
Diagnostic # 6 where reads "not sure it's recognizing the (reiserfs) filesystem" should be "not sure it's recognizing the (ext4) filesystem".
UPDATE: I was able to resolve booting into openSUSE with the subsequent resolutions describing changing hard drive IDs to "sda#" in /boot/grub/menu.lst and /etc/fstab accordingly. (I had not seen these resolutions posted until recently.) i.e.: Most everything appears to work regarding reiserfs environments.
However, I still cannot get the Mandriva partition to boot, and now I suspect Clonezilla is not correctly reading/cloning Mandriva's ext4 file system. (Attempting similar/same resolutions toward Mandriva as done with openSUSE do not resolve anything.)
Please advise re. ext4 and Clonezilla.
Thanks.
Al
Revised thoughts:
1) Perhaps Clonzilla has issues w/ ext4, at least mixed w/ other fs's (?) ref. above # 6: When booting into Mandriva (ext4), … (error) “Filesystem type is ext2fs, partition type 0x83 configfile /boot/grub/menu.lst" -i.e.: not sure it's recognizing the (ext4) filesystem.
2) Clonzilla is not handling recognition of new drives- integrating new drive IDs -although perhaps this is an issue w/ some systems grub functions (?)
3) Some, perhaps many, linux OS-derived grubs are too particular (recording,,, full drive IDs when they shouldn't). i.e.: MEPIS apparently may not be doing this so has no problem booting in this scenario.
So which version of Clonezilla live did you use?
Yes, for OpenSuSE, you have to change /etc/fstab and grub config by yourself, since the defaut settings from OpenSuSE is related to hardware, which can not be cloned.
Did you run fsck.ext4 on your mandriva partition to make sure its integrity is OK?
For new hard drive, maybe the issue is on kernel. If so, give clonezilla live 20091127-karmic a try.
Steven.