I try to run imagemount, but it does not seem to have an effect. I have
not used NBD (Network Block Device) before.
I run the example from the manpage:
$ imagemount -d /dev/nbd0 -f mypartition.partclone -r
Launched in daemon mode: All logging output being written to the system log.
It does not emit an error.
Is /dev/nbd0 a device that must exist before running imagemount or is it
something that imagemount creates? If the first case applies, how would I
create /dev/nbd0? If the second case applies, does imagemount requires
root privileges? What pieces of the NBD suite of software are required to
run imagemount? At my first attempt of running imagemount, I had not
installed anything related to NBD. Then I installed some Debian NBD
packages. The result in both cases was the same.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a temporary workaround, try following the guide I've written here which documents how to use the partclone-nbd tool (rather than this partclone-utils tool) in your standalone Linux environment.
You'll of course first need to download and build the partclone-nbd source code (from here), but since you've already appear to have done this for partclone-utils it shouldn't be much of a problem.
Hopefully that helps.
The Rescuezilla graphical frontend will always provide the easiest way to mount images, and the next version should provide a simple high-level command-line interface to deal with any random partclone-based image without having to delve into the low-level NBD details.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get the same issue on Arch Linux, partclone-utils fails silently unless I pass -D in which case it fails with an error message. I found that errors like /dev/ndb0: cannot connect: No such file or directory show up in journalctl. I think there are two problems: error messages are not shown to the user and don't set the return code to a nonzero value (they're only logged), and either imagemount is broken or I'm calling it incorrectly.
Is there a diagnosis or fix planned?
Last edit: nyanpasu64 2022-06-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I try to run imagemount, but it does not seem to have an effect. I have
not used NBD (Network Block Device) before.
I run the example from the manpage:
$ imagemount -d /dev/nbd0 -f mypartition.partclone -r
Launched in daemon mode: All logging output being written to the system log.
It does not emit an error.
Is /dev/nbd0 a device that must exist before running imagemount or is it
something that imagemount creates? If the first case applies, how would I
create /dev/nbd0? If the second case applies, does imagemount requires
root privileges? What pieces of the NBD suite of software are required to
run imagemount? At my first attempt of running imagemount, I had not
installed anything related to NBD. Then I installed some Debian NBD
packages. The result in both cases was the same.
Hi Amiga Lemming,
As a temporary workaround, try following the guide I've written here which documents how to use the
partclone-nbdtool (rather than thispartclone-utilstool) in your standalone Linux environment.You'll of course first need to download and build the
partclone-nbdsource code (from here), but since you've already appear to have done this forpartclone-utilsit shouldn't be much of a problem.Hopefully that helps.
The Rescuezilla graphical frontend will always provide the easiest way to mount images, and the next version should provide a simple high-level command-line interface to deal with any random partclone-based image without having to delve into the low-level NBD details.
I get the same issue on Arch Linux, partclone-utils fails silently unless I pass
-Din which case it fails with an error message. I found that errors like/dev/ndb0: cannot connect: No such file or directoryshow up in journalctl. I think there are two problems: error messages are not shown to the user and don't set the return code to a nonzero value (they're only logged), and either imagemount is broken or I'm calling it incorrectly.Is there a diagnosis or fix planned?
Last edit: nyanpasu64 2022-06-21