Bug report submitted

Defo used ther ight image. SD card was working fine prior to updating with Bullseye. I don’t have another SD card at hand - will have to purchase one off that there internet.

Thanks for all your help (and patience with a Noob like me!) thus far. Greatly appreciated

Hmm might be related to old Bullseye image. Need to check this.

Thanks @Joulinar and @Jappe

I’ll keep an eye on the thread

Strange, here it works, though MOUNTPOINT works as well:

root@micha:~# lsblk -po NAME,LABEL,SIZE,TYPE,FSTYPE,MOUNTPOINTS
NAME             LABEL   SIZE TYPE FSTYPE MOUNTPOINTS
/dev/sda                 2.7T disk ext4   /mnt/sda
/dev/sdb                 1.8T disk ext4
/dev/mmcblk0           119.4G disk
├─/dev/mmcblk0p1         128M part vfat   /boot/firmware
└─/dev/mmcblk0p2       119.2G part ext4   /
root@micha:~# lsblk -po NAME,LABEL,SIZE,TYPE,FSTYPE,MOUNTPOINT
NAME             LABEL   SIZE TYPE FSTYPE MOUNTPOINT
/dev/sda                 2.7T disk ext4   /mnt/sda
/dev/sdb                 1.8T disk ext4
/dev/mmcblk0           119.4G disk
├─/dev/mmcblk0p1         128M part vfat   /boot/firmware
└─/dev/mmcblk0p2       119.2G part ext4   /

But this is a Trixie system, checking back on Bullseye:

root@VM-Bullseye:~# lsblk -po NAME,LABEL,SIZE,TYPE,FSTYPE,MOUNTPOINTS
lsblk: unknown column: MOUNTPOINTS
root@VM-Bullseye:~# lsblk -po NAME,LABEL,SIZE,TYPE,FSTYPE,MOUNTPOINT
NAME        LABEL SIZE TYPE FSTYPE MOUNTPOINT
/dev/sda            8G disk
└─/dev/sda1         8G part ext4   /

There is a difference between them:

root@micha:~# lsblk --help | grep MOUNTPOINT
   MOUNTPOINT  where the device is mounted
  MOUNTPOINTS  all locations where device is mounted

vs

root@VM-Bullseye:~# lsblk --help | grep MOUNTPOINT
  MOUNTPOINT  where the device is mounted

However, it is informational only anyway, so I’ll adjust it: v9.1 · MichaIng/DietPi@9e63b8a · GitHub

But, this is only shown when the detection of the setup partition fails in the first place. And on RPi this is just expected, since it has a trailing FAT partition, serving the same need.

Ah, actually I know now why it does not expand the root partition+filesystem: We use set -e, hence the script exists immediately on any failing command, which was lsblk here. Let me generate new Bullseye images now with this fixed.

Why are you actually using a Bullseye image, instead of a Bookworm one?

1 Like

OP is using some software not able to run in Bookworm according a different forum post.

Great that the issue has been identified.

Reason for me going from Buster to Bullseye was because I saw that some software isn’t yet supported in Bookworm, namely Sonaar, Radaar etc

Sonarr and Radarr are perfectly supported on Bookworm. The only unsupported ones are ownCloud and Domoticz: Debian Bookworm has been released – DietPi Blog
RPi Cam Web Interface has not been updated in years, natively cannot work with recent camera modules (camera module 3) and should probably not be used anymore in general.

Oh, no I feel very silly and stupid.

I clearly misread something. Will try the Bookworm image later :+1:

1 Like