Kernel version | uname --all Linux homeassistant 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
Architecture | dpkg --print-architecture arm64
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3) RPi 4 Model B (aarch64)
Power supply used | (EG: 5V 1A RAVpower) Official Pi power supply
SD card used | (EG: SanDisk ultra) Kingston A400 SSD Internal Solid State Drive 2.5" SATA Rev 3.0, 240GB - SA400S37/240G
Additional Information (if applicable)
Software title | (EG: Nextcloud) dietpi-drive_manager
Was the software title installed freshly or updated/migrated? n/a
Can this issue be replicated on a fresh installation of DietPi? I don't have a spare Pi to try this.
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID 028db189-bc62-4a97-8efe-fb12245746ba
Steps to reproduce
run dietpi-drive_manager
Expected behaviour
I spect the app to run so I can mount a drive
Actual behaviour
grep: .fstab: No such file or directory
grep: .fstab: No such file or directory
grep: .fstab: No such file or directory
grep: .fstab: No such file or directory
/boot/dietpi/dietpi-drive_manager: line 155: .fstab: No such file or directory
[ INFO ] DietPi-Drive_Manager | Detecting drives, please wait...
df: /mnt/nfs_client: No such device
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda2 > /
/boot/dietpi/dietpi-drive_manager: line 274: .fstab: No such file or directory
[ INFO ] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/sda1 > /boot
/boot/dietpi/dietpi-drive_manager: line 274: .fstab: No such file or directory
[. ]mv: cannot stat '.fstab': No such file or directory
[FAILED] DietPi-Drive_Manager | mv .fstab /etc/fstab
[FAILED] DietPi-Drive_Manager | Unable to continue, DietPi-Drive_Manager will now terminate.
Extra details
I have successfully mounted a NAS drive (to backup diet to) in the past. No idea why this is happening.
I thought DietPi existed in lieu of Debian (I thought it was a minimal version of Debian).
I’ve never updated Debian since installing DietPi the very first time as I never realised I had to manage both. (DietPI and Debian).
I’m somewhat confused right now. Sorry for being super dumb here but how do I know when I need to update Debian and how do I do that without affecting DietPi?
…however, and this is embarrassing, I have just recheck all mu PIs (I have 2 local and 1 remote) that the Pi in question is actually on bookworm and that I copied the Version info from one of my local Pi’s by accident.
The correct output for echo $G_DISTRO_NAME $G_RASPBIAN is:
The good new is that I can easily update my ‘old’ local Pi from bullseye to bookworm (as I remember that blog post you linked and must have followed it correctly for the remote Pi and forgotten t do it for one of my local Pis).
The bad news is that the Debian Version isn’t the cause of my problem above.
As an aside*, I have just checked all my Pis for dietpi-drive_manager:
