« previous next »
Pages: 1 2 [3] 4   Go Down

Author Topic: Clonezilla Restore Failure on New HD [SOLVED]  (Read 7556 times)

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #30 on: May 10, 2012, 05:38:47 PM »
Quote from: bilyo on May 10, 2012, 05:19:08 PM
sent 14934999515 bytes  received 2192486 bytes  7798064.21 bytes/sec
total size is 14926001496  speedup is 1.00

It appears to have worked just fine. It's amazing what you can do when you speak the language properly.

Isn't it though?  ;D ;D

Now we basically start over again, but in reverse. Shut down, but the new drive in place, and again boot to the liveCD. Start with the umount -a command, followed by the fdisk -l command, so I can see what the partitions on the new drive presently look like.

Post your results.

Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #31 on: May 11, 2012, 09:04:31 AM »
[root@localhost ~]# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3bb2cafd

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       15936   128000992+   7  HPFS/NTFS
/dev/sda2           15936       47806   256000000    7  HPFS/NTFS
/dev/sda3           47806       63742   128000000   83  Linux
/dev/sda4           63742      121602   464760832    5  Extended
/dev/sda5           63742       64252     4096000   82  Linux swap / Solaris
/dev/sda6           64252       96122   256000000   83  Linux

Disk /dev/sdb: 1500.3 GB, 1500299395072 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003a97d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       95612   768003358+   7  HPFS/NTFS
/dev/sdb2           95613      182401   697132642+  83  Linux
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #32 on: May 11, 2012, 10:58:46 AM »
Quote from: bilyo on May 11, 2012, 09:04:31 AM
[root@localhost ~]# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3bb2cafd

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       15936   128000992+   7  HPFS/NTFS
/dev/sda2           15936       47806   256000000    7  HPFS/NTFS
/dev/sda3           47806       63742   128000000   83  Linux
/dev/sda4           63742      121602   464760832    5  Extended
/dev/sda5           63742       64252     4096000   82  Linux swap / Solaris
/dev/sda6           64252       96122   256000000   83  Linux

Disk /dev/sdb: 1500.3 GB, 1500299395072 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003a97d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       95612   768003358+   7  HPFS/NTFS
/dev/sdb2           95613      182401   697132642+  83  Linux


If  you have not done so yet, create the two mount point directories.

[root@localhost ~]# mkdir -p /mnt/here /mnt/there                 <Enter>

Then mount the two partitions we'll work with first;

[root@localhost ~]# mount /dev/sdb2 /mnt/here                    <Enter>

[root@localhost ~]# mount /dev/sda6 /mnt/there                    <Enter>

... then copy the data from the /mnt/here/home directory to the new /home partition;

[root@localhost ~]# rsync -av /mnt/here/home/ /mnt/there                <Enter>

Remember the trailing / in /mnt/here/home/, so only the contents of the directory get copied.

When returned to the prompt, unmount /dev/sda6 and mount /dev/sda3 on /mnt/there, then copy the contents of the /mnt/here/root directory to /mnt/there.

[root@localhost ~]# umount /mnt/there                    <Enter>

[root@localhost ~]# mount /dev/sda3 /mnt/there                    <Enter>

[root@localhost ~]# rsync -av /mnt/here/root/ /mnt/there                <Enter>

For ease of editing the two files we'll need to edit, we next LABEL the Linux partitions.

[root@localhost ~]# tune2fs -L home /dev/sda6                  <Enter>

[root@localhost ~]# tune2fs -L root /dev/sda3                  <Enter>

[root@localhost ~]# swaplabel -L swap /dev/sda5                  <Enter>

In the next step, we need to edit two text files, /mnt/there/etc/fstab and /mnt/there/boot/grub/menu.lst, but first I need to see the contents of each, to know what to edit.

[root@localhost ~]# cat /mnt/there/etc/fstab                      <Enter>

[root@localhost ~]# cat /mnt/there/boot/grub/menu.lst                      <Enter>

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #33 on: May 11, 2012, 01:33:54 PM »
Results of rsync -av /mnt/here/home/ /mnt/there:
sent 14935000282 bytes  received 2192486 bytes  26274745.41 bytes/sec
total size is 14926001496  speedup is 1.00
[root@localhost ~]#

Results of rsync -av /mnt/here/root/ /mnt/there:
sent 40908026262 bytes  received 2564923 bytes  29613167.71 bytes/sec
total size is 40893480303  speedup is 1.00
[root@localhost ~]#

