clonezilla-live — Anything about Clonezilla live

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[Michal S. <hra...@gm...>]

On 21 March 2012 07:15,  <jum...@hu...> wrote:
> I forgot to mention that I don't know how to make the partition sizes on the
> destination hard drive EXACTLY the same as the partition sizes on the source
> hard drive using only Gparted. I mean, I can only see the partition sizes
> down to a MiB, not a byte, so there's no way to know that the destination
> partition sizes are EXACTLY the same. This is actually why I initially did a
> clean installation of Windows on the destination hard drive; I figured doing
> so would create partitions that were the right size, even if they weren't
> blank. But as I mentioned, that method ended in failure; Windows failed to
> boot after the restoration. This should NOT have happened because Clonezilla
> is supposed to overwrite the destination partitions with data from the image
> whether the destination partitions are blank or not.
>
> Despite trying both methods, Windows still fails to boot. Please help! I've
> read the information at both Steven's links, but I still haven't been able
> to get it working.

Hello,

try booting the source drive with the shrunk partition to make sure
the issue is with the cloning, not the source.

If you were too aggressive in rearranging the partitions to shrink
them  windows will not boot without using some rescue tools to fix the
boot loader.

When doing whole disk restore you should get exact same disk layout
and windows should boot provided the geometry of the disk as faked by
the PC bios is same even for the smaller disk. This may be an issue
for disks smaller then like 80GB and old bioses.

Also note that before moving windows installation to a new hardware
you should make some preparation steps. Sometimes moving (or imaging)
the disk into a different machine works but sometimes you have to make
sure drivers for the new hardware get loaded, you get the correct disk
geometry, etc.

HTH

Michal

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

I forgot to mention that I don't know how to make the partition sizes
on the destination hard drive EXACTLY the same as the partition sizes
on the source hard drive using only Gparted. I mean, I can only see
the partition sizes down to a MiB, not a byte, so there's no way to
know that the destination partition sizes are EXACTLY the same. This
is actually why I initially did a clean installation of Windows on the
destination hard drive; I figured doing so would create partitions
that were the right size, even if they weren't blank. But as I
mentioned, that method ended in failure; Windows failed to boot after
the restoration. This should NOT have happened because Clonezilla is
supposed to overwrite the destination partitions with data from the
image whether the destination partitions are blank or not.

Despite trying both methods, Windows still fails to boot. Please help!
I've read the information at both Steven's links, but I still haven't
been able to get it working.

[Clonezilla-live] Sorry for the extra messages

[<jum...@hu...>]

Sorry about the extra messages. My email provider was having strange
problems and kept giving me errors. I got some kind of error every
time I clicked send, so I thought they were never sent. Apparently
they were. I apologize.

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, I just finished testing your method. I restored the image, but
Windows 7 wouldn't start. I tried making the image again after
restarting the source drive's installation of Windows. I got a
different type of problem, but again it wouldn't start. The image
failed to capture what was in the original installation of Windows on
my source drive.

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, I tried your method but after I restored the image to a blank,
smaller hard drive, Windows 7 failed to start. Some part of the
original drive was there because Windows 7 was at least present on the
target disk, albeit in a damaged state. I didn't try to enlarge the
second partition to see if it would make Windows bootable. Any
suggestions?

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, I tried your method but after I restored the image to a blank,
smaller hard drive, Windows 7 failed to start. Some part of the
original drive was there because Windows 7 was at least present on the
target disk, albeit in a damaged state. I didn't try to enlarge the
second partition to see if it would make Windows bootable. Any
suggestions?

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, I tried your method but after I restored the image to a blank,
smaller hard drive, Windows 7 failed to start. Some part of the
original drive was there because Windows 7 was at least present on the
target disk, albeit in a damaged state. I didn't try to enlarge the
second partition to see if it would make Windows bootable. Any
suggestions?

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, I tried your method but after I restored the image to a blank,
smaller hard drive, Windows 7 failed to start. Some part of the
original drive was there because Windows 7 was at least present on the
target disk, albeit in a damaged state. I didn't try to enlarge the
second partition to see if it would make Windows bootable. Any
suggestions?

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[Gary S. <gar...@gm...>]

You seem to have it now.

Understand that clonezilla is basically an excellent collection of scripts
and programs.

When doing a whole disk, it grabs the mbr and partition table. Each
partition it finds gets processed sequentially and separately.

the problem of large to small disk is more a problem of ntfsclone and
partimage that clonezilla uses to clone an ntfs partition. As long as each
instance of ntfs partition has room to fit  you're good to go.

As far as unpartitioned space, as long as it is on the back end, it gets
ignored by clonezilla.

Regards,
Gary Smithe
On Mar 20, 2012 9:01 PM, <jum...@hu...> wrote:

> Gary, that's an interesting method. I'm almost done reading Steven's
> document, but while waiting to hear from him, I want to try your method
> too. To be clear, when you say "make your largest partition small enough so
> that the whole drive will fit on the destination", "whole drive" does not
> include the unallocated space at the end of all the partitions, right? If I
> understood you correctly, your method involves:
>
> 1. Shrink partitions, and move all unallocated space to the end of the
> drive if necessary
> 2. Use Clonezilla to save the whole disk to an image. I assume Clonezilla
> only sees partitions as part of the total disk size and NOT the unallocated
> space?
> 3. Restore the image to a smaller hard drive whose size is bigger than the
> total size of all the resized partitions on source drive.
>
> Is this right? If this works, it's even easier than Steven's method
> because I won't have to make sure the partitions on the destination drive
> are the correct size before restoring. I also only have to do the
> restoration process once (image to drive) instead of for each partition.
> But perhaps you or Steven know something I don't. I'm going to try testing
> those 3 steps above to see what happens.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonezilla-live
>
>

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Gary, that's an interesting method. I'm almost done reading Steven's
document, but while waiting to hear from him, I want to try your
method too. To be clear, when you say "make your largest partition
small enough so that the whole drive will fit on the destination",
"whole drive" does not include the unallocated space at the end of all
the partitions, right? If I understood you correctly, your method
involves:

1. Shrink partitions, and move all unallocated space to the end of the
drive if necessary
2. Use Clonezilla to save the whole disk to an image. I assume
Clonezilla only sees partitions as part of the total disk size and NOT
the unallocated space?
3. Restore the image to a smaller hard drive whose size is bigger than
the total size of all the resized partitions on source drive.

Is this right? If this works, it's even easier than Steven's method
because I won't have to make sure the partitions on the destination
drive are the correct size before restoring. I also only have to do
the restoration process once (image to drive) instead of for each
partition. But perhaps you or Steven know something I don't. I'm going
to try testing those 3 steps above to see what happens.

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[Gary S. <gar...@gm...>]

