We are increasingly using RAID in the household and in my business, but it doesn't seem like Clonezilla recognizes RAID partitions at all :( This is really sad, especially since I can't make backups or transfer OS off a RAID C-drive to another drive.
Is there any progress being done on increasing RAID support to a more meaningful level?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for asking this again. If you software RAID, fakeRAID, not yet. There are so many items to do here…
Please keep pushing us about this. Bug us frequently… and someday we will have that :)
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These are all hardware RAID, either through a dedicated controller (Like Promise RAID Controller) or through a motherboard RAID controller. Right now 90% of our machines run in some form of RAID (typically RAID 0 or 6)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it's hardware RAID, and the device name is /dev/sd* or /dev/cciss/*, then Clonezilla can clone it.
What's the device name of your RAID on GNU/Linux?
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no idea, I don't use Linux beyond Clonezilla. All machines are Windows machines. But hardware raid would still need a driver afaik. And what about RAID which are on the motherboard SATA controller?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-03-31
I would like to echo this. I find that as the technology begins to age, many customers and people find their raid arrays were not so fool-proof. On a windows system, it's a particular pain to reinstall all the software (backing up data is easy, not a problem) with all the regkeys, software activation crap, and all that.
Cloning a raid stripe or raid 5 to a single disk (for raid mirroring) seemed like the promise clonezilla offered, but I've not seen it able to understand any raid configurations (hardware ones) yet. It would really be fantastic if clonezilla could actually clone a hardware raid as though it were a single disk, which right now it fails to do (error about cant have a partition outside the disk).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
eogamer,
Please boot Clonezilla live, enter command line prompt, run:
sudo /opt/drbl/sbin/ocs-live-bug-report
then post the generated file.
"what about RAID which are on the motherboard SATA controller? " -> Normally it's FakeRAID.
BTW, RAID is complicated:
1. Driver is required most of the cases
2. There are many RAID types, 0, 1, 5…
3. Linux software RAID is another story…
…
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-04-01
I think some people think there is only software and hardware raid. You may want to use the terminology 'firmware' raid to describe the third group, since firmware raid pretends to be hardware, and 97.3% of the public will not know the difference between firmware and hardware raid. I believe the intel raid we use here (almost every one of the many computers we use are going to be intel raid) is firmware, so clonezilla just sees a bunch of disks, not an array. I'll post the bug report though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-04-01
===
*********************************************************
The contents of /live/image/Clonezilla-Live-Version:
clonezilla-live-1.2.4-28-686
This Clonezilla live iso file was created by this command:
ocs-iso -s -i 1.2.4-28-686
*********************************************************
Installed DRBL/Clonezilla related packages: drbl-1.9.5-79 clonezilla-2.3.5-21 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.8-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.2.7-1drbl drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.6-1 pbzip2-1.1.0-1drbl udpcast-20091031-1drbl
*********************************************************
/proc/partitions:
major minor #blocks name
8 16 732574584 sdb
8 0 732574584 sda
8 1 732573560 sda1
7 0 103812 loop0
*********************************************************
Partition lists on the system:
Error: /dev/sdb: unrecognised disk label
Error: Can't have a partition outside the disk!
*********************************************************
The info from blkid:
/dev/sdb: TYPE="isw_raid_member"
/dev/sda1: TYPE="isw_raid_member"
/dev/loop0: TYPE="squashfs"
*********************************************************
Clonezilla image repository dir /home/partimag is aufs
*********************************************************
===
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, firmware RAID is the fakeRAID I mentioned. It's true the name "firmware RAID" is a better description than fakeRAID.
Could you please:
1. Boot Clonezilla live on your firmware RAID machine
2. Enter command line prompt
3. ls -alFh /dev/mapper/
Then post the results of (3)?
Thanks.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a similar situation too….I am using my motherboard intel RAID 1(mirror), I don't know why it is "fake" but it really give me "RAID results" I do have identical disks and when one of it fails to function, I still have my data and with a new disk, it rebuilds…
Anyway, I have the same situation, when Clonezilla asks me to choose the destination for saving the image file, it returns all the hardisks and partitions instead of the volume partitions……I will post a result later by doing what Steven mentioned above. Hope we can use this good free utility. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have done both commands: sudo……… and ls -alFh…….
But I don't know where is the CLONEZILLA-LIVE-BUG-REPORT…..txt located and so I cannot copy it out.
and the results of mapper….I took a photo of my screen….
in case the image cannot be shown directly:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, thanks. Yes, this is "firmware" RAID, or "fake" RAID. Since the OS (GNU/Linux) create the mapping devices for the RAID card, not the RAID card itself.
We will try to make it in the future, but it won't be in the near future, since we need to buy such a motherboard, and need some time to know how to deal with this.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Total newbie here. Just a tip for those using RAID1 or RAID10 - as alluded to above, it's _easy _to clone your drive - just pop out one of the drives (or mirrored sets) (there's your clone!), insert another drive(s) and have the RAID rebuild the unit. Viola! This is, of course, only suitable for home or small office.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Beginning with Linux* kernel version 2.6.18*, the dmraid* utility 1.0.0-rc15 supports RAID 0, RAID 1, and RAID 10.
Beginning with Linux kernel version 2.6.27*, the mdadm* utility 3.0 supports RAID 0, RAID 1, RAID 10, and RAID 5.
The kernel provides the RAID level support. The utilities support the Intel® Matrix Storage Manager metadata format.
To use the RAID features in dmraid and mdadm, you will need to set up the RAID volume using the Intel® Matrix Storage Manager option ROM (click CTRL + I when prompted during boot to enter the option ROM user interface). Instructions on how to use the RAID features in dmraid and mdadm are included in the man pages within Linux."
I hope we can have this soon. I just discovered CloneZilla and I really like it! I built a new PC and are using RAID1 mirroring.
For now, I am able to make a PartPE boot CD (XP) with the extra intel iaStor.sys driver, and use Drive Image XML and Acronis True Image to backup the partition to files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Steven. Just bumping this thread as you requested :-D Our school buys thousands of Dells that have the aforementioned Intel Matrix RAID firmware and it'd be wonderful to be able to clone them. I'll try Walter's suggestion above about removnig a disk then letting it rebuild the array after cloning but I'm not convinced that CloneZilla will recognize the disk.
I'm actually more of a FOG user, but whichever solution I can apply to RAID will be a huge advantage. How's that for a little friendly competition? ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
Bumping this thread again because i also need to backup my fakeraid disks.
Should work with dmraid, available under ubuntu and debian!
Is it possible to load this module after booting from cd from command line and then start clonezilla?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Is it possible to load this module after booting from cd from command line and then start clonezilla? " -> Not really. Clonezilla will see different disks, not the RAID device.
However, you can use partclone, which is included in Clonezilla live, to do that.
For more info, please run:
partclone.$fs -help
e.g. partclone.ext4 -help
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! I also need firmware RAID (aka fake RAID) support. There is no software (paid or free) that can backup the RAID 10 configuration we are using in the company. Acronis destroys de RAID when booting and other programs fails to boot or any have other problems.
I can give some info about dmraid devices:
They are inside /dev/mapper but the files in there are symlinks to /dev/dm-0, /dev/dm-1, /dev/dm-2 an so on, but Clonezilla wizards refuses that device names although kernel recognises and activates the raid automatically at boot time.
I think Linux uses /dev/dm-X devices as normal ones, like sda, so maybe just making Clonezilla interface and scripts allow that device names should be enough, or is there any problems when reading and writing from /dev/dm-X instead of sda, sdb and others?
If you think that there is no more changes needed, I could try to modify it.
Thanks in advance!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, we are merging some programs from Miracle Linux, and after that, the native device support will be easier. Then RAID support should be easier.
This might happen in 3 months. Please be patient.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm new to Clonezilla and trying to understand its current RAID limitations.
SCENARIO:
Source drive: Windows XP with four partions (1 active FAT32, 2 more FAT32 and 1 NTFS); no RAID
New comp: two disks connected in Motherboard RAID 1 (mirrored) and splited as 4 different partions (similar to the source drive).
QUESTION:
1. Will Clonezilla Live see the RAID-1-partions even if it would not "see" the RAID-array?
2. If yes to question 1, does it see two disks with 4 partions each or one disk with 4 partions?
2b. Would it be possible to "restore" any partion from the file-images? (I suppose that if it's possible to "restore" only one of the drives in the RAID 1 setting, the other drive would "automatically" be synchronized by the RAID controller.)
I'm willing to put some time for testing this, but if it's "impossible" it would be a waste of time.
Thanks for any input on this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Peksim,
I'm by no means an expert on either clonezilla or RAID, but I've played around with some motherboard based RAID1 and I use clonezilla regularly at home and in my business. I'll give you my thoughts, but please take them with a grain of salt:
I'm assuming you're wanting to clone your old drive to the RAID 1 pair.
So what I'd do is this:
Disable the RAID feature on your motherboard.
Partition one of the new drives however you want it.
Clonezilla the first partition of your old drive to the first partition of your new drive.
Try booting from the new drive. You may have to troubleshoot it some (i.e. manually set the flags of the first partition to 'boot' and 'LBA'.
I recently cloned a 22 GB first (boot) partition of a 74 GB drive to a 80 GB first (boot) partition of a 250 GB drive and it booted perfectly the first time - ((CLONEZILLA WIN!))
After you confirm the new drive boots, copy all the files from the old drive's other 3 partitions to the new drive's other 3 partitions (use Xcopy or copy and paste, or use clonezilla. Shouldn't matter since those three partitions, I'm assuming, just have regular files on them, not some fancy operating system files.
OK, now put BOTH the new drives in the computer and enable the motherboard RAID. Tell it to form a RAID1 and let it build the array. Confirm it boots.
Now here's the thing - I have a motherboard with RAID on it, and I run RAID1's. When I pull one drive out, it all works great, except of course the RAID1 is reported as degraded. BUT, when I disable the motherboard RAID1, it recognizes the (previously RAID1'd) drive as a plain old simple drive and it boots fine off it. Obviously, this wouldn't happen if it was originally a RAID0 or 5. So try this. If it works, you can use clonezilla to clone the entire drive over to the second drive (device-to-device) and then see if it boots from the cloned drive (again, with RAID disabled). You can re-enable the RAID and it will rebuild the degraded RAID1 array.
So essentially, what you're doing is converting one of the mirrored drives to a non-RAID by disabling the motherboard RAID,and then using clonezilla on it (and we all know it works great on non-RAID applications).
This works on my system. Hope these thoughts helped.
So
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
let me ask you again for "Fake Raid".
I need this feature because more and more devices are shipt with aktivated Chipset Raid.
In this case it is a Asus Zenbook UX51VZ-CN036H with Intel 7 Series (C216)
Ubuntu 12.10 shows all partitions, right after booting.
Greets, Dirk
I´ve did a bug report for your development:
*********************************************************
The contents of /live/image/Clonezilla-Live-Version:
clonezilla-live-20121126-quantal
This Clonezilla live iso file was created by this command:
ocs-iso -ocs-live-boot-menu-option u -s -extra-boot-param quiet union=overlayfs -i 20121126-quantal
*********************************************************
Installed DRBL/Clonezilla related packages: drbl-2.1.34-drbl1 clonezilla-3.1.22-drbl1 mkswap-uuid-0.1.1-1drbl partclone-0.2.56.drbl1 drbl-chntpw-20110511-1drbl
*********************************************************
/proc/partitions:
major minor #blocks name
Thanks for asking this. So far we haven't addressed this issue. For the past few months we have been working on Clonezilla live 2.x, and now it's done. The RAID device and the device names about those not in /dev/d will be treated in the next phase.
Please keep asking us about this. Thanks again.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are increasingly using RAID in the household and in my business, but it doesn't seem like Clonezilla recognizes RAID partitions at all :( This is really sad, especially since I can't make backups or transfer OS off a RAID C-drive to another drive.
Is there any progress being done on increasing RAID support to a more meaningful level?
Thanks for asking this again. If you software RAID, fakeRAID, not yet. There are so many items to do here…
Please keep pushing us about this. Bug us frequently… and someday we will have that :)
Steven.
These are all hardware RAID, either through a dedicated controller (Like Promise RAID Controller) or through a motherboard RAID controller. Right now 90% of our machines run in some form of RAID (typically RAID 0 or 6)
If it's hardware RAID, and the device name is /dev/sd* or /dev/cciss/*, then Clonezilla can clone it.
What's the device name of your RAID on GNU/Linux?
Steven.
I have no idea, I don't use Linux beyond Clonezilla. All machines are Windows machines. But hardware raid would still need a driver afaik. And what about RAID which are on the motherboard SATA controller?
I would like to echo this. I find that as the technology begins to age, many customers and people find their raid arrays were not so fool-proof. On a windows system, it's a particular pain to reinstall all the software (backing up data is easy, not a problem) with all the regkeys, software activation crap, and all that.
Cloning a raid stripe or raid 5 to a single disk (for raid mirroring) seemed like the promise clonezilla offered, but I've not seen it able to understand any raid configurations (hardware ones) yet. It would really be fantastic if clonezilla could actually clone a hardware raid as though it were a single disk, which right now it fails to do (error about cant have a partition outside the disk).
eogamer,
Please boot Clonezilla live, enter command line prompt, run:
sudo /opt/drbl/sbin/ocs-live-bug-report
then post the generated file.
"what about RAID which are on the motherboard SATA controller? " -> Normally it's FakeRAID.
BTW, RAID is complicated:
1. Driver is required most of the cases
2. There are many RAID types, 0, 1, 5…
3. Linux software RAID is another story…
…
Steven.
I think some people think there is only software and hardware raid. You may want to use the terminology 'firmware' raid to describe the third group, since firmware raid pretends to be hardware, and 97.3% of the public will not know the difference between firmware and hardware raid. I believe the intel raid we use here (almost every one of the many computers we use are going to be intel raid) is firmware, so clonezilla just sees a bunch of disks, not an array. I'll post the bug report though.
===
*********************************************************
The contents of /live/image/Clonezilla-Live-Version:
clonezilla-live-1.2.4-28-686
This Clonezilla live iso file was created by this command:
ocs-iso -s -i 1.2.4-28-686
*********************************************************
Installed DRBL/Clonezilla related packages: drbl-1.9.5-79 clonezilla-2.3.5-21 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.8-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.2.7-1drbl drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.6-1 pbzip2-1.1.0-1drbl udpcast-20091031-1drbl
*********************************************************
/proc/partitions:
major minor #blocks name
8 16 732574584 sdb
8 0 732574584 sda
8 1 732573560 sda1
7 0 103812 loop0
*********************************************************
Partition lists on the system:
Error: /dev/sdb: unrecognised disk label
Error: Can't have a partition outside the disk!
*********************************************************
The info from blkid:
/dev/sdb: TYPE="isw_raid_member"
/dev/sda1: TYPE="isw_raid_member"
/dev/loop0: TYPE="squashfs"
*********************************************************
Clonezilla image repository dir /home/partimag is aufs
*********************************************************
===
Yes, firmware RAID is the fakeRAID I mentioned. It's true the name "firmware RAID" is a better description than fakeRAID.
Could you please:
1. Boot Clonezilla live on your firmware RAID machine
2. Enter command line prompt
3. ls -alFh /dev/mapper/
Then post the results of (3)?
Thanks.
Steven.
I have a similar situation too….I am using my motherboard intel RAID 1(mirror), I don't know why it is "fake" but it really give me "RAID results" I do have identical disks and when one of it fails to function, I still have my data and with a new disk, it rebuilds…
Anyway, I have the same situation, when Clonezilla asks me to choose the destination for saving the image file, it returns all the hardisks and partitions instead of the volume partitions……I will post a result later by doing what Steven mentioned above. Hope we can use this good free utility. :)
Hi, I have done both commands: sudo……… and ls -alFh…….
But I don't know where is the CLONEZILLA-LIVE-BUG-REPORT…..txt located and so I cannot copy it out.
and the results of mapper….I took a photo of my screen….
in case the image cannot be shown directly:
OK, thanks. Yes, this is "firmware" RAID, or "fake" RAID. Since the OS (GNU/Linux) create the mapping devices for the RAID card, not the RAID card itself.
We will try to make it in the future, but it won't be in the near future, since we need to buy such a motherboard, and need some time to know how to deal with this.
Steven.
Total newbie here. Just a tip for those using RAID1 or RAID10 - as alluded to above, it's _easy _to clone your drive - just pop out one of the drives (or mirrored sets) (there's your clone!), insert another drive(s) and have the RAID rebuild the unit. Viola! This is, of course, only suitable for home or small office.
I would like to see support added for Intel RAID chipset that's on many motherboards (Intel ICH9/ICH10, etc)
Wondering if the Intel chipset is supported on Linux, I googled for it and found this:
http://www.intel.com/support/chipsets/imsm/sb/cs-020663.htm
"Beginning with Linux* kernel version 2.6.18*, the dmraid* utility 1.0.0-rc15 supports RAID 0, RAID 1, and RAID 10.
Beginning with Linux kernel version 2.6.27*, the mdadm* utility 3.0 supports RAID 0, RAID 1, RAID 10, and RAID 5.
The kernel provides the RAID level support. The utilities support the Intel® Matrix Storage Manager metadata format.
To use the RAID features in dmraid and mdadm, you will need to set up the RAID volume using the Intel® Matrix Storage Manager option ROM (click CTRL + I when prompted during boot to enter the option ROM user interface). Instructions on how to use the RAID features in dmraid and mdadm are included in the man pages within Linux."
I hope we can have this soon. I just discovered CloneZilla and I really like it! I built a new PC and are using RAID1 mirroring.
For now, I am able to make a PartPE boot CD (XP) with the extra intel iaStor.sys driver, and use Drive Image XML and Acronis True Image to backup the partition to files.
Hi Steven. Just bumping this thread as you requested :-D Our school buys thousands of Dells that have the aforementioned Intel Matrix RAID firmware and it'd be wonderful to be able to clone them. I'll try Walter's suggestion above about removnig a disk then letting it rebuild the array after cloning but I'm not convinced that CloneZilla will recognize the disk.
I'm actually more of a FOG user, but whichever solution I can apply to RAID will be a huge advantage. How's that for a little friendly competition? ;-)
Hi!
Bumping this thread again because i also need to backup my fakeraid disks.
Should work with dmraid, available under ubuntu and debian!
Is it possible to load this module after booting from cd from command line and then start clonezilla?
"Is it possible to load this module after booting from cd from command line and then start clonezilla? " -> Not really. Clonezilla will see different disks, not the RAID device.
However, you can use partclone, which is included in Clonezilla live, to do that.
For more info, please run:
partclone.$fs -help
e.g. partclone.ext4 -help
Steven.
Hi! I also need firmware RAID (aka fake RAID) support. There is no software (paid or free) that can backup the RAID 10 configuration we are using in the company. Acronis destroys de RAID when booting and other programs fails to boot or any have other problems.
I can give some info about dmraid devices:
They are inside /dev/mapper but the files in there are symlinks to /dev/dm-0, /dev/dm-1, /dev/dm-2 an so on, but Clonezilla wizards refuses that device names although kernel recognises and activates the raid automatically at boot time.
I think Linux uses /dev/dm-X devices as normal ones, like sda, so maybe just making Clonezilla interface and scripts allow that device names should be enough, or is there any problems when reading and writing from /dev/dm-X instead of sda, sdb and others?
If you think that there is no more changes needed, I could try to modify it.
Thanks in advance!
Yes, we are merging some programs from Miracle Linux, and after that, the native device support will be easier. Then RAID support should be easier.
This might happen in 3 months. Please be patient.
Steven.
Thanks for the info :)
Hi,
I'm new to Clonezilla and trying to understand its current RAID limitations.
SCENARIO:
Source drive: Windows XP with four partions (1 active FAT32, 2 more FAT32 and 1 NTFS); no RAID
New comp: two disks connected in Motherboard RAID 1 (mirrored) and splited as 4 different partions (similar to the source drive).
QUESTION:
1. Will Clonezilla Live see the RAID-1-partions even if it would not "see" the RAID-array?
2. If yes to question 1, does it see two disks with 4 partions each or one disk with 4 partions?
2b. Would it be possible to "restore" any partion from the file-images? (I suppose that if it's possible to "restore" only one of the drives in the RAID 1 setting, the other drive would "automatically" be synchronized by the RAID controller.)
I'm willing to put some time for testing this, but if it's "impossible" it would be a waste of time.
Thanks for any input on this.
Hi Peksim,
I'm by no means an expert on either clonezilla or RAID, but I've played around with some motherboard based RAID1 and I use clonezilla regularly at home and in my business. I'll give you my thoughts, but please take them with a grain of salt:
I'm assuming you're wanting to clone your old drive to the RAID 1 pair.
So what I'd do is this:
Disable the RAID feature on your motherboard.
Partition one of the new drives however you want it.
Clonezilla the first partition of your old drive to the first partition of your new drive.
Try booting from the new drive. You may have to troubleshoot it some (i.e. manually set the flags of the first partition to 'boot' and 'LBA'.
I recently cloned a 22 GB first (boot) partition of a 74 GB drive to a 80 GB first (boot) partition of a 250 GB drive and it booted perfectly the first time - ((CLONEZILLA WIN!))
After you confirm the new drive boots, copy all the files from the old drive's other 3 partitions to the new drive's other 3 partitions (use Xcopy or copy and paste, or use clonezilla. Shouldn't matter since those three partitions, I'm assuming, just have regular files on them, not some fancy operating system files.
OK, now put BOTH the new drives in the computer and enable the motherboard RAID. Tell it to form a RAID1 and let it build the array. Confirm it boots.
Now here's the thing - I have a motherboard with RAID on it, and I run RAID1's. When I pull one drive out, it all works great, except of course the RAID1 is reported as degraded. BUT, when I disable the motherboard RAID1, it recognizes the (previously RAID1'd) drive as a plain old simple drive and it boots fine off it. Obviously, this wouldn't happen if it was originally a RAID0 or 5. So try this. If it works, you can use clonezilla to clone the entire drive over to the second drive (device-to-device) and then see if it boots from the cloned drive (again, with RAID disabled). You can re-enable the RAID and it will rebuild the degraded RAID1 array.
So essentially, what you're doing is converting one of the mirrored drives to a non-RAID by disabling the motherboard RAID,and then using clonezilla on it (and we all know it works great on non-RAID applications).
This works on my system. Hope these thoughts helped.
So
Hi Steven,
let me ask you again for "Fake Raid".
I need this feature because more and more devices are shipt with aktivated Chipset Raid.
In this case it is a Asus Zenbook UX51VZ-CN036H with Intel 7 Series (C216)
Ubuntu 12.10 shows all partitions, right after booting.
Greets, Dirk
I´ve did a bug report for your development:
*********************************************************
The contents of /live/image/Clonezilla-Live-Version:
clonezilla-live-20121126-quantal
This Clonezilla live iso file was created by this command:
ocs-iso -ocs-live-boot-menu-option u -s -extra-boot-param quiet union=overlayfs -i 20121126-quantal
*********************************************************
Installed DRBL/Clonezilla related packages: drbl-2.1.34-drbl1 clonezilla-3.1.22-drbl1 mkswap-uuid-0.1.1-1drbl partclone-0.2.56.drbl1 drbl-chntpw-20110511-1drbl
*********************************************************
/proc/partitions:
major minor #blocks name
7 0 100996 loop0
8 0 250059096 sda
8 16 250059096 sdb
252 0 482345216 dm-0
252 1 307200 dm-1
252 2 614400 dm-2
252 3 131072 dm-3
252 4 192936960 dm-4
252 5 267381760 dm-5
252 6 20971520 dm-6
252 7 17755392 dm-7
11 0 131076 sr0
*********************************************************
Partition lists on the system:
Error: Invalid argument during seek for read on /dev/sda
Error: /dev/sdb: unrecognised disk label
*********************************************************
The info from blkid:
/dev/loop0: TYPE="squashfs"
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/mapper/isw_bcgcccbadc_RAID0SYS1: LABEL="SYSTEM" UUID="70F1-A5D3" TYPE="vfat"
/dev/mapper/isw_bcgcccbadc_RAID0SYS2: LABEL="Recovery" UUID="9CE4C18AE4C166DC" TYPE="ntfs"
/dev/mapper/isw_bcgcccbadc_RAID0SYS4: LABEL="OS" UUID="CC589790589777C2" TYPE="ntfs"
/dev/mapper/isw_bcgcccbadc_RAID0SYS5: LABEL="DATA" UUID="6AB47ED3B47EA16D" TYPE="ntfs"
/dev/mapper/isw_bcgcccbadc_RAID0SYS6: LABEL="Restore" UUID="C8B0C7FAB0C7ECCE" TYPE="ntfs"
/dev/sr0: LABEL="20121126-quantal" TYPE="iso9660"
*********************************************************
Clonezilla image repository dir /home/partimag is overlayfs
*********************************************************
===
Thanks for asking this. So far we haven't addressed this issue. For the past few months we have been working on Clonezilla live 2.x, and now it's done. The RAID device and the device names about those not in /dev/d will be treated in the next phase.
Please keep asking us about this. Thanks again.
Steven.