Dietpi-drive_manager not starting anymore

so i shut down my dietpi server for a week due to a holiday trip.

today i started it again, and everything works. only issue is that i am not able to start the driver-manager in the dietpi launcher.

i only get following info:

[ INFO ] DietPi-Drive_Manager | Detecting drives, please wait...

after that nothing happens.

my *arr installs works fine and can access the drive and move/copy files between each other.

apt-upgrade and reboot did not help

can you share following!

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
cat /etc/fstab
root@DietPi:~# lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid

sda                14.9G  0 disk
│    vfat            64M  0 part /boot/efi  53c2e147-54fb-4234-a22a-4166b14c441b 6C24-B64B
     ext4          14.9G  0 part /          36f052d4-20f8-48ae-be37-6515ac16d8cf a924186e-3cd7-45a3-b001-6a57afed8572
sdb               223.6G  0 disk
     ext4         223.5G  0 part /mnt/c5ef1 63262f45-dc88-4351-bbfd-017f42e15c9c c5ef1ad4-f767-41c0-b301-5885583d5b25
sdc                 4.5T  0 disk
     ext4           4.5T  0 part /mnt/0e3a3 4bb8956e-ccd9-4949-af33-f360bd9ae3ea 0e3a3bb8-e8fe-4216-ba2c-178f467977c1
sdd                 1.8T  0 disk
     exfat  2TB-Seagate
                    1.8T  0 part /mnt/63A8- b69827b3-01                          63A8-D4C3
root@DietPi:~# cat /etc/fstab
# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.

tmpfs /tmp tmpfs size=3863M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid,mode=1777

# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume


UUID=a924186e-3cd7-45a3-b001-6a57afed8572 / ext4 noatime,lazytime,rw 0 1
UUID=6C24-B64B /boot/efi vfat noatime,lazytime,rw 0 2
UUID=0e3a3bb8-e8fe-4216-ba2c-178f467977c1 /mnt/0e3a3bb8-e8fe-4216-ba2c-178f467977c1 ext4 noatime,lazytime,rw,nofail,noauto,x-systemd.automount
UUID=c5ef1ad4-f767-41c0-b301-5885583d5b25 /mnt/c5ef1ad4-f767-41c0-b301-5885583d5b25 ext4 noatime,lazytime,rw,nofail,noauto,x-systemd.automount
UUID=63A8-D4C3 /mnt/63A8-D4C3 exfat noatime,lazytime,rw,gid=dietpi,fmask=0002,dmask=0002,nofail,noauto,x-systemd.automount
UUID=63C5-3E59 /mnt/63C5-3E59 exfat noatime,lazytime,rw,gid=dietpi,fmask=0002,dmask=0002,nofail,noauto,x-systemd.automount

If i wait ages i get after drive manager start that:

[ INFO ] DietPi-Drive_Manager | Detecting drives, please wait...
df: /mnt/63C5-3E59: No such device
[ INFO ] DietPi-Drive_Manager |  - Detected mounted physical drive: /dev/sda2 > /

yes correct, this drive is missing. You have specified four different drives in your /etc/fstab. But three are available only.

i unmount this drive before i unplugged it (in the drive manager), and never plugged it back in.

did i do something wrong? How can i fix this now?

I thought:

  1. if i savely unmount the drive /mnt/63C5-3E59, than it would not cause any issues in the future. i do NOT have the drive anymore, since i gave it away.

can i somehow manually kill the entry in the fstab? or set stuff on default?

  1. how should i handle this in the future? since unmount, before unplug seems to be not enough.

  2. i noticed now, that this also fucks up my whole samba shares. since i added /mnt/ into samba shares, and now its not working for access in KODI and others.

Usually drive manager can be used to remove drives as this should create a new fstab file without the drive configured. For now, simply remove the entry from fstab and restart your system.

Ok I will try to google how to do that.

no need to use google

nano /etc/fstab

go to the line in question and remove it. Save your file and you are done.

thanks i found this as well. and it worked. now the drive manager starts normal