Before I proceed with the next step of labeling, may I ask if it is needed because I labeled them as you stated, root, swap, and home, when I created the partitions?  Just curious.
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #34 on: May 11, 2012, 01:42:23 PM »
Quote from: bilyo on May 11, 2012, 01:33:54 PM
Results of rsync -av /mnt/here/home/ /mnt/there:
sent 14935000282 bytes  received 2192486 bytes  26274745.41 bytes/sec
total size is 14926001496  speedup is 1.00
[root@localhost ~]#

Results of rsync -av /mnt/here/root/ /mnt/there:
sent 40908026262 bytes  received 2564923 bytes  29613167.71 bytes/sec
total size is 40893480303  speedup is 1.00
[root@localhost ~]#

Before I proceed with the next step of labeling, may I ask if it is needed because I labeled them as you stated, root, swap, and home, when I created the partitions?  Just curious.


If you are sure of the actual labels, that's fine. Check with;

[root@localhost ~]# blkid                              <Enter>

Post your results.

Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #35 on: May 11, 2012, 01:49:55 PM »
[root@localhost ~]# cat /mnt/there/etc/fstab
# Entry for /dev/sda1 :
UUID=9e65403b-ef54-4b33-a754-2d85492d49bc / ext4 defaults 1 1
none /dev/pts devpts defaults 0 0
# Entry for /dev/sda3 :
UUID=89d6e657-9a50-40d4-9ec0-ae9d29e8ff3b /home ext4 defaults 1 2
# THE FOLLOWING LINE REVISED "OPTIONS" TO ALLOW user TO MOUNT /DEV/SDB2
# /dev/sdb2 /media/pclos ext4 defaults 0 0
/dev/sdb2 /media/pclos ext4 rw,suid,dev,exec,auto,user,async 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda2 :
UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784 swap swap defaults 0 0
[root@localhost ~]# blkid
/dev/sda1: UUID="3738EB9D793FB5E7" LABEL="Win7" TYPE="ntfs"
/dev/sda5: UUID="94c393f9-234d-4515-9ad2-46538f747eea" TYPE="swap" LABEL="Swap"
/dev/sda6: LABEL="home" UUID="6f6f804f-6d38-42d0-854f-8f4edb0a82c1" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/sda2: UUID="6223E70562AA175C" LABEL="Win7Data" TYPE="ntfs"
/dev/sda3: LABEL="root" UUID="8499ef8e-d8b0-408b-8238-6e202798120f" TYPE="ext4"
/dev/sdb1: UUID="A826CB6626CB345A" LABEL="ElementsWin7" TYPE="ntfs"
/dev/sdb2: LABEL="ElementsPCLOS" UUID="f7d563e6-8e66-4a75-99dc-126734c0aea4" TYPE="ext4"
[root@localhost ~]# cat /mnt/there/boot/grub/menu.lst
timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  vmalloc=256M resume=UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  vmalloc=256M resume=UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  failsafe vmalloc=256M
initrd (hd0,0)/boot/initrd.img
[root@localhost ~]#
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #36 on: May 11, 2012, 02:59:14 PM »
Quote from: bilyo on May 11, 2012, 01:49:55 PM
[root@localhost ~]# cat /mnt/there/etc/fstab
# Entry for /dev/sda1 :
UUID=9e65403b-ef54-4b33-a754-2d85492d49bc / ext4 defaults 1 1
none /dev/pts devpts defaults 0 0
# Entry for /dev/sda3 :
UUID=89d6e657-9a50-40d4-9ec0-ae9d29e8ff3b /home ext4 defaults 1 2
# THE FOLLOWING LINE REVISED "OPTIONS" TO ALLOW user TO MOUNT /DEV/SDB2
# /dev/sdb2 /media/pclos ext4 defaults 0 0
/dev/sdb2 /media/pclos ext4 rw,suid,dev,exec,auto,user,async 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda2 :
UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784 swap swap defaults 0 0
[root@localhost ~]# blkid
/dev/sda1: UUID="3738EB9D793FB5E7" LABEL="Win7" TYPE="ntfs"
/dev/sda5: UUID="94c393f9-234d-4515-9ad2-46538f747eea" TYPE="swap" LABEL="Swap"
/dev/sda6: LABEL="home" UUID="6f6f804f-6d38-42d0-854f-8f4edb0a82c1" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/sda2: UUID="6223E70562AA175C" LABEL="Win7Data" TYPE="ntfs"
/dev/sda3: LABEL="root" UUID="8499ef8e-d8b0-408b-8238-6e202798120f" TYPE="ext4"
/dev/sdb1: UUID="A826CB6626CB345A" LABEL="ElementsWin7" TYPE="ntfs"
/dev/sdb2: LABEL="ElementsPCLOS" UUID="f7d563e6-8e66-4a75-99dc-126734c0aea4" TYPE="ext4"
[root@localhost ~]# cat /mnt/there/boot/grub/menu.lst
timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  vmalloc=256M resume=UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  vmalloc=256M resume=UUID=7c9519ab-95a2-4ccd-bb27-9d72ec428784
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=9e65403b-ef54-4b33-a754-2d85492d49bc  failsafe vmalloc=256M
initrd (hd0,0)/boot/initrd.img
[root@localhost ~]#


