Re: [Clonezilla-live] fsck.ext3: Unable to resolve 'LABEL=boot'
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Re: [Clonezilla-live] fsck.ext3: Unable to resolve 'LABEL=boot'
|
From: Steven S. <st...@nc...> - 2009-09-23 15:24:41
|
Hi Dale, Dale Stimson wrote: > Hi, > > I'm a co-worker of Davidson's (although I am remote from his > location) and have talked with Davidson about this issue, > (This email is sent with Davidson's concurrence). > > >> Which version of Clonezilla live did you use? >> > > clonezilla-live-1.2.2-26 > How about give Clonezilla live 20090919-karmic a try? I put some more in the following: > >> Are you sure the different "target" harddrive size is equal or larger >> than the original one? >> > > Yes, definitely. > > New information: > > The image restore process has been tried multiple times onto > different hard drives. Sometimes it seems to mostly work and > sometimes it fails with Fedora 11, as described. The behavior was > constant for a given target hard drive. > > However, when a hard drive for which F11 failures were occurring > was first zeroed before the restart being done, all was well: > dd if=/dev/zero of=/dev/sda > > In the two cases tried with target pre-zeroing, the resulting > restored target drive does work properly under Fedora 11. The next > test to be performed by the original poster will be to find another > "uninitialized" target drive upon which he can first verify the > original problem occurs, and then zero just the MBR area. > > The hypothesis stated in the original poster's email seems probable: > > ... the imaging process [is] perhaps not properly initializing some > portion of the destination hard drive (e.g., maybe by zeroing it > [or something in or near the MBR]) in a way that Fedora 5 does not > care about, but Fedora 11 does. > > I hope the above will help to diagnose the problem. > Thanks. When you save an image, how about entering expert mode, and choose "-q" to force Clonezilla to use partimage to save the image? Maybe it makes difference. If so, maybe some data was not correctly saved or restored by partclone... Steven. > On Sat, Sep 19, 2009 at 09:53:05PM +0800, Steven Shiau wrote: > >> Hi Davidson, >> Which version of Clonezilla live did you use? >> Are you sure the different "target" harddrive size is equal or larger >> than the original one? >> >> Steven. >> >> Davidson Hom wrote: >> >>> I am using CloneZilla to image a hard drive. This hard drive is >>> dual-boot for Fedora 5 and Fedora 11, sharing a boot partition. >>> >>> The boot partition has the Fedora 5 version of grub. >>> >>> The partition layout is: >>> /dev/sda1 /boot >>> /dev/sda2 / for FC5 >>> /dev/sda3 swap >>> /dev/sda4 extended >>> /dev/sda5 / for F11 >>> /dev/sda6 /home >>> >>> On the system/drive *from* which the image is made, all works as >>> expected. I can boot into either Fedora 5 or Fedora 11, and either of >>> those OS's can access the /home partition with no problem. >>> >>> I then restored the disk image back onto the same system with the same >>> hard drive. All was OK. >>> >>> I then restored the disk image back onto the same system with a >>> different hard drive, but the same model (presumably identical >>> hardware). The problem does occur. >>> >>> If I restore on a different system, but to the original hard drive, >>> things work. >>> >>> After restoring the different harddrive, I boot into Fedora 5 and all >>> is well. Everything is properly accessible. As expected, I get the >>> following output from running blkid: >>> >>> /dev/sda3: TYPE="swap" LABEL="swap" UUID="4167d8f6-e6a6-422f-b7f3-b63402b71b1e" >>> /dev/sda2: LABEL="/" UUID="ea61bbcb-b692-416f-96fe-3915614a2d4c" SEC_TYPE="ext2" TYPE="ext3" >>> /dev/sda1: LABEL="boot" UUID="8b50e034-d9c0-4295-bade-bde385368c8d" SEC_TYPE="ext2" TYPE="ext3" >>> /dev/sda5: UUID="93759d5a-452d-4fbe-8725-cccb71e2dc24" SEC_TYPE="ext2" TYPE="ext3" >>> /dev/sda6: UUID="7a78f920-a0ac-4706-9b80-2e3a3b69627e" SEC_TYPE="ext2" TYPE="ext3" LABEL="home" >>> >>> Output of ls -ld /dev/sda*: >>> brw-r----- 1 root disk 8, 0 Sep 17 09:20 sda >>> brw-r----- 1 root disk 8, 1 Sep 17 09:20 sda1 >>> brw-r----- 1 root disk 8, 2 Sep 17 09:20 sda2 >>> brw-r----- 1 root disk 8, 3 Sep 17 09:20 sda3 >>> brw-r----- 1 root disk 8, 4 Sep 17 09:20 sda4 >>> brw-r----- 1 root disk 8, 5 Sep 17 09:20 sda5 >>> brw-r----- 1 root disk 8, 6 Sep 17 09:20 sda6 >>> >>> However, when I boot into Fedora 11, the boot fails with the diagnostic: >>> fsck.ext3: Unable to resolve 'LABEL=boot' >>> dumping me into the shell, from which I see: >>> >>> "fdisk -l" output: >>> >>> Device Boot Start End Blocks Id System >>> /dev/sda1 1 13 104391 83 Linux >>> /dev/sda2 14 2563 20482875 83 Linux >>> /dev/sda3 2564 3073 4096575 82 Linux swap / Solaris >>> /dev/sda4 3074 19457 131604480 5 Extended >>> /dev/sda5 3074 5684 20971520 83 Linux >>> /dev/sda6 5684 19457 110632927+ 83 Linux >>> >>> blkid output: >>> /dev/sda5: UUID="0008f94193759d5a-452d-4fbe-8725-cccb71e2dc24" SEC_TYPE="ext2" TYPE="ext3" >>> /dev/sda6: LABEL="home" UUID="7a78f920-a0ac-4706-9b80-2e3a3b69627e" SEC_TYPE="ext2" TYPE="ext3" >>> >>> Output of ls -ld /dev/sda*: >>> brw-rw----. 1 root disk 8, 0 2009-09-17 09:42 sda >>> brw-rw----. 1 root disk 8, 5 2009-09-17 09:42 sda5 >>> brw-rw----. 1 root disk 8, 6 2009-09-17 09:42 sda6 >>> >>> It's worthy of note that partitions 4, 5, and 6 were created during >>> the installation of Fedora 11. >>> >>> I will also note that if I remove the F11 /etc/fstab entry for the >>> boot partition, that F11 boots OK, but still only recognizes sda5 and >>> sda6 as partitions. >>> >>> So, I am puzzled: >>> >>> 1. My configuration works from the system before imaging. >>> Both Fedora 5 and Fedora 11 recognize all partitions. >>> >>> 2. My configuration works from the system after imaging, >>> for Fedora 5, but not Fedora 11. >>> Fedora 11 is recognizing only two of the partitions. >>> >>> 3. My configuration works if I restore the exact same hard drive >>> (not just the same hard drive model), both both F5 and F11. >>> >>> Conclusion: ??? >>> This is a hard one, but is the imaging process perhaps not properly >>> initializing some portion of the destination hard drive (e.g., maybe >>> by zeroing it) in a way that Fedora 5 does not care about, but Fedora >>> 11 does. >>> >>> Any help appreciated! >>> >>> _______________________________________________ >>> Clonezilla-live mailing list >>> Clo...@li... >>> https://lists.sourceforge.net/lists/listinfo/clonezilla-live >>> >> -- >> Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> >> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw >> Public Key Server PGP Key ID: 1024D/9762755A >> Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A >> _______________________________________________ >> Clonezilla-live mailing list >> Clo...@li... >> https://lists.sourceforge.net/lists/listinfo/clonezilla-live >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
