Yes I did. Started with a totally blank drive on both… Used RPI-imager on both drives.
Pulled a drive from my PI-400 and checked the partition ids, they were the same as my other drives. Maybe the root cause is RPI-Imager.
I think I will grab another drive and do a flash of dietpi using balena etcher(on my x64 pc running Mint Linux) to see what ids the new partitions end up with.
Will get back to you with the results. Possibly RPI-Imager is having problems with bookworm.
Looks like RPI-Imager is having problems with bookworm since it seems to be using one set of partitions ids for any flashes.
Did the flash using BalenaEtcher on my pc and when I plugged the drive into this machine it automounted and was listed in Nemo as expected.
Guess I will have to find a better flash tool to replace RPI_Imager.
Thank you for your help. Would never have found the root problem without your help.
Personally I’m using Rufus to flash the image. Anyway it is possible to manually change drive IDs if needed
Agreed, should not be required from doing a simple iso flash from a program that is supposed to be top of the line.
Thanks on the program suggestion. Will have to check it out.
If I’m not mistaken, drive ID’s are already included into the image. Means, flashing the very same image will end up with same ID’s in that drive.
Well, when I flashed the exact same iso using balena etcher it came out with totally different ids.
Plus in the past I have flashed the same iso using RPI-Imager to set up new machines with dietpi and was able to bring the new sdrs to let me copy files to the new drive. In fact I checked 2 machine I have that are still running the bullseye version of dietpi and they have ditterent ids on each machine. Both were flashed on the same machine and I remember that I was able to access both drives on the same machine for purposes of copying some files to the new drives.