In the past I've always been able to work with Intel RST RAID volumes. During device detection, I would see them listed just like any other device....something like this:
/dev/md126
/dev/sda
/dev/sdb
where the md device ( /dev/md126 in this case) would be the RAID device.
I could save images from them and restore images into them.
Since the June 2021 version (at least), a message comes up during device detection that says:
"excluding linux RAID member partition"
/dev/sda
/dev/sdb
I know it says "linux raid" but I see that message with brand new, blank hard drives, so it's not a linux partition issue.
If I go to a command prompt and type
mdadm --detail /dev/md126
it will show details for the volume, so mdadm is seeing it and mounting it.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please run the following commands in the command line prompt:
1. sudo -i
2. blkid
3. cat /proc/partitions
4. mdadm --detail /dev/md126
Please post the results of 2-4, and tell us the whole steps about your run Clonezilla in detail.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Steven, here are the requested outputs and also a screenshot of the device discovery not showing the /dev/md126 device as older versions used to. I noticed that the array is resyncing. In the past I have been able to restore an image into a resyncing volume without issues so I don't think this could be related.
My steps were all defaults....I booted the CD, selected the following options:
Start Clonezilla
device-image
local_dev
enter to discover devices
ctrl-c to exit discovery
select a repository
no-fsck
choose directory for repository
Beginner
"savedisk" or "restoredisk" would have let me pick from the list of devices, but md126 is not in the list to save it to image or to restore an image onto it.
Oh, please run "sudo blkid" to show all the partitions and disks. Otherwise there is no /dev/md126 in your photo.
BTW, you can try "saveparts" instead of "savedisk".
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Post#1
all images are of the “older” version of clonezilla 2.6.7-28 2020 (debian based)
Disregard the "unrecognized label” errors... that's because the drives are blank. It goes away once they get some data in them.
/dev/sda and /dev/sdb are setup as a RAID1 in the Intel RST (that's what /dev/md126 is)
Note how the /dev/md126 volume is listed in the old version of clonezila with a UUID but is not in the newer version. It also shows in the list of destinations...and for sanity I included an image where I am restoring an image into it.
Post#2
all images are of the new “stable” version 20210609 (Ubuntu based, the debian version gives the same results)
There’s no way to access /dev/md126 as a source (to save an image from it) or a destination (to restore a previously saved image into it).
Also, I haven’t had success with “saveparts”. I want to save the entire volume, not individual partitions. I’ve been doing it for years, I’m surprised the option is not there anymore.
When you use saveparts in Clonezilla live >= 2.7.2-39 or 20210609-hirsute, it will show something like:
[ ] md126 30G_md-name-debian:126 [*] md126p1 4G_ext4_md-name-debian:126 [*] md126p2 26G_btrfs_md-name-debian:126
You can choose something like the above.
Since /dev/md126 can be a disk or a partition. We need to find a better way to judge that. If you have any suggestion, please let us know. Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please give testing Clonezilla live 2.7.3-18 or 20210809-* a try: https://clonezilla.org/downloads.php
I believe this issue is fixed. You can use savedisk to save /dev/md126.
Please let us know the results. Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can confirm that the "test" version of Clonezilla you indicated, 2.7.3-18 does the following: does display /dev/md126 in the list of discovered devices does allow to save /dev/md126 to an image
* does not allow an image to be restored into /dev/md126 as it does not display md126 in the list of available targets.
Thanks for reporting this issue.
Please give testing Clonezilla live 2.7.3-19 a try. I believe this issue about restoring the image to md device is fixed.
Please let us know the results. Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Success!
I can report that version 2.7.3-19 fixed the issue: it allows saving the "md" device to an image AND it allows to restore an image into the "md" device.
Thanks for all the help!
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello again, sorry to resurrect my previous post but I'm having the same issue again with the latest versions of Clonezilla.
I've tried 20220103-impish, 2.8.1-12 and also gave the i686 2.8.1-12 a try. They all have the same behavior, which is the "md" device missing as a source.
I've tried on computers running in Legacy (MBR disks) mode and on computers running in UEFI (GPT disks) mode.
In the UEFI computers, I tried also booting in Legacy mode but it made no difference.
Any help?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What is the MD devices you have? We made some changes last Aug IIRC, if the md device name can not be identified with some partitions, then it will be treated as a partition. E.g.,
/dev/md126 with ext4 -> A partition
/dev/md126, and /dev/md126p1 exists, -> /dev/md126 is a disk, and /dev/md126p1 is a partition.
Hence try to use "saveparts" and "restoreparts" if you have something like /dev/md126, and no /dev/md126p1 exists.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These are Windows 10 Dells with the boot drive in RAID1. Since they are boot systems, they surely have more than one partition...and for that same reason, saveparts won't work.
I have tried booting with an old Clonezilla 2018 and that one does see the md126 device as a source and works fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried saveparts in the past and after restoring the image (or images) the volume would not be bootable. My assumption was that to copy an entire (bootable) volume, it had to be done with savedisk not saveparts. Was I wrong about that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By default when "restoreparts" is used, the option "-g auto" and "-k1" are not enabled.
If the restored OS is GNU/Linux, please enter expert mode, and choose "-g auto" so that grub can be reinstalled.
What OS did you restore? In uEFI mode or legacy mode?
What were the error messages about booting issue?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course savedisk can be improved. However, the culprit is not really on savedisk I believe. Say,
if your block device is /dev/md126 with ext4, then it's not a disk. It's a partition in Clonezilla. Which disk does it belong to? Maybe it should belong to /dev/md126. However, Clonezilla will be confused... The /dev/md126 is a disk and a partition simultaneously... This will break a lot of relations about disk and partition in Clonezilla.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the past I've always been able to work with Intel RST RAID volumes. During device detection, I would see them listed just like any other device....something like this:
/dev/md126
/dev/sda
/dev/sdb
where the md device ( /dev/md126 in this case) would be the RAID device.
I could save images from them and restore images into them.
Since the June 2021 version (at least), a message comes up during device detection that says:
"excluding linux RAID member partition"
/dev/sda
/dev/sdb
I know it says "linux raid" but I see that message with brand new, blank hard drives, so it's not a linux partition issue.
If I go to a command prompt and type
mdadm --detail /dev/md126
it will show details for the volume, so mdadm is seeing it and mounting it.
Any ideas?
Please run the following commands in the command line prompt:
1. sudo -i
2. blkid
3. cat /proc/partitions
4. mdadm --detail /dev/md126
Please post the results of 2-4, and tell us the whole steps about your run Clonezilla in detail.
Thanks.
Steven
Steven, here are the requested outputs and also a screenshot of the device discovery not showing the /dev/md126 device as older versions used to. I noticed that the array is resyncing. In the past I have been able to restore an image into a resyncing volume without issues so I don't think this could be related.
So what you want is to use /dev/md126 as the image repository? Not to save /dev/md126 as an image?
Steven
I want to be able to create an image from the /dev/md126 volume...older versions allowed that.
Last edit: Enrix 2021-08-02
OK, and what's the result for "blkid"? You did not provide that. Thanks.
Steven
BTW, what were the steps you have choose? Please let us know in detail so that we can try to reproduce this issue.
Thanks.
Steven
My steps were all defaults....I booted the CD, selected the following options:
Start Clonezilla
device-image
local_dev
enter to discover devices
ctrl-c to exit discovery
select a repository
no-fsck
choose directory for repository
Beginner
"savedisk" or "restoredisk" would have let me pick from the list of devices, but md126 is not in the list to save it to image or to restore an image onto it.
Here attached is the result from blkid
Oh, please run "sudo blkid" to show all the partitions and disks. Otherwise there is no /dev/md126 in your photo.
BTW, you can try "saveparts" instead of "savedisk".
Steven
Post#1
all images are of the “older” version of clonezilla 2.6.7-28 2020 (debian based)
Disregard the "unrecognized label” errors... that's because the drives are blank. It goes away once they get some data in them.
/dev/sda and /dev/sdb are setup as a RAID1 in the Intel RST (that's what /dev/md126 is)
Note how the /dev/md126 volume is listed in the old version of clonezila with a UUID but is not in the newer version. It also shows in the list of destinations...and for sanity I included an image where I am restoring an image into it.
Post#2
all images are of the new “stable” version 20210609 (Ubuntu based, the debian version gives the same results)
There’s no way to access /dev/md126 as a source (to save an image from it) or a destination (to restore a previously saved image into it).
Also, I haven’t had success with “saveparts”. I want to save the entire volume, not individual partitions. I’ve been doing it for years, I’m surprised the option is not there anymore.
When you use saveparts in Clonezilla live >= 2.7.2-39 or 20210609-hirsute, it will show something like:
[ ] md126 30G_md-name-debian:126
[*] md126p1 4G_ext4_md-name-debian:126
[*] md126p2 26G_btrfs_md-name-debian:126
You can choose something like the above.
Since /dev/md126 can be a disk or a partition. We need to find a better way to judge that. If you have any suggestion, please let us know. Thanks.
Steven
Please give testing Clonezilla live 2.7.3-18 or 20210809-* a try:
https://clonezilla.org/downloads.php
I believe this issue is fixed. You can use savedisk to save /dev/md126.
Please let us know the results. Thanks.
Steven
I can confirm that the "test" version of Clonezilla you indicated, 2.7.3-18 does the following:
does display /dev/md126 in the list of discovered devices
does allow to save /dev/md126 to an image
* does not allow an image to be restored into /dev/md126 as it does not display md126 in the list of available targets.
see attached images
Last edit: Enrix 2021-08-14
Thanks for reporting this issue.
Please give testing Clonezilla live 2.7.3-19 a try. I believe this issue about restoring the image to md device is fixed.
Please let us know the results. Thanks.
Steven
Success!
I can report that version 2.7.3-19 fixed the issue: it allows saving the "md" device to an image AND it allows to restore an image into the "md" device.
Thanks for all the help!
Great. Thanks for your feedback.
Steven
Hello again, sorry to resurrect my previous post but I'm having the same issue again with the latest versions of Clonezilla.
I've tried 20220103-impish, 2.8.1-12 and also gave the i686 2.8.1-12 a try. They all have the same behavior, which is the "md" device missing as a source.
I've tried on computers running in Legacy (MBR disks) mode and on computers running in UEFI (GPT disks) mode.
In the UEFI computers, I tried also booting in Legacy mode but it made no difference.
Any help?
What is the MD devices you have? We made some changes last Aug IIRC, if the md device name can not be identified with some partitions, then it will be treated as a partition. E.g.,
/dev/md126 with ext4 -> A partition
/dev/md126, and /dev/md126p1 exists, -> /dev/md126 is a disk, and /dev/md126p1 is a partition.
Hence try to use "saveparts" and "restoreparts" if you have something like /dev/md126, and no /dev/md126p1 exists.
Steven
These are Windows 10 Dells with the boot drive in RAID1. Since they are boot systems, they surely have more than one partition...and for that same reason, saveparts won't work.
I have tried booting with an old Clonezilla 2018 and that one does see the md126 device as a source and works fine.
The mode saveparts/restoreparts in Clonezilla can deal with more than one partitions. Do you have any issue to choose two or more ones?
Steven
I have tried saveparts in the past and after restoring the image (or images) the volume would not be bootable. My assumption was that to copy an entire (bootable) volume, it had to be done with savedisk not saveparts. Was I wrong about that?
By default when "restoreparts" is used, the option "-g auto" and "-k1" are not enabled.
If the restored OS is GNU/Linux, please enter expert mode, and choose "-g auto" so that grub can be reinstalled.
What OS did you restore? In uEFI mode or legacy mode?
What were the error messages about booting issue?
Steven
I'd have to recreate the issues with saveparts...I haven't tried saveparts in years since savedisk was working perfectly until now.
At this point it looks like you're implying that there is no fix for working with md devices with savedisk, correct?
(I have to say, I'm a bit surprised that I am the only person in the entire planet with an issue saving images from a intel RST RAID1 boot drive)
Of course savedisk can be improved. However, the culprit is not really on savedisk I believe. Say,
if your block device is /dev/md126 with ext4, then it's not a disk. It's a partition in Clonezilla. Which disk does it belong to? Maybe it should belong to /dev/md126. However, Clonezilla will be confused... The /dev/md126 is a disk and a partition simultaneously... This will break a lot of relations about disk and partition in Clonezilla.
Steven