aeromaxx
Posts: 20
Joined: Sat Jun 11, 2016 11:37 am

Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 6:23 am

I found a question over on the Raspberry Pi Stack Exchange that talked about updating software in raspberry pi images to save SD write cycles.

This is something I have been able to do successfully following the answer posted here: https://raspberrypi.stackexchange.com/q ... g-an-image

What I am having a problem with is unmounting the image and all the partitions.

These are the commands that I used to mount the paritions.

Code: Select all

sudo mount --rbind /dev --verbose /mnt/rpi/rootfs/dev;
sudo mount --types proc none --verbose /mnt/rpi/rootfs/proc;
sudo mount --options bind /sys --verbose /mnt/rpi/rootfs/sys;

# mount: /dev bound on /mnt/rpi/rootfs/dev.
# mount: none mounted on /mnt/rpi/rootfs/proc.
# mount: /sys bound on /mnt/rpi/rootfs/sys.

sudo chroot /mnt/rpi/rootfs;
Detaching from the screen that I was chrooted into with CTRL+D and then using the DF tool to get information about the mounted partitions showed the following output below. Some of these mounts I can unmount but others can't be as I get an error message saying that the target is busy.

Before unmount.

Code: Select all

$ df --all

/dev/mapper/loop0p1     42030     21420     20610  51% /mnt/rpi/boot
/dev/mapper/loop0p2   1089132    956848     58920  95% /mnt/rpi/rootfs
udev                   924264         0    924264   0% /mnt/rpi/rootfs/dev
devpts                      0         0         0    - /mnt/rpi/rootfs/dev/pts
tmpfs                  954300       328    953972   1% /mnt/rpi/rootfs/dev/shm
mqueue                      0         0         0    - /mnt/rpi/rootfs/dev/mqueue
hugetlbfs                   0         0         0    - /mnt/rpi/rootfs/dev/hugepages
none                        -         -         -    - /mnt/rpi/rootfs/proc
sysfs                       0         0         0    - /mnt/rpi/rootfs/sys
After unmount.

Code: Select all

$ df --all

/dev/mapper/loop0p2   1089132    956848     58920  95% /mnt/rpi/rootfs
udev                   924264         0    924264   0% /mnt/rpi/rootfs/dev
devpts                      0         0         0    - /mnt/rpi/rootfs/dev/pts
tmpfs                  954300       328    953972   1% /mnt/rpi/rootfs/dev/shm
Some additional output from other commands.

Code: Select all

$ fuser --all --verbose /mnt/rpi/rootfs/dev/shm

                     USER PID ACCESS COMMAND
/mnt/rpi/rootfs/dev/shm:
                     root     kernel mount /dev/shm

Code: Select all

$ fuser --all --verbose /mnt/rpi/rootfs/dev/pts

                     USER PID ACCESS COMMAND
/mnt/rpi/rootfs/dev/pts:
                     root     kernel mount /dev/pts

Code: Select all

$ fuser --all --verbose /mnt/rpi/rootfs/dev

                     USER PID ACCESS COMMAND
/mnt/rpi/rootfs/dev:
                     root     kernel mount /dev

Code: Select all

$ fuser --all --verbose /mnt/rpi/rootfs

                     USER PID ACCESS COMMAND
/mnt/rpi/rootfs:
                     root     kernel mount /mnt/rpi/rootfs

Code: Select all

$ lsof +D /mnt/rpi/rootfs/dev

