I am trying to update the Wife’s machine from 11.3 to 11.4. I have cloned the drive. I have edited /boot/grub/menu.lst, /boot/grub/device.map and /etc/fstab to match up with the new drives ID. i can boot it in the failsafe mode and am posting this from it right now but I get a error 11 when I try and boot it in the normal mode.
/boot/grub/menu.lst
# Modified by YaST2. Last modification on Tue Sep 27 21:02:34 PDT 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.10-0.2
root (hd0,1
kernel /boot/vmlinuz-2.6.34.10-0.2-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part2 resume=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part2 splash=silent quiet showopts vga=0x31a
initrd /boot/initrd-2.6.34.10-0.2-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3 - 2.6.34.10-0.2
root (hd0,1)
kernel /boot/vmlinuz-2.6.34.10-0.2-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part2 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.34.10-0.2-desktop
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.8-0.2
root (hd0,1)
kernel /boot/vmlinuz-2.6.34.8-0.2-desktop root=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part2 resume=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part1 splash=silent quiet showopts vga=0x31a
initrd /boot/initrd-2.6.34.8-0.2-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3 - 2.6.34.8-0.2
root (hd0,1)
kernel /boot/vmlinuz-2.6.34.8-0.2-desktop root=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part2 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.34.8-0.2-desktop
/boot/grub/device.map
(hd0) /dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734
/etc/fstab
/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part2 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5V330734-part3 /home ext4 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Here is where I believe the error lies in /etc/grub.conf as this is were the bootloader throws a error in YAST bootloader when I tried to save it.
This may reference the old seagate drive not the new cloned WD drive.
setup --stage2=/boot/grub/stage2 --force-lba (hd0,3307343307341) (hd0,1)
quit
I also believe the bootloader may be in the mbr 
As I if I didn’t know better when I made the original 11.3 install.
What am I doing wrong here?
The closing parenthesis is missing here:
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.10-0.2
root (hd0,1**)**
please_try_again thanks for a second set of eyes. It looks like there were some errors on copying in the cloning as I didn’t touch that part of the file or another file where I found something amiss.
I have the drive under test in Pmagic right now. The guy on in the brow shirt just dropped it on my front porch. Even though it was packaged in a WD shipping box and packed again in a box full of peanuts it may have been damaged. I am not overly paranoid about such things as WD is very good on their Warranty replacement and Newegg gives you 30 days minus a restocking fee. The brown truck had sailed away by the time I got up to the front door so what are you to do? It’s not worth the grief dealing with UPS.
I am doing a test long on the drive in question then will use Clonzilla to re-clone it bit for bit this time.
Glad I don’t have a job. This is work enough for me. 
For info, if you use disk/by-uuid rather than disk/by-id in Grub menu and /etc/fstab, you won’t need to edit these files after cloning hard drives. This notation is better for cloning if you intend to use the cloned drive on another machine, while the disk/by-id is safer if you keep the two drives on the same machine. You can find out the uuids with the command blkid or the partinfo script, which displays both IDs and UUIDs of all partitions. You can also choose to use this notation during setup by selecting “mount by UUID” in fstab options (while partitioning in “expert” mode):
To get an overview of the current device mapping, you can use findgrub with the option -M, as shown in this post: Looking for Grub and Windows bootloader in all partitions. - Page 12. Get the latest version though.
I don’t know what Clonzilla does better (but probably a couple things), as I have always used dd to clone hard disks.
It really isn’t a problem for me to edit the few files for the new drive. ls -l /dev/disk/by-* gives all the information I need and can be done from Pmagic when the cloning is done by cutting and pasting the drive Id which I learned the other day . I am not even sure /boot/grub/device.map needs editing as I didn’t do that file when I did this machine the other day. The old drive is coming out of the machine as it’s a hot running, energy demanding old dog which I don’t trust all that much.
If you don’t mind editing a few files, then I would recommend editing /boot/grub/device.map too. It is normally only used when you install Grub - and get created at this point under openSUSE (not all distros do this). So as long as you don’t reinstall Grub and if the machine only has one HD, it doesn’t matter (It is not used to boot the system). However some programs (including my scripts but not only) read device.map to display info or before taking actions (updategrub will abort if it finds a wrong device.map). Some system scripts like /usr/lib/bootloader/bootloader_entry also cat device.map too - this one just for logging purpose though. In fact, many users have a wrong device.map after removing/replacing a hard disk and don’t bother. It’s OK (up to a certain point). But a correct device.map doesn’t hurt for sure.
On 2011-09-28 06:36, FlameBait wrote:
>
> I am trying to update the Wife’s machine from 11.3 to 11.4. I have
> cloned the drive. I have edited /boot/grub/menu.lst,
> /boot/grub/device.map and /etc/fstab to match up with the new drives ID.
> i can boot it in the failsafe mode and am posting this from it right now
> but I get a error 11 when I try and boot it in the normal mode.
For the next time.
info grub → Node: Stage2 errors
11 : Unrecognized device string
This error is returned if a device string was expected, and the
string encountered didn’t fit the syntax/rules listed in the *note
Filesystem::.
So, look for devices (a,b). One has a missing parenthesis, as you know
Pity grub doesn’t say which line is in error.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
The reason for the errors was a bad job of cloning the drive with G4L. This was not the only error I found looking at files. After testing the drive for defects I re-did it with Clonezilla. I edited the necessary files and it’s just rebooting from reboot after the zypper dup process.
