Caja - Unmount USB stick failed

Post here if you are a new Porteus member and you're looking for some help.
tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#1 by tom2238 » 10 Sep 2019, 19:39

Hello.
I'm trying unmount USB stick in Caja, but i get this error:

Code: Select all

Error ejecting /dev/sdb: Command-line `eject "/dev/sdb"' exited with non-zero exit status 1: umount: /mnt/sdb1: not mounted
eject: unmount of `/mnt/sdb1' failed
It's look like the USB stick is successfully unmounted. However, error dialog always appear. In always fresh mode it works well and no error window is displayed.
How to fix this error?

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#2 by Ed_P » 10 Sep 2019, 21:46

What startup cheatcodes are you using?
Ed

tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#3 by tom2238 » 11 Sep 2019, 07:31

Current cheatcodes are:

Code: Select all

guest@porteus:~$ cat /proc/cmdline 
quiet from=/dev/sda6 nocd zram=5% changes=/ timezone=Europe/Warsaw noload=000-lxde norootcopy fsck

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#4 by Ed_P » 11 Sep 2019, 15:31

I'm no expert but try this combo tom2238.

Code: Select all

quiet from=/mnt/sda6 nocd zram=5% changes=EXIT:/ timezone=Europe/Warsaw noload=000-lxde norootcopy fsck
Ed

tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#5 by tom2238 » 21 Sep 2019, 19:52

So,
First reboot = same error
changes=EXIT:/ cheatcode = same error
Always fresh = no problem
changes-ro cheatcode = same error

Is it problem in DE, maybe?

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#6 by Ed_P » 21 Sep 2019, 22:41

Not if you can boot in AF mode, which includes the DE. What cheatcodes are used in your AF mode? And what modules do you have in your modules directory?
Ed

tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#7 by tom2238 » 22 Sep 2019, 08:11

Cheatcodes in AF:

Code: Select all

from=/dev/sda6 nocd zram=5% timezone=Europe/Warsaw noload=003-lxde norootcopy
Modules are same in normal and AF mode.

Code: Select all

guest@porteus:/mnt/sda6/porteus/modules$ tree 
.
├── audio
│   ├── audacity-2.0.6-i486-1wre.xzm
│   └── lxmp_bass.xzm
├── cs_CZ-locales-files.xzm
├── develop
│   ├── cs-devel_locales.xzm
│   ├── gdb-7.11.1-i586-1.xzm
│   ├── jdk1.8.0_161.xzm 
│   ├── qtcreator_2.5.0-2_i386.xzm 
│   ├── qt-libqtwebkit4_2.3.4_edit_i386.xzm 
│   ├── qt-4.8.7-i586-8.xzm 
│   └── 05-devel.xzm
├── extra
│   ├── epson-inkjet-printer-201601w-1.0.0.xzm 
│   └── 07-printing-i586-03.02.2017.xzm 
├── games
│   ├── aisleriot-3.18.2-4-omv2015.0.i586.xzm
│   ├── bzflag-2.4.12-alt1_all-i586.xzm 
│   ├── gnome-mahjongg-3.10.2-i686-1dl.xzm
│   ├── gnome-tetravex-3.10.1-i686-1dl.xzm
│   └── openttd-1.9.1-i386-pt.xzm 
├── graphics
│   ├── gimp-2.8.6-i486.xzm 
│   └── mtpaint-3.40-i586-2_slonly.xzm
├── lib
│   ├── exfat-porteus.xzm
│   ├── libcares2-1.13.0-1.mga6.i586.xzm
│   ├── libicu57_57.1-6+deb9u2_i386.xzm 
│   ├── libphonon4-4.9.1-1.mga6.i586.xzm
│   ├── porteus_libs_1.xzm
│   └── rt61_driver.xzm
├── lxde
│   └── cs-openbox_locales.xzm
├── mate
│   ├── console-cyrillic-0.9.17-noarch-1.xzm
│   ├── cs-core_locales.xzm
│   ├── cs_CZ-locales-files.xzm
│   ├── cs-mate_locales.xzm
│   ├── glibc-i18n-i586-1jay.xzm
│   ├── gnome-icon-theme-symbolic_3.12.0-1_all.xzm
│   ├── gnome-icon-theme_3.12.0-1ubuntu3_all.xzm
│   ├── la-capitaine-icon-theme.xzm
│   ├── man-files-3.2.2-noarch-1.xzm
│   ├── mate-icon-theme-faenza-1.6.0-i486-1extra.xzm
│   ├── mate-themes-1.6.0-i486-1extra.xzm
│   └── sonar-sound.xzm.xzm
├── net
│   ├── bluez-5.48-i586-1.xzm
│   ├── flashplayer-plugin-28.0.0.161.xzm
│   ├── fw
│   │   ├── decorator-4.1.2-i586-1_slonly.xzm
│   │   ├── firewalld-0.4.4.5-i586-2_slonly.xzm
│   │   ├── python-six-1.11.0-i586-2.xzm
│   │   └── python-slip-0.6.5-i586-1_slonly.xzm
│   ├── palemoon_28.4.0+repack-1_i386.xzm 
│   └── rclone-v1.44-linux-386.xzm
├── office
│   ├── libreoffice-6.0.3.2-cs-help-language.xzm
│   ├── libreoffice-6.0.3.2-2.i586-ru-4.0.xzm
│   ├── texlive-extra-2017.170622-i586-2_slonly.xzm
│   ├── texlive-fonts-2017.170622-noarch-1_slonly.xzm
│   ├── texlive-2017.170622-i586-1_slonly.xzm
│   └── texstudio-2.12.6-i586-1_slonly.xzm
├── sound
│   ├── sound-theme-freedesktop_0.8-1_all.xzm
│   └── ubuntu-sounds_0.13_all.xzm
├── system
│   ├── gslapt-0.5.4c.xzm
│   ├── porteus-modules-manager-merge-1.0.xzm
│   └── 3168-slapt-get.xzm
└── utils
    ├── aha-0.4.10.6-i586-1_slonly.xzm
    ├── compiz-0.8.8-all.xzm
    ├── gbuildnum.xzm
    ├── giggle-0.5-i486-3sl.xzm 
    ├── gnome-genius_1.0.22.1_i386.xzm 
    ├── hostapd-2.5-i486-1salix.xzm
    ├── htop-2.0.1-i586-1.xzm
    ├── iw-4.3-i586-1.xzm
    ├── nano-2.6.0-i586-1.xzm
    ├── tree-1.7.0-i586-1.xzm
    └── vnstat-1.17-i586-1_slonly.xzm