Good thing you checked blkid, as your swap LABEL is Swap. (case sensitive and all that)

The /mnt/there/etc/fstab needs to be edited to read;

-------------------------------------------------------------------------------------------------------------
# Entry for /dev/sda3 :
LABEL=root / ext4 defaults 1 1
none /dev/pts devpts defaults 0 0
# Entry for /dev/sda6 :
LABEL=home /home ext4 defaults 1 2
# THE FOLLOWING LINE REVISED "OPTIONS" TO ALLOW user TO MOUNT /DEV/SDB2
# /dev/sdb2 /media/pclos ext4 defaults 0 0
/dev/sdb2 /media/pclos ext4 rw,suid,dev,exec,auto,user,async 0 0                <-- This line bothers me... fix later
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
LABEL=Swap swap swap defaults 0 0

-------------------------------------------------------------------------------------------------------------

The /mnt/there/boot/grub/menu.lst needs these edits;

-------------------------------------------------------------------------------------------------------------
timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,2)/boot/gfxmenu
default 0

title linux
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=root  vmalloc=256M resume=LABEL=Swap splash=silent vga=788
initrd (hd0,2)/boot/initrd.img

title linux nonfb                   <-- Remove the - between linux and nonfb
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=root  vmalloc=256M resume=LABEL=Swap
initrd (hd0,2)/boot/initrd.img

title failsafe
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=root  failsafe vmalloc=256M
initrd (hd0,2)/boot/initrd.img

title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1

-------------------------------------------------------------------------------------------------------------

Assuming you are using the official KDE release, the edits can be done with kwrite, using the following;

[root@localhost ~]# kwrite /mnt/there/etc/fstab                  <Enter>

Edit as shown above, then save the file.

[root@localhost ~]# kwrite /mnt/there/boot/grub/menu.lst                  <Enter>

Edit as shown above, then save the file.

Only after the above edits have been done, you need to create a new initrd image for your default kernel. To know what that is, we need the following information;

[root@localhost ~]# ls -l /mnt/there/boot |grep vm                    <Enter>

[root@localhost ~]# ls -l /mnt/there/boot |grep init                    <Enter>

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #37 on: May 11, 2012, 03:50:20 PM »
Using Gnome. Gedit seems to work the same way.  Note that last two results are out of order. Also, please note that in the /grub/menu.lst file in the next line after "title linux nonfb" there is a hyphen between linux and nonfb. Is it OK there?

# Entry for /dev/sda3 :
LABEL=root / ext4 defaults 1 1
none /dev/pts devpts defaults 0 0
# Entry for /dev/sda6 :
LABEL=home /home ext4 defaults 1 2
# THE FOLLOWING LINE REVISED "OPTIONS" TO ALLOW user TO MOUNT /DEV/SDB2
# /dev/sdb2 /media/pclos ext4 defaults 0 0
/dev/sdb2 /media/pclos ext4 rw,suid,dev,exec,auto,user,async 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
LABEL=Swap swap swap defaults 0 0

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,2)/boot/gfxmenu
default 0

title linux
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=root
vmalloc=256M resume=LABEL=Swap splash=silent vga=788
initrd (hd0,2)/boot/initrd.img

title linux nonfb
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=root
vmalloc=256M resume=LABEL=Swap
initrd (hd0,2)/boot/initrd.img

title failsafe
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=root
failsafe vmalloc=256M
initrd (hd0,2)/boot/initrd.img

title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1