I don't have the resources to confirm, but what you need to do is:

1) on source drive, make your largest partition small enough so that the
_whole drive_ will fit on the destination.

2) use clonezilla in expert mode to image the whole disk _not_ partitions,
and enable 'Skip checking destination disk size before creating partition
table'

by your description, I think you sized down correctly, you were just in the
mindset to do partitions only.

You need to image the whole disk to get the mbr and make the whole thing
work.
On Mar 20, 2012 8:26 PM, <jum...@hu...> wrote:

> Steven, I read the posts in the first link first. It seems that bri70123
> only had one partition on his hard drive. Even then, I see a potential
> problem for him, and I don't see how he overcame it. Let's take the
> situation he gave us: 20 GB of used space on a 500 GB hard drive. Now he
> wants to copy the contents of the 500 GB hard drive to the 250 GB hard
> drive, so he shrinks the one partition he has to less than 250 GB, and then
> he makes an image that he wants to copy to the 250 GB hard drive, using
> -icds.
>
> It sounds straightforward enough, but I have some questions. First, would
> he use the option to save partitions or to save hard drive? Is Clonezilla
> able to tell the difference between a partition and a hard drive? In my
> situation, I used the option to save partitions, then tried to restore
> those partitions to a hard drive whose total size was far larger than those
> partitions combined, but it failed, saying I couldn't restore partitions to
> a hard drive or soemthing like that. But I had no choice.
>
> My situation is that I have 2 partitions from Windows 7. Since I have 2
> partitions, I shrank the larger one to minimize the total size of the 2
> partitions. Now, if I try to use Clonezilla to save partitions, I can only
> restore those partitions to other partitions (and not to the hard drive as
> a whole). I tried to first restore the saved partitions to my entire hard
> drive. I hoped that doing this would erase the whole hard drive, create 2
> partitions, and then allow me to expand the second partition to take up all
> the unallocated space, but it didn't work. I got that error telling me I
> couldn't restore to a hard drive when I saved partitions instead of the
> entire hard drive (of course I couldn't save the entire hard drive, because
> the image would reveal that the destination was smaller, which Clonezilla
> doesn't allow!).
>
> So I tried something else. I did a clean install of Windows 7 to create
> the partitions instead of going to the trouble of finding out their exact
> size (all I know is that one is about 100 MB and the other takes up the
> rest of the space if you install Windows on a blank hard drive). Then I
> used restore partitions to overwrite the newly created partitions, which,
> presumably, would be the correct size. I decided that if I could
> successfully start Windows after this, I would simply use Gparted to resize
> the larger partition to take up the rest of the unallocated space. But
> again, I failed. This time, Windows refused to start. When I tried Gparted
> anyways, it found an error on the larger partition and couldn't do anything
> with it. So I hit dead ends whether I tried to restore to partitions or to
> the entire hard drive.
>
> Perhaps the document you provided to in the second link might help with my
> situation? My situation is complicated because of 2 factors:
>
> 1. I need to clone to a smaller hard drive.
> 2. I have more than one partition
>
> Any suggestions to point me in the right direction while I read your PDF
> document?
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonezilla-live
>
>

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Steven, I read the posts in the first link first. It seems that
bri70123 only had one partition on his hard drive. Even then, I see a
potential problem for him, and I don't see how he overcame it. Let's
take the situation he gave us: 20 GB of used space on a 500 GB hard
drive. Now he wants to copy the contents of the 500 GB hard drive to
the 250 GB hard drive, so he shrinks the one partition he has to less
than 250 GB, and then he makes an image that he wants to copy to the
250 GB hard drive, using -icds.

It sounds straightforward enough, but I have some questions. First,
would he use the option to save partitions or to save hard drive? Is
Clonezilla able to tell the difference between a partition and a hard
drive? In my situation, I used the option to save partitions, then
tried to restore those partitions to a hard drive whose total size was
far larger than those partitions combined, but it failed, saying I
couldn't restore partitions to a hard drive or soemthing like that.
But I had no choice.

My situation is that I have 2 partitions from Windows 7. Since I have
2 partitions, I shrank the larger one to minimize the total size of
the 2 partitions. Now, if I try to use Clonezilla to save partitions,
I can only restore those partitions to other partitions (and not to
the hard drive as a whole). I tried to first restore the saved
partitions to my entire hard drive. I hoped that doing this would
erase the whole hard drive, create 2 partitions, and then allow me to
expand the second partition to take up all the unallocated space, but
it didn't work. I got that error telling me I couldn't restore to a
hard drive when I saved partitions instead of the entire hard drive
(of course I couldn't save the entire hard drive, because the image
would reveal that the destination was smaller, which Clonezilla
doesn't allow!).

So I tried something else. I did a clean install of Windows 7 to
create the partitions instead of going to the trouble of finding out
their exact size (all I know is that one is about 100 MB and the other
takes up the rest of the space if you install Windows on a blank hard
drive). Then I used restore partitions to overwrite the newly created
partitions, which, presumably, would be the correct size. I decided
that if I could successfully start Windows after this, I would simply
use Gparted to resize the larger partition to take up the rest of the
unallocated space. But again, I failed. This time, Windows refused to
start. When I tried Gparted anyways, it found an error on the larger
partition and couldn't do anything with it. So I hit dead ends whether
I tried to restore to partitions or to the entire hard drive.

Perhaps the document you provided to in the second link might help
with my situation? My situation is complicated because of 2 factors:

1. I need to clone to a smaller hard drive.
2. I have more than one partition

Any suggestions to point me in the right direction while I read your
PDF document?

Re: [Clonezilla-live] Cloning a larger hard drive to a smaller hard drive

[Steven S. <st...@nc...>]

It's possible you can manually make that, as the description in the 
post, or here:
https://sourceforge.net/projects/clonezilla/files/clonezilla_live_doc/CloningToSmallerDrive_0.1/

Ref:
https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/5125793

Steven.

On 2012/3/20 上午 11:00, jum...@hu... wrote:
> Does anyone know if it's possible to save the contents of a larger hard
> drive to an image, then copy the image to a smaller hard drive? I read
> that this was not currently possible because of a limitation in the way
> Clonezilla works.
>
> But then I found this:
> http://geekyprojects.com/storage/how-to-clone-hard-drive-to-smaller-drive/
>
> The way that article describes the process makes it seem easily enough:
> just use Gparted to resize the hard drive partition, then copy only that
> partition (instead of the entire hard drive).
>
> But what if you have more than one partition? Is it still possible to
> make the process work using Gparted?
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
>
>
>
> _______________________________________________
> 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] Cloning a larger hard drive to a smaller hard drive

[<jum...@hu...>]

Does anyone know if it's possible to save the contents of a larger
hard drive to an image, then copy the image to a smaller hard drive? I
read that this was not currently possible because of a limitation in
the way Clonezilla works.

But then I found this:
http://geekyprojects.com/storage/how-to-clone-hard-drive-to-smaller-drive/

The way that article describes the process makes it seem easily
enough: just use Gparted to resize the hard drive partition, then copy
only that partition (instead of the entire hard drive).

But what if you have more than one partition? Is it still possible to
make the process work using Gparted?

Re: [Clonezilla-live] Is it safe to interrupt a Clonezilla Live imaging process?

[<jum...@hu...>]

Thanks Steven!

Re: [Clonezilla-live] Is it safe to interrupt a Clonezilla Live imaging process?

[Steven S. <st...@nc...>]

On 03/14/2012 03:05 AM, jum...@hu... wrote:
> Thanks! I found that my mistake was to use partclone instead of 
> ntfsclone, because in an older version of Clonezilla, ntfsclone was 
> the default option, so I assumed it still was the default option, but 
> the newest version changed things a bit.
We have switched to partclone for a long time. :)
>
> About what you said: Clonezilla gives dire warnings about how a USB 
> hard drive might not be usable if the computer is improperly shut down 
> during the Clonezilla process. Could this really happen? I would never 
> improperly shut it down myself intentionally, but if the power fails 
> during the process, it's out of my control.
Yes. If the USB drive is removed when a file system is written, or 
without unmounting properly, the file system might be broken.
>
> If something like that happened, would the USB drive become a 
> permanent doorstopper, or is there still a way to make it usable 
> again? Will I lose any other data that's already stored on the USB drive?
Normally it's only file system broken, i.e. software issue. Not hardware 
issue.

Steven.
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
> _______________________________________________
> 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

Re: [Clonezilla-live] Is it safe to interrupt a Clonezilla Live imaging process?

[<jum...@hu...>]

Thanks! I found that my mistake was to use partclone instead of
ntfsclone, because in an older version of Clonezilla, ntfsclone was
the default option, so I assumed it still was the default option, but
the newest version changed things a bit.

About what you said: Clonezilla gives dire warnings about how a USB
hard drive might not be usable if the computer is improperly shut down
during the Clonezilla process. Could this really happen? I would never
improperly shut it down myself intentionally, but if the power fails
during the process, it's out of my control.

If something like that happened, would the USB drive become a
permanent doorstopper, or is there still a way to make it usable
again? Will I lose any other data that's already stored on the USB
drive?

Re: [Clonezilla-live] Is it safe to interrupt a Clonezilla Live imaging process?

[Steven S. <st...@nc...>]

If you are saving an image, it's should be safe. Since all the process 
will only be read-only.
So just press "Ctrl-C" to stop the process.
However, still you have to shutdown machine normally. Do not power if 
off by pressing the power button before you issue the "poweroff" command.

Steven.

On 2012/3/9 上午 09:37, jum...@hu... wrote:
> I am inexperienced with Clonezilla Live, and I chose the wrong imaging
> program priority (I think I chose partclone > partimage > dd) for my
> computer. Either as a result of this or something else, the process of
> creating an image from my hard drive is extremely slow and will take
> most of the day.
>
> Is it safe to stop the process of creating the image, or will it corrupt
> the hard drive I'm trying to back up? If it is safe to stop the process,
> is there a key I should press or should I just use my computer's power
> button?
>
> Thanks
>
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
>
> _______________________________________________
> 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

Re: [Clonezilla-live] XSRF Attempt Detected

[Steven S. <st...@nc...>]

Similar bugs report here:
https://sourceforge.net/apps/trac/sourceforge/ticket/17314

Please open a ticket on sf.net trac system if it's always reproducible.
Thanks.

Steven.

On 2012/3/9 上午 10:26, jum...@hu... wrote:
> Is anyone getting the error "XSRF Attempt Detected" whenever you try to
> sign into Clonezilla forum? I can sign into Sourceforge just fine from
> Sourceforge's main page, but when I try to sign in from the link on
> Clonezilla's site (http://clonezilla.org/forum.php), I get "XSRF Attempt
> Detected" as soon as I enter my login details. Because of this I cannot
> post on the forum. Please let me know if anybody has similar experiences.
>
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
>
> _______________________________________________
> 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] XSRF Attempt Detected

[<jum...@hu...>]

Is anyone getting the error "XSRF Attempt Detected" whenever you try
to sign into Clonezilla forum? I can sign into Sourceforge just fine
from Sourceforge's main page, but when I try to sign in from the link
on Clonezilla's site (http://clonezilla.org/forum.php), I get "XSRF
Attempt Detected" as soon as I enter my login details. Because of this
I cannot post on the forum. Please let me know if anybody has similar
experiences.

[Clonezilla-live] Is it safe to interrupt a Clonezilla Live imaging process?

[<jum...@hu...>]

I am inexperienced with Clonezilla Live, and I chose the wrong imaging
program priority (I think I chose partclone > partimage > dd) for my
computer. Either as a result of this or something else, the process of
creating an image from my hard drive is extremely slow and will take
most of the day.

Is it safe to stop the process of creating the image, or will it
corrupt the hard drive I'm trying to back up? If it is safe to stop
the process, is there a key I should press or should I just use my
computer's power button?

Thanks

Re: [Clonezilla-live] NVIDIA M2090 gpu and nouveau messages

[Steven S. <st...@nc...>]

Yes, this should be Linux kernel related issue.
Linux kernel 3.2.2 will be available in Debian Sid these days, and we 
will create another Clonezilla live with this updated kernel. It might 
solve this issue.
Please be patient for the next testing release.

Steven.

