Creating a bug report/issue
I had upgraded to 8.13.2 from 8.12.1 on my Odroid C1 octoprint system and the system failed to reboot afterwards and i had to reinstall the O/S from scratch, after which USB drives are no longer recognized in v8.13.1.
Required Information
-
DietPi version |
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=13
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’
G_LIVE_PATCH_STATUS[1]=‘not applicable’
-
Distro version | bullseye
-
Kernel version |
Linux Orange-Juice 5.15.89-meson #22.11.4 SMP Mon Jan 23 21:12:18 UTC 2023 armv7l GNU/Linux
-
SBC model | Odroid C1 (armv7l)
-
Power supply used | 5v 3A
-
SD card used | eMMC 16GB
Steps to reproduce
- I did a clean install of 8.13.2 and it does not recognize any USB thumb drives, not even the one that was used up until the upgrade from 8.12.1
- …
Expected behaviour
- …Clean install of O/S then the drive manager should see the USB thumb drives as drives to be used
Actual behaviour
- …the USB thumb drives are not recognized
Extra details
- …all the thumb drives are recognized outside of this device on a raspi 3B+ running dietpi 8.13.2
can you check following
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
and check for kernel error messages.
dmesg -l err,crit,alert,emerg
Do you have a backup that you can restore?
my USB drives are where I had my backups. and when I do a clean install of DietPi it automatically upgrades to latest version regardless of the version you start with. I did the C1 from a 7.x version.
I do not have another C1 to test against with 8.12.1… but I did have a C1+ which was still running v8.12.1 and it recognized the USB drive that the C1 would not under 8.13.2.
So i ran the upgrade to 8.13.2 on the C1+ and after install and reboot the C1+ would not post with the USB drive installed. i removed the USB drive and powered off the C1+ and then upon boot it loaded just fine. inside Dietpi i went to the drive manager and then installed the USB drive and it was NOT found at all.
so from the C1+ it does the same as the C1.
the lsblk on the C1+ with a 64GB USB drive attached showed:
NAME FSTYPE LABEL SIZE RO TYPE MOUNTPOINT PARTUUID UUID
mmcblk0 14.8G 0 disk
├─mmcblk0p1 vfat BOOT 200M 0 part /boot 8a91de21-01 DBE9-EB9D
└─mmcblk0p2 ext4 14.6G 0 part / 8a91de21-02 5641e2e0-dda0-4966-bac6-219e59a2cb67
the dmesg you asked for showed no response.
also, i have Odroid C2s that have not been upgraded yet and are still at 8.12.1 so I can try one of those as well to see if it is a C1 issue or an odroid issue.
have a look to the apt packages that might be installed along with our DietPi update
apt update
apt list --upgradable
Maybe there is a kernel update that makes USB drives unusable.
You could execute apt upgrade manually, to see how it behaves. I doubt our DietPi update will have any influence. I guess it’s an apt package.
well nothing exciting here
root@Odroid-C1plus:~# apt update
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
Hit:3 https://mirrors.aliyun.com/armbian bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@Odroid-C1plus:~# apt list --upgradable
Listing... Done
you need to check on a system where it is working still and not on the one where USB is not working anymore.
my bad, sorry. i misread. ok, i can try it on a C2. Not sure it’ll be an even test.
I have no idea how to put a lower version of DietPi on to the C1 or C1+ for retesting.
seeing as the install from any version autoupgrades to latest. can i just instqall 8.12.1 somehow?
ok. Odroid C2 running 8.12.1 sees the USB drive just fine. but I don’t know if it will suffer from the failure until after upgrade is done. it could be a C1/C1+ issue.
did the apt update and it says 9 packages are available and those are :
armbian-firmware/bullseye,bullseye 22.11.4 all [upgradable from: 22.11.2]
containerd.io/bullseye 1.6.16-1 arm64 [upgradable from: 1.6.14-1]
curl/stable-security 7.74.0-1.3+deb11u5 arm64 [upgradable from: 7.74.0-1.3+deb11u3]
docker-ce-cli/bullseye 5:23.0.0-1~debian.11~bullseye arm64 [upgradable from: 5:20.10.22~3-0~debian-bullseye]
docker-ce/bullseye 5:23.0.0-1~debian.11~bullseye arm64 [upgradable from: 5:20.10.22~3-0~debian-bullseye]
libcurl4/stable-security 7.74.0-1.3+deb11u5 arm64 [upgradable from: 7.74.0-1.3+deb11u3]
linux-u-boot-odroidc2-current/bullseye 22.11.4 arm64 [upgradable from: 22.11.1]
sudo/stable-security 1.9.5p2-3+deb11u1 arm64 [upgradable from: 1.9.5p2-3]
webmin/stable 2.013 all [upgradable from: 2.010]
did an apt upgrade without issue.
now, do I do the dietpi-update to 8.13.2 or should I try something else first?
to avoid a misunderstanding. The DietPi version has nothing to do with kernel version or apt package version.
pls reboot your system first
did the reboot, but right before that I took a peek in the drive manager and it did see the USB drive on the C2.
after the reboot I looked in drive manager and the USB drive is still there. I don’t know what that tells us, if it’s a C1 issue only or what?
if possible, do a backup of the C2 to local storage (not USB) and update to DietPi v8.13. Reboot afterwards. I guess you will see your USB drive still.
not worried about the backup, the C2 was a spare that’s why it had not been upgraded yet.
so I did a dietpi-update and it still sees the USB drive.
is there a way to do an install to the C1/C1+ that is NOT the latest, like stop the upgrade process at a designated point?
but I may have something. I think i found a C1 saved installed image from december. I will try that and see what it does.
you could boot without network connected. But it would require a local console access.
Still I guess it’s not the DietPi version. Probably kernel or u-boot.
well I figured installing the older version of dietpi would have the older kernel…without the latest apt changes. lets see what this image I have from december shows us. i can at least hopefully get a list of the apts being upgraded.
there is no direct relation between DietPi version, kernel and apt package version.
I now have the C1+ with a working version of dietpi 8.11.2 on it. and it DOES see the USB drive.
so we have the working kernel here. if I am not mistaken.
i did the apt update and there are 10 packages to be upgraded. they are:
root@Odroid-C1:~# apt list --upgradable
Listing... Done
armbian-firmware/bullseye,bullseye 22.11.4 all [upgradable from: 22.08.6]
base-files/stable 11.1+deb11u6 armhf [upgradable from: 11.1+deb11u5]
curl/stable-security 7.74.0-1.3+deb11u5 armhf [upgradable from: 7.74.0-1.3+deb11u3]
libcurl4/stable-security 7.74.0-1.3+deb11u5 armhf [upgradable from: 7.74.0-1.3+deb11u3]
libksba8/stable-security 1.5.0-3+deb11u2 armhf [upgradable from: 1.5.0-3+deb11u1]
libtasn1-6/stable 4.16.0-2+deb11u1 armhf [upgradable from: 4.16.0-2]
linux-dtb-current-meson/bullseye 22.11.4 armhf [upgradable from: 22.08.6]
linux-image-current-meson/bullseye 22.11.4 armhf [upgradable from: 22.08.6]
nano/stable 5.4-2+deb11u2 armhf [upgradable from: 5.4-2+deb11u1]
sudo/stable-security 1.9.5p2-3+deb11u1 armhf [upgradable from: 1.9.5p2-3]
if possible, do a copy / backup if this system. Just to be able to test again. Once backup finished, upgrade all apt packages and reboot your system.
ok. this current system is from a backup image I just flashed to the drive. I can reflash from that image again if needed. so I can upgrade without another backup.
1 Like