When usb-creator runs it seems to mount the target partition right away.
When it tries to run /sbin/parted--that program appears to return a non-zero return code. It is attempting to set the boot flag for the target partition.
When I run /sbin/parted manually with the same parameters I seem to get an return code of 1 and I get the
following message:
WARNING: the kernel failed to re-read the partition table on /dev/sdb
(Device or resource busy). As a result, it may not reflect all of your changes
until after reboot.
(package parted file libparted/arch/linux.c)
Unmounting the target partition and running parted allows parted to run without the warning. This is from GNU parted 2.1.
I tried this on a karmic partition using parted 1.8.8.1.159-1e0e and, with the partition mounted, it doesn't produce this
message (or the problem when running usb-creator).
I suspect that this is what has changed. Perhaps unmounting the target partition for the length of the parted command would suffice.
When usb-creator runs it seems to mount the target partition right away.
When it tries to run /sbin/parted--that program appears to return a non-zero return code. It is attempting to set the boot flag for the target partition.
When I run /sbin/parted manually with the same parameters I seem to get an return code of 1 and I get the
following message:
WARNING: the kernel failed to re-read the partition table on /dev/sdb
(Device or resource busy). As a result, it may not reflect all of your changes
until after reboot.
(package parted file libparted/ arch/linux. c)
Unmounting the target partition and running parted allows parted to run without the warning. This is from GNU parted 2.1.
I tried this on a karmic partition using parted 1.8.8.1.159-1e0e and, with the partition mounted, it doesn't produce this
message (or the problem when running usb-creator).
I suspect that this is what has changed. Perhaps unmounting the target partition for the length of the parted command would suffice.