On 2012/2/1 上午 04:32, Paul Van Allsburg wrote:
> Hi!
> I have a pair of C1103 servers with two NVIDIA M2090 compute GPUs in each.
> (http://www.sgi.com/products/servers/standard_depth/1u_intel_2p.html    C1103-TY12 )
> I ran into an Oops message using clonezilla-live-1.2.8-23-amd64 so I upgraded to clonezilla-live-1.2.12-10-amd64 today.  I can
> now pxe backup&  restore just fine.   I've used 1.2.8-23-amd64 for several months on older hardware without any problems and it
> wasn't until I installed the M2090 cards that the Oops happened.  Anyway, the reason I write is that I get repeating messages on
> the console like this:
>
> [   73.575316] [drm] nouveau 0000:02:00.0: unknown i2c port 48
> [   74.309436] [drm] nouveau 0000:03:00.0: unknown i2c port 48
> [   83.565604] [drm] nouveau 0000:02:00.0: unknown i2c port 48
> [   84.299664] [drm] nouveau 0000:03:00.0: unknown i2c port 48
>
> I'm making the assumption that the Nouveau driver doesn't quite recognize the M2090 cards and is just grumpy and complaining.
> Since it is working, I'll just report this behavior as something to be aware of.
>
> Here is the initial messages from dmsg
>
>
> [   21.973986] [drm] Initialized drm 1.1.0 20060810
> [   22.044913] nouveau 0000:02:00.0: PCI INT A ->  GSI 24 (level, low) ->  IRQ 24
> [   22.066332] nouveau 0000:02:00.0: setting latency timer to 64
> [   22.067402] [drm] nouveau 0000:02:00.0: Detected an NVc0 generation card (0x0c8880a1)
> [   22.088768] checking generic (f5000000 1000000) vs hw (c8000000 8000000)
> [   22.088770] checking generic (f5000000 1000000) vs hw (c6000000 2000000)
> [   22.091689] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PRAMIN
> [   22.122455] [drm] nouveau 0000:02:00.0: ... BIOS signature not found
> [   22.143366] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PROM
> [   22.451914] [drm] nouveau 0000:02:00.0: ... appears to be valid
> [   22.471826] [drm] nouveau 0000:02:00.0: BIT BIOS found
> [   22.491131] [drm] nouveau 0000:02:00.0: Bios version 70.10.46.00
> [   22.510088] [drm] nouveau 0000:02:00.0: TMDS table version 2.0
> [   22.528614] [drm] nouveau 0000:02:00.0: Found Display Configuration Block version 4.0
> [   22.530805] eth1: no IPv6 routers present
> [   22.547317] [drm] nouveau 0000:02:00.0: Raw DCB entry 0: 02000300 00000000
> [   22.565930] [drm] nouveau 0000:02:00.0: Raw DCB entry 1: 0000000e 00020030
> [   22.584072] [drm] nouveau 0000:02:00.0: DCB connector table: VHER 0x40 5 16 4
> [   22.601893] [drm] nouveau 0000:02:00.0:   0: 0x00000000: type 0x00 idx 0 tag 0xff
> [   22.619752] [drm] nouveau 0000:02:00.0: Adaptor not initialised, running VBIOS init tables.
> [   22.638167] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 0 at offset 0x723E
> [   22.676465] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.694278] [drm] nouveau 0000:02:00.0: 0x71B9: Failed parsing init table opcode: INIT_I2C_IF -19
> [   22.712466] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.730703] [drm] nouveau 0000:02:00.0: 0x720D: i2c bus not found
> [   22.749174] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.767752] [drm] nouveau 0000:02:00.0: 0x721D: i2c bus not found
> [   22.786544] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.805441] [drm] nouveau 0000:02:00.0: 0x7224: i2c bus not found
> [   22.824102] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.842244] [drm] nouveau 0000:02:00.0: 0x722B: i2c bus not found
> [   22.860111] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.877495] [drm] nouveau 0000:02:00.0: 0x7232: i2c bus not found
> [   22.934534] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 1 at offset 0x7900
> [   22.975694] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   22.991703] [drm] nouveau 0000:02:00.0: 0x8BBD: Failed parsing init table opcode: INIT_I2C_LONG_IF -19
> [   23.023138] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 2 at offset 0x8DF6
> [   23.039274] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 3 at offset 0x8E00
> [   23.055078] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 4 at offset 0x9074
> [   23.070283] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table at offset 0x90D9
> [   23.104977] [drm] nouveau 0000:02:00.0: unknown i2c port 51
> [   23.119370] [drm] nouveau 0000:02:00.0: 1 available performance level(s)
> [   23.133526] [drm] nouveau 0000:02:00.0: 0: core 50MHz shader 101MHz memory 135MHz timing 6
> [   23.147986] [drm] nouveau 0000:02:00.0: c: core 50MHz shader 101MHz memory 135MHz voltage 890mV
> [   23.167199] [TTM] Zone  kernel: Available graphics memory: 12368584 kiB.
> [   23.181507] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
> [   23.195625] [TTM] Initializing pool allocator.
> [   23.209860] [drm] nouveau 0000:02:00.0: Detected 5376MiB VRAM
> [   23.224394] mtrr: type mismatch for c8000000,8000000 old: write-back new: write-combining
> [   23.239627] [drm] nouveau 0000:02:00.0: 512 MiB GART (aperture)
> [   23.446645] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [   23.462140] [drm] No driver support for vblank timestamp query.
> [   23.477982] [drm] nouveau 0000:02:00.0: unknown i2c port 48
> [   23.538082] No connectors reported connected with modes
> [   23.553919] [drm] Cannot find any crtc or sizes - going 1024x768
> [   23.570785] [drm] nouveau 0000:02:00.0: allocated 1024x768 fb: 0x1e0000, bo ffff880631506000
> [   23.587208] checking generic (f5000000 1000000) vs hw (c8000000 8000000)
> [   23.587209] checking generic (f5000000 1000000) vs hw (c6000000 2000000)
> [   23.587332] fb1: nouveaufb frame buffer device
> [   23.603662] drm: registered panic notifier
> [   23.619805] [drm] Initialized nouveau 0.0.16 20090420 for 0000:02:00.0 on minor 0
> [   23.619825] nouveau 0000:03:00.0: PCI INT A ->  GSI 30 (level, low) ->  IRQ 30
> [   23.619829] nouveau 0000:03:00.0: setting latency timer to 64
> [   23.620968] [drm] nouveau 0000:03:00.0: Detected an NVc0 generation card (0x0c8880a1)
> [   23.620973] checking generic (f5000000 1000000) vs hw (d8000000 8000000)
> [   23.620975] checking generic (f5000000 1000000) vs hw (d6000000 2000000)
> [   23.624057] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PRAMIN
> [   23.633751] [drm] nouveau 0000:03:00.0: ... BIOS signature not found
> [   23.633753] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PROM
> [   23.920160] [drm] nouveau 0000:03:00.0: ... appears to be valid
> [   23.938086] [drm] nouveau 0000:03:00.0: BIT BIOS found
> [   23.955932] [drm] nouveau 0000:03:00.0: Bios version 70.10.46.00
> [   23.973904] [drm] nouveau 0000:03:00.0: TMDS table version 2.0
> [   23.991884] [drm] nouveau 0000:03:00.0: Found Display Configuration Block version 4.0
> [   24.010139] [drm] nouveau 0000:03:00.0: Raw DCB entry 0: 02000300 00000000
> [   24.010141] [drm] nouveau 0000:03:00.0: Raw DCB entry 1: 0000000e 00020030
> [   24.010143] [drm] nouveau 0000:03:00.0: DCB connector table: VHER 0x40 5 16 4
> [   24.010145] [drm] nouveau 0000:03:00.0:   0: 0x00000000: type 0x00 idx 0 tag 0xff
> [   24.010159] [drm] nouveau 0000:03:00.0: Adaptor not initialised, running VBIOS init tables.
> [   24.010161] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 0 at offset 0x723E
> [   24.030207] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030209] [drm] nouveau 0000:03:00.0: 0x71B9: Failed parsing init table opcode: INIT_I2C_IF -19
> [   24.030211] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030212] [drm] nouveau 0000:03:00.0: 0x720D: i2c bus not found
> [   24.030213] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030215] [drm] nouveau 0000:03:00.0: 0x721D: i2c bus not found
> [   24.030216] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030217] [drm] nouveau 0000:03:00.0: 0x7224: i2c bus not found
> [   24.030219] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030220] [drm] nouveau 0000:03:00.0: 0x722B: i2c bus not found
> [   24.030221] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.030222] [drm] nouveau 0000:03:00.0: 0x7232: i2c bus not found
> [   24.070364] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 1 at offset 0x7900
> [   24.094867] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.094869] [drm] nouveau 0000:03:00.0: 0x8BBD: Failed parsing init table opcode: INIT_I2C_LONG_IF -19
> [   24.094871] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 2 at offset 0x8DF6
> [   24.094877] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 3 at offset 0x8E00
> [   24.095003] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 4 at offset 0x9074
> [   24.095007] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table at offset 0x90D9
> [   24.114869] [drm] nouveau 0000:03:00.0: unknown i2c port 51
> [   24.114870] [drm] nouveau 0000:03:00.0: 1 available performance level(s)
> [   24.114873] [drm] nouveau 0000:03:00.0: 0: core 50MHz shader 101MHz memory 135MHz timing 6
> [   24.114957] [drm] nouveau 0000:03:00.0: c: core 50MHz shader 101MHz memory 135MHz voltage 890mV
> [   24.119858] [drm] nouveau 0000:03:00.0: Detected 5376MiB VRAM
> [   24.119862] mtrr: type mismatch for d8000000,8000000 old: write-back new: write-combining
> [   24.119874] [drm] nouveau 0000:03:00.0: 512 MiB GART (aperture)
> [   24.310393] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [   24.310395] [drm] No driver support for vblank timestamp query.
> [   24.310400] [drm] nouveau 0000:03:00.0: unknown i2c port 48
> [   24.354939] No connectors reported connected with modes
> [   24.354941] [drm] Cannot find any crtc or sizes - going 1024x768
> [   24.355850] [drm] nouveau 0000:03:00.0: allocated 1024x768 fb: 0x1e0000, bo ffff8806328ce400
> [   24.355852] checking generic (f5000000 1000000) vs hw (d8000000 8000000)
> [   24.355854] checking generic (f5000000 1000000) vs hw (d6000000 2000000)
> [   24.356044] fb2: nouveaufb frame buffer device
> [   24.356050] [drm] Initialized nouveau 0.0.16 20090420 for 0000:03:00.0 on minor 1
> [   25.041780] mdadm: sending ioctl 800c0910 to a partition!
> [   25.057908] mdadm: sending ioctl 800c0910 to a partition!
> [   25.057915] mdadm: sending ioctl 1261 to a partition!
> [   25.057916] mdadm: sending ioctl 1261 to a partition!
> [   25.058246] mdadm: sending ioctl 1261 to a partition!
> [   25.058249] mdadm: sending ioctl 1261 to a partition!
> [   25.058465] mdadm: sending ioctl 1261 to a partition!
> [   25.058468] mdadm: sending ioctl 1261 to a partition!
> [   25.058667] mdadm: sending ioctl 1261 to a partition!
> [   25.058670] mdadm: sending ioctl 1261 to a partition!
> [   26.009909] fuse init (API version 7.17)
> [   26.109278] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
> [   26.156161] SGI XFS Quota Management subsystem
> [   26.197337] JFS: nTxBlock = 8192, nTxLock = 65536
> [   27.153671] RPC: Registered named UNIX socket transport module.
> [   27.187493] RPC: Registered udp transport module.
> [   27.204355] RPC: Registered tcp transport module.
> [   27.220451] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [   27.311447] FS-Cache: Loaded
> [   27.364775] FS-Cache: Netfs 'nfs' registered for caching
> [   27.395278] Installing knfsd (copyright (C) 1996 ok...@mo...).
> [   33.614269] [drm] nouveau 0000:02:00.0: unknown i2c port 48
> [   34.348382] [drm] nouveau 0000:03:00.0: unknown i2c port 48
> [   43.604536] [drm] nouveau 0000:02:00.0: unknown i2c port 48
> [   44.338589] [drm] nouveau 0000:03:00.0: unknown i2c port 48
> [   53.594800] [drm] nouveau 0000:02:00.0: unknown i2c port 48
>
>
> Here is my default boot menu options and the scripts behind it...
>
>   From /tftpboot/pxelinux.cfg/default :
> LABEL backup
> MENU LABEL backup
>     kernel clonenbi
>     append initrd=nbi_img/initrd.img boot=live live-config noswap nolocales noprompt edd=on ocs_prerun="mount -t nfs
> 192.168.12.102:/home /mnt" ocs_prerun1="mount --bind /mnt/partimag /home/partimag" ocs_live_run="bash
> /home/partimag/clonebucompute11.bash" ocs_live_batch="yes" ocs_live_extra_param="" ocs_live_keymap="NONE" ocs_lang="en_US.UTF-8"
> ocs_daemonon="ssh" vga=788 nosplash fetch=tftp://192.168.11.102/nbi_img/filesystem.squashfs
>
> LABEL restore
> MENU LABEL restore
>    kernel clonenbi
>    append initrd=nbi_img/initrd.img boot=live live-config noswap nolocales noprompt textonly edd=on ocs_prerun1="sleep 4"
> ocs_prerun2="mount -t nfs 192.168.12.102:/home /mnt" ocs_prerun3="mount --bind /mnt/partimag /home/partimag" ocs_live_run="bash
> /home/partimag/clonerstcompute11.bash" ocs_live_batch="yes" ocs_live_extra_param="" ocs_live_keymap="NONE"
> ocs_lang="en_US.UTF-8" ocs_daemonon="ssh" vga=788 nosplash fetch=tftp://192.168.11.102/nbi_img/filesystem.squashfs
>
>
> # cat /home/partimag/clonebucompute11.bash
> #!/bin/bash
> #MENU LABEL Clonezilla Live
> script -c /home/partimag/clonebackupcompute11.bash  /home/partimag/`hostname -I | cut -d" " -f1`.txt
> exit
>
> # cat /home/partimag/clonebackupcompute11.bash
> #!/bin/bash
> #MENU LABEL Clonezilla Live Backup Compute Node
> . /opt/drbl/sbin/drbl-conf-functions
> . /opt/drbl/sbin/ocs-functions
> . /etc/ocs/ocs-live.conf
> if mountpoint /home/partimag/&>/dev/null; then
>     /opt/drbl/sbin/ocs-sr -q2 -b -j2  -z1p -i 2000 -p /home/partimag/rm_pxe_link11 savedisk compute-node sda
> else
>     [ "$BOOTUP" = "color" ]&&  $SETCOLOR_FAILURE
>     echo "Fail to find the Clonezilla image home /home/partimag!"
>     echo "Program terminated!"
>     [ "$BOOTUP" = "color" ]&&  $SETCOLOR_NORMAL
> fi
> exit
>
> # cat /home/partimag/rm_pxe_link11
> #!/bin/sh
> mkdir /media/pxe
> mount -t nfs 192.168.12.102:/tftpboot /media/pxe
> rm -f "/media/pxe/pxelinux.cfg/`/home/partimag/iphex eth0`"
> cd /
> umount /media/pxe
> umount /home/partimag
> umount /mnt
> init 6
>
>
> Many thanks for the great software!
> Cheers,
> Paul
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> 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] NVIDIA M2090 gpu and nouveau messages

