An error occurred while accessing 'MANJARO_KDEM_2405', the system responded: The requested operation
has failed: Error mounting /dev/sdc1 at /run/media/tracy/MANJARO_KDEM_2405: Filesystem type iso9660 not configured in kernel.
Currently using Kernel 6.6
Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.6.41-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU N3540 @ 2.16GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics
Manufacturer: Notebook
Product Name: W54_W94_W955TU,-T,-C
Rebooted to Kernel 6.1 and the USB Flash Drive mounts.
Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.1.103-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU N3540 @ 2.16GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics
Manufacturer: Notebook
Product Name: W54_W94_W955TU,-T,-C
I’ve been using Kernel 6.6 for several Months,and this is the first time I’ve noticed an issue.
The kernel is prebuilt with support for iso9660. It could be a mismatch between the kernel and the modules.
Try switching mirror to https://mirror.easyname.at/manjaro - the mirror is known to be a fully up-to-date mirror. (this is temporary, in the sense it will not change your existing mirror pool custom or not)
sudo pacman-mirrors -aU https://mirror.easyname.at/manjaro
Then run a full system sync.
sudo pacman -Syu
3 Likes
tracy@daphne ~]$ sudo pacman-mirrors -aU https://mirror.easyname.at/manjaro
[sudo] password for tracy:
::INFO Writing mirror list
::BUILDMIRROR : https://mirror.easyname.at/manjaro/stable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
[tracy@daphne ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra 7.8 MiB 192 KiB/s 00:41 [##############################################################] 100%
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: nano-syntax-highlighting: local (2020.10.10+10+g1aa64a8-2) is newer than extra (2020.10.10-2)
there is nothing to do
The only result is the above message… “there is nothing to do”
That is strange 
if you compare the output of
uname -r
And
pacman -Qe
You should get the same versions - e.g. for my system
$ pacman -Qe linux
linux610 6.10.3-6
$ uname -r
6.10.3-6-MANJARO
If you get the same results - I have no idea why - but you did mention USB Flash Drive - it may be due to the ISO filesystem being damaged or incomplete - but that is just a wild guess, I really don’t have any clues.
If there is an inconsistency in the output - one could suspect filesystem error - yeah - even with consistency it could be filesystem - my initial thought was btrfs - yet another guess.
This is due to a forgotten overlay package - either ignore or use -uu to downgrade to the repo package.
I’m current on 6.1,as I booted into 6.1 to see if there was a problem with the Flash Drive.
Here’s my current results…
[tracy@daphne ~]$ pacman -Qe | grep linux
linux515 5.15.164-1
linux61 6.1.103-1
linux66 6.6.44-1
util-linux 2.40.2-1
[tracy@daphne ~]$
[tracy@daphne ~]$ uname -r
6.1.103-1-MANJARO
[tracy@daphne ~]$
I’ll reboot into 6.6, and post that result.
I’m using EXT4
[tracy@daphne ~]$ pacman -Qe | grep linux
linux515 5.15.164-1
linux61 6.1.103-1
linux66 6.6.44-1
util-linux 2.40.2-1
[tracy@daphne ~]$ uname -r
6.6.44-1-MANJARO
[tracy@daphne ~]$
I found a similar issue from Oct. 2023 Iso9660 unable to mount - #11 by Yochanan
Perhaps it is as simple as modprobing the module?
sudo modprobe isofs
It’s working after I rebooted into 6.6, so maybe it was a module thing.
I created a new Flash drive with manjaro-kde-24.0.5-minimal-240730-linux69 on it
- if one syncs the system - and that sync contains a new kernel build e.g. 6.6.45 → 6.6.46 - then modules stop functioning until one restart the system.
I have been there countless times - especially when building iso - which makes heavy use of overlayfs.
2 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.