COMMAND    PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
systemd    984 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-sess  998 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-sess  998 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-laun 1192 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-laun 1192 username01    1u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-laun 1192 username01    2u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-daem 1207 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-daem 1207 username01    1u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-daem 1207 username01    2u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
at-spi-bu 1422 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dbus-daem 1427 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
at-spi2-r 1429 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
dconf-ser 1436 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-sett 1444 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-sett 1444 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-pane 1470 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-pane 1470 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd     1500 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-fus 1505 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-fus 1505 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-fus 1505 username01    2w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-fus 1505 username01    3u   CHR 10,229      0t0   85 /mnt/rpi/rootfs/dev/fuse
caja      1518 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
caja      1518 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
wnck-appl 1522 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-udis 1524 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
polkit-ma 1527 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
polkit-ma 1527 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-maxi 1528 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-maxi 1528 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
blueman-a 1531 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
blueman-a 1531 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
blueman-a 1531 username01   13r   CHR  10,62      0t0    4 /mnt/rpi/rootfs/dev/rfkill
mate-volu 1578 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-volu 1578 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-powe 1579 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-powe 1579 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
nm-applet 1584 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
nm-applet 1584 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
nm-applet 1584 username01    3r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
nm-applet 1584 username01    5u   CHR  226,0      0t0  341 /mnt/rpi/rootfs/dev/dri/card0
tilda     1586 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
tilda     1586 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
tilda     1586 username01    3r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
tilda     1586 username01    6u   CHR  226,0      0t0  341 /mnt/rpi/rootfs/dev/dri/card0
tilda     1586 username01   16u   CHR    5,2      0t0   87 /mnt/rpi/rootfs/dev/ptmx
update-no 1599 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
update-no 1599 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
update-no 1599 username01    4u   CHR  226,0      0t0  341 /mnt/rpi/rootfs/dev/dri/card0
mate-scre 1603 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
mate-scre 1603 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
deja-dup- 1606 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
deja-dup- 1606 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
applet.py 1610 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
applet.py 1610 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
applet.py 1610 username01    3r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
gvfsd-tra 1619 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-afc- 1629 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-afc- 1629 username01    3r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
pulseaudi 1644 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
pulseaudi 1644 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
pulseaudi 1644 username01    2w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
pulseaudi 1644 username01   16u   CHR  116,2      0t0  448 /mnt/rpi/rootfs/dev/snd/controlC0
pulseaudi 1644 username01   23u   CHR  116,2      0t0  448 /mnt/rpi/rootfs/dev/snd/controlC0
pulseaudi 1644 username01   28u   CHR  116,2      0t0  448 /mnt/rpi/rootfs/dev/snd/controlC0
marco     1659 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
marco     1659 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-gpho 1723 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
syndaemon 1733 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
syndaemon 1733 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-mtp- 1792 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfs-goa- 1799 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
trashappl 1814 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
clock-app 1819 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
notificat 1821 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-met 1932 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-net 1965 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-smb 1987 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
gvfsd-smb 1987 username01    3r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
gvfsd-smb 1987 username01   12r   CHR    1,9      0t0   11 /mnt/rpi/rootfs/dev/urandom
gvfsd-dns 2049 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
obexd     2227 username01    0u   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
popsquare 2993 username01    0r   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null
popsquare 2993 username01    1w   CHR    1,3      0t0    6 /mnt/rpi/rootfs/dev/null

Code: Select all

$ lsof +D /mnt/rpi/rootfs/dev/pts

COMMAND  PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bash    1951 username01    0u   CHR  136,1      0t0    4 /mnt/rpi/rootfs/dev/pts/1
bash    1951 username01    1u   CHR  136,1      0t0    4 /mnt/rpi/rootfs/dev/pts/1
bash    1951 username01    2u   CHR  136,1      0t0    4 /mnt/rpi/rootfs/dev/pts/1
bash    1951 username01  255u   CHR  136,1      0t0    4 /mnt/rpi/rootfs/dev/pts/1
bash    2581 username01    0u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
bash    2581 username01    1u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
bash    2581 username01    2u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
bash    2581 username01  255u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
lsof    3065 username01    0u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
lsof    3065 username01    1u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2
lsof    3065 username01    2u   CHR  136,2      0t0    5 /mnt/rpi/rootfs/dev/pts/2

Code: Select all

$ lsof +D /mnt/rpi/rootfs/dev/shm

COMMAND    PID       USER  FD   TYPE DEVICE SIZE/OFF NODE NAME
mate-sett 1444 username01 mem    REG   0,25 67108904    5 /mnt/rpi/rootfs/dev/shm/pulse-shm-3418099913
mate-sett 1444 username01 mem    REG   0,25 67108904    6 /mnt/rpi/rootfs/dev/shm/pulse-shm-1776820011
caja      1518 username01 mem    REG   0,25 67108904    5 /mnt/rpi/rootfs/dev/shm/pulse-shm-3418099913
caja      1518 username01 mem    REG   0,25 67108904    3 /mnt/rpi/rootfs/dev/shm/pulse-shm-3660422944
mate-volu 1578 username01 mem    REG   0,25 67108904    5 /mnt/rpi/rootfs/dev/shm/pulse-shm-3418099913
mate-volu 1578 username01 mem    REG   0,25 67108904    7 /mnt/rpi/rootfs/dev/shm/pulse-shm-963002600
update-no 1599 username01 mem    REG   0,25 67108904    5 /mnt/rpi/rootfs/dev/shm/pulse-shm-3418099913
update-no 1599 username01 mem    REG   0,25 67108904    8 /mnt/rpi/rootfs/dev/shm/pulse-shm-2165640840
pulseaudi 1644 username01 mem    REG   0,25 67108904    5 /mnt/rpi/rootfs/dev/shm/pulse-shm-3418099913
pulseaudi 1644 username01 mem    REG   0,25 67108904    4 /mnt/rpi/rootfs/dev/shm/pulse-shm-1934004479