[Paul V. A. <van...@ho...>]

Hi!
I have a pair of C1103 servers with two NVIDIA M2090 compute GPUs in each.
(http://www.sgi.com/products/servers/standard_depth/1u_intel_2p.html    C1103-TY12 )
I ran into an Oops message using clonezilla-live-1.2.8-23-amd64 so I upgraded to clonezilla-live-1.2.12-10-amd64 today.  I can 
now pxe backup & restore just fine.   I've used 1.2.8-23-amd64 for several months on older hardware without any problems and it 
wasn't until I installed the M2090 cards that the Oops happened.  Anyway, the reason I write is that I get repeating messages on 
the console like this:

[   73.575316] [drm] nouveau 0000:02:00.0: unknown i2c port 48
[   74.309436] [drm] nouveau 0000:03:00.0: unknown i2c port 48
[   83.565604] [drm] nouveau 0000:02:00.0: unknown i2c port 48
[   84.299664] [drm] nouveau 0000:03:00.0: unknown i2c port 48

I'm making the assumption that the Nouveau driver doesn't quite recognize the M2090 cards and is just grumpy and complaining.  
Since it is working, I'll just report this behavior as something to be aware of.

Here is the initial messages from dmsg


[   21.973986] [drm] Initialized drm 1.1.0 20060810
[   22.044913] nouveau 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
[   22.066332] nouveau 0000:02:00.0: setting latency timer to 64
[   22.067402] [drm] nouveau 0000:02:00.0: Detected an NVc0 generation card (0x0c8880a1)
[   22.088768] checking generic (f5000000 1000000) vs hw (c8000000 8000000)
[   22.088770] checking generic (f5000000 1000000) vs hw (c6000000 2000000)
[   22.091689] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PRAMIN
[   22.122455] [drm] nouveau 0000:02:00.0: ... BIOS signature not found
[   22.143366] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PROM
[   22.451914] [drm] nouveau 0000:02:00.0: ... appears to be valid
[   22.471826] [drm] nouveau 0000:02:00.0: BIT BIOS found
[   22.491131] [drm] nouveau 0000:02:00.0: Bios version 70.10.46.00
[   22.510088] [drm] nouveau 0000:02:00.0: TMDS table version 2.0
[   22.528614] [drm] nouveau 0000:02:00.0: Found Display Configuration Block version 4.0
[   22.530805] eth1: no IPv6 routers present
[   22.547317] [drm] nouveau 0000:02:00.0: Raw DCB entry 0: 02000300 00000000
[   22.565930] [drm] nouveau 0000:02:00.0: Raw DCB entry 1: 0000000e 00020030
[   22.584072] [drm] nouveau 0000:02:00.0: DCB connector table: VHER 0x40 5 16 4
[   22.601893] [drm] nouveau 0000:02:00.0:   0: 0x00000000: type 0x00 idx 0 tag 0xff
[   22.619752] [drm] nouveau 0000:02:00.0: Adaptor not initialised, running VBIOS init tables.
[   22.638167] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 0 at offset 0x723E
[   22.676465] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.694278] [drm] nouveau 0000:02:00.0: 0x71B9: Failed parsing init table opcode: INIT_I2C_IF -19
[   22.712466] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.730703] [drm] nouveau 0000:02:00.0: 0x720D: i2c bus not found
[   22.749174] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.767752] [drm] nouveau 0000:02:00.0: 0x721D: i2c bus not found
[   22.786544] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.805441] [drm] nouveau 0000:02:00.0: 0x7224: i2c bus not found
[   22.824102] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.842244] [drm] nouveau 0000:02:00.0: 0x722B: i2c bus not found
[   22.860111] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.877495] [drm] nouveau 0000:02:00.0: 0x7232: i2c bus not found
[   22.934534] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 1 at offset 0x7900
[   22.975694] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   22.991703] [drm] nouveau 0000:02:00.0: 0x8BBD: Failed parsing init table opcode: INIT_I2C_LONG_IF -19
[   23.023138] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 2 at offset 0x8DF6
[   23.039274] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 3 at offset 0x8E00
[   23.055078] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 4 at offset 0x9074
[   23.070283] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table at offset 0x90D9
[   23.104977] [drm] nouveau 0000:02:00.0: unknown i2c port 51
[   23.119370] [drm] nouveau 0000:02:00.0: 1 available performance level(s)
[   23.133526] [drm] nouveau 0000:02:00.0: 0: core 50MHz shader 101MHz memory 135MHz timing 6
[   23.147986] [drm] nouveau 0000:02:00.0: c: core 50MHz shader 101MHz memory 135MHz voltage 890mV
[   23.167199] [TTM] Zone  kernel: Available graphics memory: 12368584 kiB.
[   23.181507] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
[   23.195625] [TTM] Initializing pool allocator.
[   23.209860] [drm] nouveau 0000:02:00.0: Detected 5376MiB VRAM
[   23.224394] mtrr: type mismatch for c8000000,8000000 old: write-back new: write-combining
[   23.239627] [drm] nouveau 0000:02:00.0: 512 MiB GART (aperture)
[   23.446645] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   23.462140] [drm] No driver support for vblank timestamp query.
[   23.477982] [drm] nouveau 0000:02:00.0: unknown i2c port 48
[   23.538082] No connectors reported connected with modes
[   23.553919] [drm] Cannot find any crtc or sizes - going 1024x768
[   23.570785] [drm] nouveau 0000:02:00.0: allocated 1024x768 fb: 0x1e0000, bo ffff880631506000
[   23.587208] checking generic (f5000000 1000000) vs hw (c8000000 8000000)
[   23.587209] checking generic (f5000000 1000000) vs hw (c6000000 2000000)
[   23.587332] fb1: nouveaufb frame buffer device
[   23.603662] drm: registered panic notifier
[   23.619805] [drm] Initialized nouveau 0.0.16 20090420 for 0000:02:00.0 on minor 0
[   23.619825] nouveau 0000:03:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
[   23.619829] nouveau 0000:03:00.0: setting latency timer to 64
[   23.620968] [drm] nouveau 0000:03:00.0: Detected an NVc0 generation card (0x0c8880a1)
[   23.620973] checking generic (f5000000 1000000) vs hw (d8000000 8000000)
[   23.620975] checking generic (f5000000 1000000) vs hw (d6000000 2000000)
[   23.624057] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PRAMIN
[   23.633751] [drm] nouveau 0000:03:00.0: ... BIOS signature not found
[   23.633753] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PROM
[   23.920160] [drm] nouveau 0000:03:00.0: ... appears to be valid
[   23.938086] [drm] nouveau 0000:03:00.0: BIT BIOS found
[   23.955932] [drm] nouveau 0000:03:00.0: Bios version 70.10.46.00
[   23.973904] [drm] nouveau 0000:03:00.0: TMDS table version 2.0
[   23.991884] [drm] nouveau 0000:03:00.0: Found Display Configuration Block version 4.0
[   24.010139] [drm] nouveau 0000:03:00.0: Raw DCB entry 0: 02000300 00000000
[   24.010141] [drm] nouveau 0000:03:00.0: Raw DCB entry 1: 0000000e 00020030
[   24.010143] [drm] nouveau 0000:03:00.0: DCB connector table: VHER 0x40 5 16 4
[   24.010145] [drm] nouveau 0000:03:00.0:   0: 0x00000000: type 0x00 idx 0 tag 0xff
[   24.010159] [drm] nouveau 0000:03:00.0: Adaptor not initialised, running VBIOS init tables.
[   24.010161] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 0 at offset 0x723E
[   24.030207] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030209] [drm] nouveau 0000:03:00.0: 0x71B9: Failed parsing init table opcode: INIT_I2C_IF -19
[   24.030211] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030212] [drm] nouveau 0000:03:00.0: 0x720D: i2c bus not found
[   24.030213] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030215] [drm] nouveau 0000:03:00.0: 0x721D: i2c bus not found
[   24.030216] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030217] [drm] nouveau 0000:03:00.0: 0x7224: i2c bus not found
[   24.030219] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030220] [drm] nouveau 0000:03:00.0: 0x722B: i2c bus not found
[   24.030221] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.030222] [drm] nouveau 0000:03:00.0: 0x7232: i2c bus not found
[   24.070364] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 1 at offset 0x7900
[   24.094867] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.094869] [drm] nouveau 0000:03:00.0: 0x8BBD: Failed parsing init table opcode: INIT_I2C_LONG_IF -19
[   24.094871] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 2 at offset 0x8DF6
[   24.094877] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 3 at offset 0x8E00
[   24.095003] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 4 at offset 0x9074
[   24.095007] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table at offset 0x90D9
[   24.114869] [drm] nouveau 0000:03:00.0: unknown i2c port 51
[   24.114870] [drm] nouveau 0000:03:00.0: 1 available performance level(s)
[   24.114873] [drm] nouveau 0000:03:00.0: 0: core 50MHz shader 101MHz memory 135MHz timing 6
[   24.114957] [drm] nouveau 0000:03:00.0: c: core 50MHz shader 101MHz memory 135MHz voltage 890mV
[   24.119858] [drm] nouveau 0000:03:00.0: Detected 5376MiB VRAM
[   24.119862] mtrr: type mismatch for d8000000,8000000 old: write-back new: write-combining
[   24.119874] [drm] nouveau 0000:03:00.0: 512 MiB GART (aperture)
[   24.310393] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   24.310395] [drm] No driver support for vblank timestamp query.
[   24.310400] [drm] nouveau 0000:03:00.0: unknown i2c port 48
[   24.354939] No connectors reported connected with modes
[   24.354941] [drm] Cannot find any crtc or sizes - going 1024x768
[   24.355850] [drm] nouveau 0000:03:00.0: allocated 1024x768 fb: 0x1e0000, bo ffff8806328ce400
[   24.355852] checking generic (f5000000 1000000) vs hw (d8000000 8000000)
[   24.355854] checking generic (f5000000 1000000) vs hw (d6000000 2000000)
[   24.356044] fb2: nouveaufb frame buffer device
[   24.356050] [drm] Initialized nouveau 0.0.16 20090420 for 0000:03:00.0 on minor 1
[   25.041780] mdadm: sending ioctl 800c0910 to a partition!
[   25.057908] mdadm: sending ioctl 800c0910 to a partition!
[   25.057915] mdadm: sending ioctl 1261 to a partition!
[   25.057916] mdadm: sending ioctl 1261 to a partition!
[   25.058246] mdadm: sending ioctl 1261 to a partition!
[   25.058249] mdadm: sending ioctl 1261 to a partition!
[   25.058465] mdadm: sending ioctl 1261 to a partition!
[   25.058468] mdadm: sending ioctl 1261 to a partition!
[   25.058667] mdadm: sending ioctl 1261 to a partition!
[   25.058670] mdadm: sending ioctl 1261 to a partition!
[   26.009909] fuse init (API version 7.17)
[   26.109278] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[   26.156161] SGI XFS Quota Management subsystem
[   26.197337] JFS: nTxBlock = 8192, nTxLock = 65536
[   27.153671] RPC: Registered named UNIX socket transport module.
[   27.187493] RPC: Registered udp transport module.
[   27.204355] RPC: Registered tcp transport module.
[   27.220451] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   27.311447] FS-Cache: Loaded
[   27.364775] FS-Cache: Netfs 'nfs' registered for caching
[   27.395278] Installing knfsd (copyright (C) 1996 ok...@mo...).
[   33.614269] [drm] nouveau 0000:02:00.0: unknown i2c port 48
[   34.348382] [drm] nouveau 0000:03:00.0: unknown i2c port 48
[   43.604536] [drm] nouveau 0000:02:00.0: unknown i2c port 48
[   44.338589] [drm] nouveau 0000:03:00.0: unknown i2c port 48
[   53.594800] [drm] nouveau 0000:02:00.0: unknown i2c port 48


