Hello again,
I had seen somewhere a comment about Ubuntu being "particular" about partitions, but tried to push the boundaries... Learning by mistake. Documentation is honestly great, it did really help a lot and there is not much at all that would warrant rework.
One thing that may be of interest: today, I configured another Pi5 (same setup as first one: 8GB, Argon One nvme, Crucial P3 Plus 500GB SSD,... but three different OS'es). When I experimented with the first Pi5, there was one failed attempt, which I did not think much about, where the partitions got completely corrupted on both the SD card that I used to format the SSD and on the SSD itself: on the SSD, Gparted showed the ext4 partitions for my three OS'es adjacent to one another, there was no boot partition at all, and there was a small partition of "unknown type". As for the SD card, on which I had PINN and several OS'es as well, it showed three very small partitions, but the ext4 partitions had all but disappeared. It is just as if the boot partitions had been installed on the SD card and the ext4 on the SSD.
The same happened as well today with the second Pi5: on the SSD with PINN on it, no boot partitions for my three OS'es, ext4 partitions next to one another and a small partition of "unknown type". The SD card partitions (SD card with PINN and three OS'es as well) also got corrupted. The common point between the two failures was an error message, when trying to install the OS'es from USB key, to the effect that "OS partitions could not be read". In both cases, in hindsight, I made the mistake of leaving the SD card on the Pi5 with PINN and three test OS'es on it while trying to install OS'es on the SSD drive with PINN on the SSD as well. Could it be that the OS installation script gets mixed up because of two instances of PINN, one on the SD card and one on the SSD? I should also mention (apart from the fact that it was a silly idea to leave the SD card, out of laziness to have to open the Argon One case to take it out) that I did a simple reboot and not a proper shutdown after copying PINN to the SSD.
Anyhow, just a minute inconvenience, and one that truly was the result of a silly idea, but I was just curious as to whether the fact that PINN was on both the SD card and on the SSD could have been the cause.
I had seen somewhere a comment about Ubuntu being "particular" about partitions, but tried to push the boundaries... Learning by mistake. Documentation is honestly great, it did really help a lot and there is not much at all that would warrant rework.
One thing that may be of interest: today, I configured another Pi5 (same setup as first one: 8GB, Argon One nvme, Crucial P3 Plus 500GB SSD,... but three different OS'es). When I experimented with the first Pi5, there was one failed attempt, which I did not think much about, where the partitions got completely corrupted on both the SD card that I used to format the SSD and on the SSD itself: on the SSD, Gparted showed the ext4 partitions for my three OS'es adjacent to one another, there was no boot partition at all, and there was a small partition of "unknown type". As for the SD card, on which I had PINN and several OS'es as well, it showed three very small partitions, but the ext4 partitions had all but disappeared. It is just as if the boot partitions had been installed on the SD card and the ext4 on the SSD.
The same happened as well today with the second Pi5: on the SSD with PINN on it, no boot partitions for my three OS'es, ext4 partitions next to one another and a small partition of "unknown type". The SD card partitions (SD card with PINN and three OS'es as well) also got corrupted. The common point between the two failures was an error message, when trying to install the OS'es from USB key, to the effect that "OS partitions could not be read". In both cases, in hindsight, I made the mistake of leaving the SD card on the Pi5 with PINN and three test OS'es on it while trying to install OS'es on the SSD drive with PINN on the SSD as well. Could it be that the OS installation script gets mixed up because of two instances of PINN, one on the SD card and one on the SSD? I should also mention (apart from the fact that it was a silly idea to leave the SD card, out of laziness to have to open the Argon One case to take it out) that I did a simple reboot and not a proper shutdown after copying PINN to the SSD.
Anyhow, just a minute inconvenience, and one that truly was the result of a silly idea, but I was just curious as to whether the fact that PINN was on both the SD card and on the SSD could have been the cause.
Statistics: Posted by ph_remy — Thu May 09, 2024 10:09 pm