k-pi
Posts: 637
Joined: Sun Feb 12, 2017 1:46 pm
Location: Upper Hale, Surrey, UK.

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 9:00 am

Detaching from the screen that I was chrooted into with CTRL+D
You are still in the changerooted system, detaching just means that you can reattach elsewhere or from another computer, it leaves the system running in the background, if I remember, so you need to exit the changerooted system.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5344
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 9:17 am

I'd also be curious to know how to avoid this problem, as I never got to the bottom of it.

I've switched to using systemd-nspawn instead, which works much better.
k-pi wrote:
Tue Oct 16, 2018 9:00 am
Detaching from the screen that I was chrooted into with CTRL+D
You are still in the changerooted system, detaching just means that you can reattach elsewhere or from another computer, it leaves the system running in the background, if I remember, so you need to exit the changerooted system.
ctrl-d is 'end of file' rather than detach (as opposed to ctrl-a d, which is the default sequence to detach from screen and leave it running in the background). ctrl-d will exit the shell, quitting screen if it's the last windows that was open.

mfa298
Posts: 1325
Joined: Tue Apr 22, 2014 11:18 am

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 11:22 am

aeromaxx wrote:
Tue Oct 16, 2018 6:23 am
What I am having a problem with is unmounting the image and all the partitions.

These are the commands that I used to mount the paritions.

Code: Select all

sudo mount --rbind /dev --verbose /mnt/rpi/rootfs/dev;
sudo mount --types proc none --verbose /mnt/rpi/rootfs/proc;
sudo mount --options bind /sys --verbose /mnt/rpi/rootfs/sys;

# mount: /dev bound on /mnt/rpi/rootfs/dev.
# mount: none mounted on /mnt/rpi/rootfs/proc.
# mount: /sys bound on /mnt/rpi/rootfs/sys.

sudo chroot /mnt/rpi/rootfs;
After exiting the chroot you need to un-mount those filesystems first before trying to un-mount the pi image. The other issue you might have is when you install updates that might start up some processes within the chroot which you would also need to stop first (what these might be would potentially depend on the packages you install). There might be a way to stop apt/dpkg starting any processes during the upgrade.

I'm wondering if you actually need to mount those filesystems - I've done a bit of work adding stuff to a standard Raspbian lite image and usually just mount the two partitions in the image (/ and /boot) and nothing else.

I might also recommend looking at kpartx, it'll create something like /dev/mapper/loop0p1 and /dev/mapper/loop0p2 without you having to look up the offsets for the mount command.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5344
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 12:07 pm

losetup -P is better than kpartx, since your partitions end up in /dev/loopXpY, rather than /dev/mapper/loopXpY, so some tools understand it better.

The issue for me was that you couldn't umount those remaining partitions and there were no processes launched from inside the chroot that were using them. I thought that's what OP is describing as well.

aeromaxx
Posts: 20
Joined: Sat Jun 11, 2016 11:37 am

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 1:47 pm

k-pi wrote:
Tue Oct 16, 2018 9:00 am
You are still in the changerooted system, detaching just means that you can reattach elsewhere or from another computer, it leaves the system running in the background, if I remember, so you need to exit the changerooted system.
How would I exit the changerooted system?

I have tried typing exit, but I was still unable to umount the mounted image.
mfa298 wrote:
Tue Oct 16, 2018 11:22 am
After exiting the chroot you need to un-mount those filesystems first before trying to un-mount the pi image.

<snip>

I might also recommend looking at kpartx, it'll create something like /dev/mapper/loop0p1 and /dev/mapper/loop0p2 without you having to look up the offsets for the mount command.
I am unable to unmount those file systems as mentioned in the original post I get the message that the device is busy.