Here is my default boot menu options and the scripts behind it...

 From /tftpboot/pxelinux.cfg/default :
LABEL backup
MENU LABEL backup
   kernel clonenbi
   append initrd=nbi_img/initrd.img boot=live live-config noswap nolocales noprompt edd=on ocs_prerun="mount -t nfs 
192.168.12.102:/home /mnt" ocs_prerun1="mount --bind /mnt/partimag /home/partimag" ocs_live_run="bash 
/home/partimag/clonebucompute11.bash" ocs_live_batch="yes" ocs_live_extra_param="" ocs_live_keymap="NONE" ocs_lang="en_US.UTF-8" 
ocs_daemonon="ssh" vga=788 nosplash fetch=tftp://192.168.11.102/nbi_img/filesystem.squashfs

LABEL restore
MENU LABEL restore
  kernel clonenbi
  append initrd=nbi_img/initrd.img boot=live live-config noswap nolocales noprompt textonly edd=on ocs_prerun1="sleep 4" 
ocs_prerun2="mount -t nfs 192.168.12.102:/home /mnt" ocs_prerun3="mount --bind /mnt/partimag /home/partimag" ocs_live_run="bash 
/home/partimag/clonerstcompute11.bash" ocs_live_batch="yes" ocs_live_extra_param="" ocs_live_keymap="NONE" 
ocs_lang="en_US.UTF-8" ocs_daemonon="ssh" vga=788 nosplash fetch=tftp://192.168.11.102/nbi_img/filesystem.squashfs


