When I use Clonezilla I have a DRBL server setup and send the images over to my server. I have successfully without any issues done the following: WINXP Machine ( 1 HD) clone & restore WinXP & Ubuntu 10.04 ( 1 HD) Clone & restore ** This system I had an issue with but that was only because the HD had bad sectors at the beginning of the drive, not allowing Windows to shut down properly, once I mounted the drive in Linux and ran ntfsfix (I believe it was) everything went off without a hitch! System starts up and runs good as new! Win7 & Ubuntu 10.04 ( 2 HDs) Clone & restore ** This system I did each drive individually to separate folders, reason being is that I was upgrading each to a larger drive, my Win7 went onto a new drive, and the Ubuntu went onto the old Win7 drive. When I run Clonezilla I image the drive, not partitions. Good Luck! Chuq On Sat, 2010-08-07 at 16:31 -0400, Tom Brown wrote: > I wish I had the time and skill to determine whether the issue is with > Clonezilla Live’s scripts, Debian (Clonezilla Live is Debian based) or > some Clonezilla tweak to, or misunderstanding of, udev. All I know is > Clonezilla Live v1.2.2-26 no longer warrants absolute trust. > > > > Here is my SATA drive line up in Slack according to /dev/disk/by-id. > The line up is rock solid, always matches /etc/fstab and is the way I > cabled the drives. > > > > /dev/sda – WD 2500 (internal; 250 GB; 3 partitions for swap, / > and /home) > > /dev/sdb – WD 1001FALS (internal 1TB; 1 partition; BackupPC partition) > > /dev/sdc – WD 1001FALS (external; 1TB; 1 partition; BackupPC partition > clone) > > > > Here is the Clonezilla SATA line up according to /dev/disk/by-id in > the same server. This is so wrong. > > > > /dev/sda – WD1001FALS (external; 1 partition; BackupPC clone) > > /dev/sdb – WD2500 (internal; 3 partitions) > > /dev/sdc - WD1001FALS (internal; 3 partitions; single BackupPC > partition destroyed) > > > > I know how to double check drive assignments in Clonezilla Live and > hopefully compensate for the squirrely assignments. One piece of > critical information is the unique ID number assigned to each of the > 1TB drives since both are model WD 1001FALS. /dev/disk/by-id gives you > the unique IDs. > > > > btw, once you leave the graphical script to check and record drive > assignments, you need the root password to restart Clonezilla Live at > the command line. > > > > sudo su (no pwd) > > clonezilla > > > > Wish me good luck restoring the BackupPC partition. > > > Tom -- > > > > > > > > ______________________________________________________________________ > > From:frgeek-michiana-bounce@xxxxxxxxxxxxx > [mailto:frgeek-michiana-bounce@xxxxxxxxxxxxx] On Behalf Of Richard > Zimmerman > Sent: Friday, August 06, 2010 21:19 > To: frgeek-michiana@xxxxxxxxxxxxx > Subject: [frgeek-michiana] Re: Clonezilla caution > > > > > > > <Tom> > > I have never had Slackware change a mount point on me; whatever is > written in /etc/fstab is gospel. I know udev has changed things on > Debian boxes in the past. Ethernet interface assignments on our > warehouse server used to change mysteriously until Goose hard coded > the assignments in a udev config file. > > > </Tom> > > > > > > Actually any OS that uses udev can suffer from this. VL did too to an > extent. As for the ETh('s) I had to > use :/etc/udev/rules.d/10-network.rules to force an eth name to a mac > address. > > > > > > Richard > > > > > > > > > > > --- > Richard "Goose" Zimmerman, ke4rit > Mishawaka, IN > > > > > > > > > > > >