I am also using kpartx to mount the image initally.
ShiftPlusOne wrote:
Tue Oct 16, 2018 12:07 pm
The issue for me was that you couldn't umount those remaining partitions and there were no processes launched from inside the chroot that were using them. I thought that's what OP is describing as well.
Yes you are correct this was what I was describing, I can't unmount those remaining partitions as I get the error message that the device is busy.

k-pi
Posts: 637
Joined: Sun Feb 12, 2017 1:46 pm
Location: Upper Hale, Surrey, UK.

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 2:43 pm

How do I exit from chrooted jail?

Type exit
$ exit
https://www.cyberciti.biz/faq/unix-linu ... ge-syntax/
Is there a way to get back to the original root?? Or have I put myself into the "jail" thing that I've run into while googling for an answer to this?

Thanks
Rich
· actions · 2007-Mar-12 7:57 pm ·

nwrickert
Mod
join:2004-09-04
Geneva, IL

Yes, you have put yourself in chroot jail.

However


exit


will exit from the chroot shell, and you will be back where you were just before the chroot.

aeromaxx
Posts: 20
Joined: Sat Jun 11, 2016 11:37 am

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 2:54 pm

k-pi wrote:
Tue Oct 16, 2018 2:43 pm
How do I exit from chrooted jail?

Type exit
$ exit
I tried typing exit, but I am still unable to unmount the partitions, they are still busy.

k-pi
Posts: 637
Joined: Sun Feb 12, 2017 1:46 pm
Location: Upper Hale, Surrey, UK.

Re: Chrooting raspberry pi images unable to unmount?

Tue Oct 16, 2018 6:24 pm

Some of these mounts I can unmount
If that is what you did, you may well have a broken chroot, & therefore not being able to exit it.

aeromaxx
Posts: 20
Joined: Sat Jun 11, 2016 11:37 am

Re: Chrooting raspberry pi images unable to unmount?

Wed Oct 17, 2018 11:13 am

k-pi wrote:
Tue Oct 16, 2018 6:24 pm
Some of these mounts I can unmount
If that is what you did, you may well have a broken chroot, & therefore not being able to exit it.
I don't see how I could have possibly broken chroot when all I have done is typed in the chroot command and then typed in exit once in the chroot environment.

The partitions are busy when trying to unmount them, have you tried to do it? and were you able to do it successfully?

mfa298
Posts: 1325
Joined: Tue Apr 22, 2014 11:18 am

Re: Chrooting raspberry pi images unable to unmount?

Wed Oct 17, 2018 11:25 am

aeromaxx wrote:
Wed Oct 17, 2018 11:13 am
The partitions are busy when trying to unmount them, have you tried to do it? and were you able to do it successfully?
It might help if you listed out all the steps you've taken so someone else can try and replicate it. It could be a simple issue in how your doing things or could be something more complex (all I can say is it's not something I've had an issue with when I've worked in a chroot, but I'm probably not doing the same things as you).

k-pi
Posts: 637
Joined: Sun Feb 12, 2017 1:46 pm
Location: Upper Hale, Surrey, UK.

Re: Chrooting raspberry pi images unable to unmount?

Wed Oct 17, 2018 11:45 am

aeromaxx wrote:
Wed Oct 17, 2018 11:13 am
.. have you tried to do it? and were you able to do it successfully?
Unmounting partitions whilst in a chroot environment - no.
Have I used a chroot environment - yes.
(& exited without any problems) 8-)

aeromaxx
Posts: 20
Joined: Sat Jun 11, 2016 11:37 am

Re: Chrooting raspberry pi images unable to unmount?

Wed Oct 17, 2018 5:24 pm

k-pi wrote:
Wed Oct 17, 2018 11:45 am
aeromaxx wrote:
Wed Oct 17, 2018 11:13 am
.. have you tried to do it? and were you able to do it successfully?
Unmounting partitions whilst in a chroot environment - no.
Have I used a chroot environment - yes.
(& exited without any problems) 8-)
Oh you have misundestood my initial post, I'm not trying to unmount partitions whilst in a chroot environment.

I can use the chroot environment and exit without errors, that's not the issue I am having.

The problem I am having is unmounting the partitions and the disk image after using chroot.

Return to “Advanced users”