[root@localhost ~]# ls -l /mnt/there/boot |grep init
-rw------- 1 root root 7845821 2010-11-30 18:02 initrd-2.6.33.5-pclos1.bfs.img
lrwxrwxrwx 1 root root      30 2012-05-11 14:03 initrd.img -> initrd-2.6.33.5-pclos1.bfs.img

[root@localhost ~]# ls -l /mnt/there/boot |grep vm
lrwxrwxrwx 1 root root      27 2012-05-11 14:03 vmlinuz -> vmlinuz-2.6.33.5-pclos1.bfs
-rw-r--r-- 1 root root 2059536 2010-05-30 02:42 vmlinuz-2.6.33.5-pclos1.bfs
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #38 on: May 11, 2012, 04:51:54 PM »
Quote from: bilyo on May 11, 2012, 03:50:20 PM
Using Gnome. Gedit seems to work the same way.  Note that last two results are out of order. Also, please note that in the /grub/menu.lst file in the next line after "title linux nonfb" there is a hyphen between linux and nonfb. Is it OK there?

# Entry for /dev/sda3 :
LABEL=root / ext4 defaults 1 1
none /dev/pts devpts defaults 0 0
# Entry for /dev/sda6 :
LABEL=home /home ext4 defaults 1 2
# THE FOLLOWING LINE REVISED "OPTIONS" TO ALLOW user TO MOUNT /DEV/SDB2
# /dev/sdb2 /media/pclos ext4 defaults 0 0
/dev/sdb2 /media/pclos ext4 rw,suid,dev,exec,auto,user,async 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
LABEL=Swap swap swap defaults 0 0

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,2)/boot/gfxmenu
default 0

title linux
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=root
vmalloc=256M resume=LABEL=Swap splash=silent vga=788
initrd (hd0,2)/boot/initrd.img

title linux nonfb
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=root
vmalloc=256M resume=LABEL=Swap
initrd (hd0,2)/boot/initrd.img

title failsafe
kernel (hd0,2)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=root
failsafe vmalloc=256M
initrd (hd0,2)/boot/initrd.img

title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1

[root@localhost ~]# ls -l /mnt/there/boot |grep init
-rw------- 1 root root 7845821 2010-11-30 18:02 initrd-2.6.33.5-pclos1.bfs.img
lrwxrwxrwx 1 root root      30 2012-05-11 14:03 initrd.img -> initrd-2.6.33.5-pclos1.bfs.img

[root@localhost ~]# ls -l /mnt/there/boot |grep vm
lrwxrwxrwx 1 root root      27 2012-05-11 14:03 vmlinuz -> vmlinuz-2.6.33.5-pclos1.bfs
-rw-r--r-- 1 root root 2059536 2010-05-30 02:42 vmlinuz-2.6.33.5-pclos1.bfs


The hyphen in the BOOT_IMAGE=linux-nonfb has no affect on the boot menu, whereas the one in the title line prevents that option from being available.

First we have to create a proper chroot environment to work in, then create the actual new initrd image

[root@localhost ~]# mount -o bind /dev /mnt/there/dev                 <Enter>

[root@localhost ~]# mount -o bind /proc /mnt/there/proc                 <Enter>

[root@localhost ~]# mount -o bind /sys /mnt/there/sys                 <Enter>

[root@localhost ~]# chroot /mnt/there                           <Enter>

The prompt should change, to indicate you are now in the / directory of the chroot environment;

[root@localhost /]#

All commands from this point will be executed as if the chroot environment was the running system.

[root@localhost /]# cd /boot                         <Enter>

[root@localhost boot]# mv initrd-2.6.33.5-pclos1.bfs.img initrd-2.6.33.5-pclos1.bfs.img.old                <Enter>

[root@localhost boot]# mkinitrd -v initrd-2.6.33.5-pclos1.bfs.img 2.6.33.5-pclos1.bfs                  <Enter>

You should again see a lot of text scrolling up the screen. When returned to the prompt, the build is complete. To verify the build;

[root@localhost boot]# ls -l |grep init                  <Enter>

To leave the chroot environment;

[root@localhost boot]# exit                     <Enter>

[root@localhost ~]# umount /mnt/there/sys              <Enter>

[root@localhost ~]# umount /mnt/there/proc              <Enter>

[root@localhost ~]# umount /mnt/there/dev              <Enter>

[root@localhost ~]# umount /mnt/there              <Enter>

[root@localhost ~]# umount /mnt/here              <Enter>

One could just do a umount -a command, but I've had the umount of the /dev directory hang at times, so I prefer doing the umounts in the reverse order of the original mounts.

