Cinnamon Desktop Nemo file manager not auto-mounting usb ssd on startup

Gale · July 25, 2023, 6:50pm

Creating a bug report/issue

Required Information

DietPi version | Lastest Bookworm version
Distro version | `
Kernel version |
Architecture | dpkg --print-architecture
SBC model | RPI-4B
Power supply used | (EG: 5V 1A RAVpower)
SD card used | Kingston SSD in usb case

Additional Information (if applicable)

Software title | Nemo
This was a fresh install starting with the latest Bookworm Dietpi iso
Also I am using a powered usb hub to ensure that there are no power problems with using the usb ssd.
Another note, Gparted sees the external drive just fine.
Bug report ID | echo $G_HW_UUID

Steps to reproduce

…Plug in a flash drive or USB SSD
…It will not appear in Nemo file listings

Expected behaviour

…Per the Nemo config setup it should automout the drive and show it in the file list.

Actual behaviour

…No automount, not in file list

Extra details

…This problem seems to have started with Bookworm as I have the same setup using Bullseye version of deitpi and it works as expected

Jappe · July 26, 2023, 5:47am

But the drive is mountable at all?
Can you show pls cat /etc/fstab.

WarHawk · July 26, 2023, 7:21am

is this right?

5V 1A RAVpower

Gale · July 26, 2023, 1:15pm

No itn is not. As this is the same Raspberry PI 4B I am running the earlier version of Dietpi and Cinnamon Desktop I did not bother to list every thing. It is
a standard power cube for the 4B.

Joulinar · July 26, 2023, 1:27pm

DietPi themself don’t have any auto mount feature for drives. Means you need to mount them via drive manager and not just plug in. If there was a feature to auto mount USB drives in Cinnamon, it was a Cinnamon feature. Probably something that would need to be reported there.

Gale · July 26, 2023, 1:28pm

Using dietpi driver manager it can be mounted and does show in fstab. Using the bullseye version (on another usb ssd) I used RPI Imager to install the bookworm version od dietpi on this ssd. I actually swapped the drives out and the new drive booted just fine. It is only after I had finished the cinnamon install and was going to copy some files over from the “old” drive that I found that nemo would not autoboot the drive. I mounted the drive using dietpi drive manager and nemo still did not see it. I was able to access the drive in a terminal session using standard commands.

Joulinar · July 26, 2023, 2:19pm

But this would be out of DietPi scope. We don’t manage nemo app. If you are able to see it on terminal, it should be visible on other desktop apps as well.

Gale · July 26, 2023, 3:28pm

I would think the same but was wondering why it just appeared when I tried the bookworm version of dietpi.
One other thing I just thought about was I mounted the drive using dietpi driver manager it appeared fstab as a temporary listing. I will try to see if I can make it a permanent mount that will survive a reboot. I will let you knwo what I see.

Joulinar · July 26, 2023, 3:42pm

using drive manager will create a permanent entry within /etc/fstab and should be available still after reboot. Keep in mind, we setup drives in a way, they did not get mounted on reboot directly. They will become available as soon as you access them.

Gale · July 26, 2023, 3:46pm

OK, kere is my fstab listing after mounting the drive after mounting it using dietpi driver manager and then rebooting the system.

#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
PARTUUID=0b153577-02 / ext4 noatime,lazytime,rw 0 1
PARTUUID=0b153577-01 /boot vfat noatime,lazytime,rw 0 2
UUID=076d28bd-d8f2-47da-8e22-28b4493b8787 /mnt/sdd2 ext4 noatime,lazytime,rw,nofail,noauto,x-systemd.automount
UUID=D33A-B557 /mnt/sdd1 vfat noatime,lazytime,rw,nofail,noauto,x-systemd.automount

As I do not normally look and or edit fstab maybe you can let me know what some these options listed for sdd1 and sdd2 mean as I don’t see them in my system drive listings.

Joulinar · July 26, 2023, 3:59pm

Both /mnt/sdd1 and /mnt/sdd2 will become available as soon as you access them. Just try following on CLI

reboot
df -h
cd /mnt/sdd1
cd /mnt/sdd2
df -h

Gale · July 26, 2023, 4:12pm

My other question is what the noauto option means as I do not see it in the system drive listings.

And after I did a reboot, the drive wa available from the command line and gparted showed the drive as mounted. In fact I unmounter the drive using driver manager the rebooted. Gparted still showed the drive (sdd) but not mounted as one would expect.

I will now try the commands you listed and see what happens.

The cd commands worked normally and I was able to ls the drives.
But df did not show the drives either before or after running the cd commands.

Gale · July 26, 2023, 4:29pm

Forgot ntomdo the reboot after unmounting the drives. Did the reboot and brought driver manager up again to remount the drives and saw the following:

Pi 4 Model B (aarch64) | IP: 192.168.1.60────────────┤ DietPi-Drive_Manager ├───────────────────────────────────────────────┐
      │ Please select a drive to see available options.                                                                      │ 
      │  - User data location: RootFS (/mnt/dietpi_userdata)                                                                 │ 
      │                                                                                                                      │ 
      │                                                     ●─ sda ──────────────────────────────────────────────●           │ 
      │           /                                         : /dev/sda2 | ext4 | Capacity: 58.5G | Used: 5.5G (9%)           │ 
      │           /mnt/D33A-B557                            : /dev/sda1 | vfat | Not mounted                                 │ 
      │                                                     ●─ sdb ──────────────────────────────────────────────●           │ 
      │           /boot                                     : /dev/sdb1 | vfat | Capacity: 127M | Used: 32M (25%)            │ 
      │           /mnt/076d28bd-d8f2-47da-8e22-28b4493b8787 : /dev/sdb2 | ext4 | Not mounted                                 │ 
      │                                                     ●─ sdc ──────────────────────────────────────────────●           │ 
      │           /tmp/sdc                                  : /dev/sdc | No filesystem / format required                     │ 
      │                                                     ●─ sdd ──────────────────────────────────────────────●           │ 
      │           /tmp/sdd                                  : /dev/sdd | No filesystem / format required                     │ 
      │                                                     ●─ Global Options ───────────────────────────────────●           │ 
      │           Idle Spindown                             : Set a global idle duration, before drives power down           │ 
      │                                                     ●─ Add / Refresh Drives ─────────────────────────────●           │ 
      │           Add network drive                         : Select to mount networked drives                               │ 
      │           Refresh                                   : Scan for recently added/removed drives                         │ 
      │                                                                                                                      │ 
      │                                                                                                                      │ 
      │                                  <Ok>                                      <Exit>                                    │ 
      │

Not sure whatbis going on but the partitions seem to listed with the wrong ids,
/dev/sda1 shows as what should be sdb1 (per gparted) and vice-versa)

Joulinar · July 26, 2023, 4:29pm

You unmount the drives before reboot?

usually it should be

mounting the drives using drive manager
this will create entries within /etc/fstab
entries should survive a reboot
USB drives will not be mounted on reboot directly
USB drives will be mounted automatically as soon as someone or something is going to access the mount point

Gale · July 26, 2023, 4:32pm

No I was just tryng to see what was going on so I unmounted the drives and rebooted to start from a know good point. And then I saw the problem I just showed you.

Actulally I have always seen the usb drives automounting if they were plugged in prior to the boot up or immediatly if plugged in after the system was up and running. And this is exactly how things worked untill I decided to do a fresh install and configuration with the new bookworm version of dietpi. I decided to do a fresh install as in the blog it was stated the there might be problems trying to use the update script to do the update from bullseye to bookworm.

Joulinar · July 26, 2023, 4:35pm

keep Gparted away for time being. Way better to check in system level directly using:

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid

Important are drive IDs and not the name sba or sdb

Gale · July 26, 2023, 4:39pm

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
NAME   FSTYPE LABEL   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
sda                  59.6G  0 disk                                                 
├─sda1 vfat           128M  0 part            0b153577-01                          D33A-B557
└─sda2 ext4          59.5G  0 part /          0b153577-02                          076d28bd-d8f2-47da-8e22-28b4493b8787
sdb                 111.8G  0 disk                                                 
├─sdb1 vfat           128M  0 part /boot      0b153577-01                          D33A-B557
└─sdb2 ext4         111.7G  0 part            0b153577-02                          076d28bd-d8f2-47da-8e22-28b4493b8787
sdc                     0B  0 disk                                                 
sdd                     0B  0 disk

Even stranger…

fstab shows:

#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
PARTUUID=0b153577-02 / ext4 noatime,lazytime,rw 0 1
PARTUUID=0b153577-01 /boot vfat noatime,lazytime,rw 0 2

Joulinar · July 26, 2023, 4:51pm

Both drives have the very same id and partitions. Did you cloned them?

Gale · July 26, 2023, 4:57pm

No.
Since I was setting the new drive up as a replacement for my previous system drive I did the full setup and configuration of Cinnamon exactly the same way so the partition layout is exactly same on both drives.

And here is what a plain lsblk shows:

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0  59.6G  0 disk 
├─sda1   8:1    0   128M  0 part 
└─sda2   8:2    0  59.5G  0 part /
sdb      8:16   0 111.8G  0 disk 
├─sdb1   8:17   0   128M  0 part 
└─sdb2   8:18   0 111.7G  0 part 
sdc      8:32   1     0B  0 disk 
sdd      8:48   1     0B  0 disk

Joulinar · July 26, 2023, 5:20pm

You need to show IDs as well as this is the important part and they need to be different. Otherwise you will have issues to distinguish between them.

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid

Did you flashed a DietPi image to both drives?