Now, I was try connect 1TB HDD and eject in Caja is error free.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#8 by Ed_P » 22 Sep 2019, 20:47

tom2238 wrote:
22 Sep 2019, 08:11
Modules are same in normal and AF mode.
AF mode means running without added user modules.
tom2238 wrote:
22 Sep 2019, 08:11
Now, I was try connect 1TB HDD and eject in Caja is error free.
If you can now eject error free it implies your changes= cheatcode was the hang up. You'll have to save changes you want to keep using a different approach.
Ed

tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#9 by tom2238 » 23 Sep 2019, 06:35

In AF (base_only) it work without problem.
With all user modules without changes cheatcode - no problem.
Something is wrong in changes.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#10 by Ed_P » 23 Sep 2019, 18:54

Porteus saves all changes in RAM and they are lost when you reboot. Saving changes with the changes= cheatcode requires a mounted device and it remains mounted until you reboot.

If you read the /boot/docs/cheatcodes.txt you might find more options.

An option that I use that might solve your problem is to boot Porteus, create a save.dat file with the Porteus Save File Manager, reboot with a changes= option pointing to the save.dat file, make all your desired changes, and shutdown Porteus saving your changes to the save.dat file, then rename the save.dat file to save.dat.xzm, move the save.dat.xzm file to your modules folder, remove the changes= cheatcode and reboot. Your system is now customized, changes are no longer being saved and the drive can be unmounted. :good:
Ed

tom2238
Black ninja
Black ninja
Posts: 49
Joined: 15 Nov 2018, 14:52
Distribution: Porteus MATE v5.0 x86_64
Location: Czechia

Caja - Unmount USB stick failed

Post#11 by tom2238 » 02 Oct 2019, 15:40

So, if USB stick connected to /mnt/sdc1 and device is /dev/sdc1, working without problem. Maybe problem with udev config?

markwn
Ronin
Ronin
Posts: 2
Joined: 23 Dec 2019, 20:21
Distribution: ubuntu

Caja - Unmount USB stick failed

Post#12 by markwn » 22 Jan 2020, 19:10

How dangerous is this for a USB? I would leave it as it is.
Last edited by markwn on 11 Feb 2020, 20:48, edited 2 times in total.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Caja - Unmount USB stick failed

Post#13 by Ed_P » 22 Jan 2020, 22:16

If you are writing to a removable drive or have written to or deleted from a removable drive files removing the drive without safely removing it will result in the file or files being corrupted or the whole drive corrupted if the file allocation directory gets corrupted.

If the removable drive has no writing to or deleting from it it may not cause a problem removing it.
Ed

Post Reply