# cat /home/partimag/clonebucompute11.bash
#!/bin/bash
#MENU LABEL Clonezilla Live
script -c /home/partimag/clonebackupcompute11.bash  /home/partimag/`hostname -I | cut -d" " -f1`.txt
exit

# cat /home/partimag/clonebackupcompute11.bash
#!/bin/bash
#MENU LABEL Clonezilla Live Backup Compute Node
. /opt/drbl/sbin/drbl-conf-functions
. /opt/drbl/sbin/ocs-functions
. /etc/ocs/ocs-live.conf
if mountpoint /home/partimag/ &>/dev/null; then
   /opt/drbl/sbin/ocs-sr -q2 -b -j2  -z1p -i 2000 -p /home/partimag/rm_pxe_link11 savedisk compute-node sda
else
   [ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
   echo "Fail to find the Clonezilla image home /home/partimag!"
   echo "Program terminated!"
   [ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
fi
exit

# cat /home/partimag/rm_pxe_link11
#!/bin/sh
mkdir /media/pxe
mount -t nfs 192.168.12.102:/tftpboot /media/pxe
rm -f "/media/pxe/pxelinux.cfg/`/home/partimag/iphex eth0`"
cd /
umount /media/pxe
umount /home/partimag
umount /mnt
init 6


Many thanks for the great software!
Cheers,
Paul

[Clonezilla-live] Stable Clonezilla live (1.2.12-10) Released

[Steven S. <st...@nc...>]

This release of Clonezilla live (1.2.12-10) includes major enhancements
and major bug fixes.

ENHANCEMENTS and CHANGES
* The underlying GNU/Linux operating system was upgraded. This release
is based on the Debian Sid repository (as of 2012/Jan/27).
* The Linux kernel was updated to 3.2.1-2.
* Partclone was updated to version 0.2.45.
* Syslinux was updated to 4.0.5.
* A better mechanism was implemented in ocs-update-syslinux. Only when
the files to be updated are found on the system "syslinux -i" will be run.
* A better mechanism was implemented to keep the MS Windows boot
reserved partition size when option "-k1" is chosen.
* A better mechanism to deal with UFS partition in a GPT table when
saving FreeBSD 9.0.
* An option to use "autoname" to create the image name was added. Thanks
to encephalophone (Mike) for the patch.
* An option (-icds, --ignore-chk-dsk-size-pt) to skip checking skip
checking destination disk size before creating the partition table on it
was added. Thanks to Sartoratti Lorenzo for reporting this issue.
* Option -z7|--lrzip-compress was added for Clonezilla to use lrzip to
compress image.
* VMFS3 and VMFS5 support are separated, no more mixed because
partclone.fstype from 0.2.45 now can tell them. Since vmfs5 support is
still buggy, disable it in drbl-ocs.conf.
* A mechanism was added to avoid saving an image for an unmatched GPT
and MBR partition table disk.
* //NOTE// From Clonezilla live 1.2.6-24, if you manage the boot
parameters by yourself, you have to put the extra boot parameter
"config" or "live-config" to make live-config to work.
* //NOTE// From Clonezilla live 1.2.6-24, due to the change in
Live-boot, the boot parameter to assign static IP address has been
changed. The new format is:
    ip=**[DEVICE]:[CLIENT_IP]:[NETMASK]:[GATEWAY_IP]:[NAMESERVER]
[,[DEVICE]:[CLIENT_IP]:[NETMASK]:[GATEWAY_IP]:[NAMESERVER]]***::
    e.g.
ip=eth0:192.168.100.1:255.255.255.0:192.168.100.254:8.8.8.8,eth1:192.168.101.1:255.255.255.0::


BUG FIXES
* An issue about PXE booting on a machine with multiple network cards
has been fixed.
* An issue about the unknown slow execution after an image is restored
100% has been fixed.
* /live/ and /live/cow unmounting error or warning messages are
suppressed when rebooting or halting.
* Serial console did not have tty when live-getty and console boot
parameters are assigned. Thanks to Shuras for this bug report.
* A problem where failing to reinstall grub1 for the restored OS was fixed.
* A problem where grub2 failed to be restored along with Fedora 16 due
to a different grub2 boot directory, /boot/grub2/, was fixed. Thanks to
Robert Weir for reporting this issue.


Steven.
-- 
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

Re: [Clonezilla-live] FreeBSD new filesystem UFS2 with SUJ

[Steven S. <st...@nc...>]

This is really a tough one...
Firstly, Partclone has to support it
Secondly, it would be better if the Linux kernel support it, too.
Anyway, we will try in the future.
If you are familiar with UFS+SUJ and coding, please help the developer
of Partclone, Thomas Tsai, to have Partclone support UFS+SUJ.

Steven.

On 01/12/2012 02:16 AM, Barış Gerze wrote:
> When will you support natively getting image of FreeBSD 9's new
> filesystem with SUJ ( soft updates with journaling ) ?
> 
> Thanks.
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual 
> desktops for less than the cost of PCs and save 60% on VDI infrastructure 
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> 
> 
> 
> _______________________________________________
> 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