#95 Large VHD only detected as 136GB

open
nobody
5
2010-12-14
2010-12-14
No

I am trying to use clonezilla to migrate a Linux system to a Hyper-V virtual machine. I created a 600GB VHD that will store my data from the old system.

Clonezilla only sees this disk as 136.8GB and will not restore the data to that virtual drive. If I attach the VHD to the VM as a SCSI disk clonezilla cannot see the disk at all due to missing drivers for the missing hv_ modules I assume. I dont know if its a limitation of the ATA driver being used by clonezilla to access disk sdb or if its a limitation of the Hyper-V virtual disk adapter presenting sdb to clonezilla. The smaller 73GB VHD I created for the OS worked without any issues.

I tried using clonezilla-live-1.2.5-35-i686 and the latest stable version 1.2.6-40-i686.

Discussion

  • Justin Yaple

    Justin Yaple - 2010-12-14

    I also tried 20101106-maverick with the same results.

     
  • Steven Shiau

    Steven Shiau - 2010-12-15

    This is kernel-related issue. I remember the kernel from Debian Lenny works for this. Do you know any new kernel on the recent GNU/Linux distribution works for this?
    Thanks.

    Steven.

     
  • Justin Yaple

    Justin Yaple - 2010-12-23

    I just updated my gentoo kernel from 2.6.11 to 2.6.36 and am having the same problem now. Funny that the older kernel saw all 600GB without any problems but the new kernel only sees it as 136GB.

    The driver that seems to be involved to access the VHD is CMD64x PATA support in "Drivers>Serial ATA and Parallel ATA drivers" at least thats the driver I had to add to the kernel config in order to access the VHD and prevent kernel panic with VFS errors about being unable to mount the root fs on unknown block....

     
  • Steven Shiau

    Steven Shiau - 2010-12-29

    So could you please report this bug on linux kernel mailing list? I believe they can deal with this.

    Steven.

     
  • Justin Yaple

    Justin Yaple - 2010-12-29

    I have been talking with the gentoo folks and it seems to be that the IDE emulation in Hyper-V does not report the LBA48 fields correctly. So its actually broken emulation. Prior to kernel 2.6.28 the linux kernel was apparently more forgiving of drive oddities so was able to somehow figure out that the LBA fields were wrong.

    As a workaround I am trying the hv drivers in staging but those were very unstable in kernle 2.6.36 so I am backing down to 2.6.32. This has allowed me to attach the VHD as a SCSI disk rather than IDE and the SCSI interface seems to work correctly for VHDs > 137GB.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks