@Lolonois said in usb boot from 5tb hdd:
@korn16ftl3 Looks correct, except you are missing one hex-number in the product ID (should be :25ee and not :5ee).
The quiet parameter is double but it does not have an impact: The kernel parameters are parsed left to right and the last one wins, if there are two identical parameters.
My new question is since we are playing with the cmdline.txt, what are the other parameters that are there?
The kernel parameters are documented in the kernel documentation, in the raspberry pi documentation, and the kernel parameter of plymouth and info about plymouth itself are documented for example in the Arch wiki,
i made the previously mentioned changes to the cmdline.txt and am getting the same error readouts.
im starting to think/wonder if the GPT portion of thi is what is causing some of my problems as retropie its self if i understand correctly was written for MBR and everything boots just fine in MBR and GPT when everything is <2tb the second i convert the GPT partition manually (before initial retropie boot and partition resize) everything ceases toi load/boot.
im going to remove the
quiet init=/usr/lib/raspi-config/init_resize.sh
from the cmdline.txt since perhaps it is hanging on attempt to resize a partition that has already been resized for one and for two is GPT and not sure how to handle it.
lets see what that does i suppose.
also debating on wiping everything abd starting over using gparted and specifically raspberry pi os to try to set tis up as well maybe that ii yield different results.
will report back after a little bit of experimenting and a bit more research.
alternatively i have seen some things online that enable UEFI booting ( [https://www.linux.it/~ema/posts/secure-boot-rpi/](link url) , [https://github.com/pftf/RPi4](link url) ) would this be any help with trying to boot from >2TB partitions as UEFI booting supports it? would there be any drawbacks or risks to experimenting with these options?