Last item is installing grub to the MBR on the new hard drive. Use the instructions here;

http://www.pclinuxos.com/forum/index.php/topic,62786.msg508062.html#msg508062

When done with that, reboot, remove the liveCD when requested, then select linux from the boot menu. If everything went as it should, which it seems to have, so far, you should experience a normal boot procedure.

Post your results.



Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #39 on: May 11, 2012, 06:18:41 PM »
Following is result of ls -l |grep init:

[root@localhost boot]# ls -l |grep init
-rw------- 1 root root 3847794 May 11 18:59 initrd-2.6.33.5-pclos1.bfs.img
-rw------- 1 root root 7845821 Nov 30  2010 initrd-2.6.33.5-pclos1.bfs.img.old
lrwxrwxrwx 1 root root      30 May 11 14:03 initrd.img -> initrd-2.6.33.5-pclos1.bfs.img

umount /mnt/there/dev and umount /mnt/there returned "device is busy". The only other information provided is a parenthetical statement starting with (In some cases useful...).
umount -a returned the same except "umount /: Device busy" was added to list.

Stopping until I hear from you.
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #40 on: May 11, 2012, 07:15:06 PM »
Quote from: bilyo on May 11, 2012, 06:18:41 PM
Following is result of ls -l |grep init:

[root@localhost boot]# ls -l |grep init
-rw------- 1 root root 3847794 May 11 18:59 initrd-2.6.33.5-pclos1.bfs.img
-rw------- 1 root root 7845821 Nov 30  2010 initrd-2.6.33.5-pclos1.bfs.img.old
lrwxrwxrwx 1 root root      30 May 11 14:03 initrd.img -> initrd-2.6.33.5-pclos1.bfs.img

umount /mnt/there/dev and umount /mnt/there returned "device is busy". The only other information provided is a parenthetical statement starting with (In some cases useful...).
umount -a returned the same except "umount /: Device busy" was added to list.

Stopping until I hear from you.

Did you exit out of the chroot environment before issuing those umount commands?
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline bilyo

  • Sr. Member
  • ****
  • Posts: 267
Re: Clonezilla Restore Failure on New HD
« Reply #41 on: May 11, 2012, 07:51:55 PM »
Yes.

Would it break anything to just reboot the liveCD  and then fix GRUB?
« Last Edit: May 11, 2012, 08:21:20 PM by bilyo »
Logged

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #42 on: May 11, 2012, 08:54:00 PM »
Quote from: bilyo on May 11, 2012, 07:51:55 PM
Yes.

Would it break anything to just reboot the liveCD  and then fix GRUB?

Probably not. I have about 20 installations on this machine, so don't really use the liveCD much; just boot to another installation. If you've closed gedit after saving the edited files, I don't think anything left in memory can hurt anything at all.

Grub will be fine as a single procedure from a reboot to the liveCD. Nothing needs to be mounted, just run the procedure as in the link.

Once you can boot into the installation on the hard drive, you might want to consider installing a newer kernel. That one's pretty old, and Texstar warned us all to install the 2.6.38 kernel, to avoid problems with the new rpm packages, last summer.
« Last Edit: May 11, 2012, 08:57:53 PM by Old-Polack »
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Xenaflux

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3834
Re: Clonezilla Restore Failure on New HD
« Reply #43 on: May 11, 2012, 09:26:15 PM »
OP and bilyo

My apologies for the interuption // attempted hijacking   ;D

Quote
I have about 20 installations on this machine

I would be interested in the knowledge regarding above.( as I don't get over 15 )
Link to .... will be fine.
If you don't have time, also OK as it is certainly not a pressing matter
Thanks
Logged
The great thing in this world is not so much where we stand,
as in what direction we are moving.
                                                    (Oliver Wendell Holmes )

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11541
  • ----IOFLU----
Re: Clonezilla Restore Failure on New HD
« Reply #44 on: May 11, 2012, 10:10:38 PM »
Quote from: Xenaflux on May 11, 2012, 09:26:15 PM
OP and bilyo

My apologies for the interuption // attempted hijacking   ;D

Quote
I have about 20 installations on this machine

I would be interested in the knowledge regarding above.( as I don't get over 15 )
Link to .... will be fine.
If you don't have time, also OK as it is certainly not a pressing matter
Thanks

There must be a real question there, somewhere.  ;D

Pray tell, what might it be?
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...
Pages: 1 2 [3] 4   Go Up
« previous next »