Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
So I tried creating an image on a USB stick (an 8Gb Kingston one) and
that works perfectly OK.
I've compared the contents of the USB stick and the USB drive and they
look identical, they both mount without problems on the Pi when it's
running from its SD card.
When I try and boot from the USB disk I get the error code for "Kernel
image not found".
The only thing I can think may be happening is that the eeprom boot
code isn't as 'clever' as the normal disk mounting code in the OS and,
thus, for some reason can't mount and read from the USB disk but can
mount and read the USB stick.
However I'm a bit stuck now, I don't really want to go and buy another
USB disk and find that doesn't work either.
On 15/12/2021 15:27, Chris Green wrote:
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
So I tried creating an image on a USB stick (an 8Gb Kingston one) and
that works perfectly OK.
I've compared the contents of the USB stick and the USB drive and they
look identical, they both mount without problems on the Pi when it's running from its SD card.
When I try and boot from the USB disk I get the error code for "Kernel image not found".
The only thing I can think may be happening is that the eeprom boot
code isn't as 'clever' as the normal disk mounting code in the OS and, thus, for some reason can't mount and read from the USB disk but can
mount and read the USB stick.
However I'm a bit stuck now, I don't really want to go and buy another
USB disk and find that doesn't work either.
How is the 500GB drive partitioned? And what format are its partitions?
You need a small boot partition in FAT32 format and the rest can be an EXT4.
You should then be able to rsync /boot from a working SD card to the
boot partition and copy the rest of the card to the much larger ext4 partition using rsync etc.
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 15/12/2021 15:27, Chris Green wrote:It was created directly by copying the Pi distribution image to it,
Well now I'm really stumped.How is the 500GB drive partitioned? And what format are its partitions?
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
So I tried creating an image on a USB stick (an 8Gb Kingston one) and
that works perfectly OK.
I've compared the contents of the USB stick and the USB drive and they
look identical, they both mount without problems on the Pi when it's
running from its SD card.
When I try and boot from the USB disk I get the error code for "Kernel
image not found".
The only thing I can think may be happening is that the eeprom boot
code isn't as 'clever' as the normal disk mounting code in the OS and,
thus, for some reason can't mount and read from the USB disk but can
mount and read the USB stick.
However I'm a bit stuck now, I don't really want to go and buy another
USB disk and find that doesn't work either.
You need a small boot partition in FAT32 format and the rest can be an EXT4. >>
that creates it as above. I tried with dd directly and using
rpi-imager, they both produced the same as far as I can see.
You should then be able to rsync /boot from a working SD card to theIf I could get a brand new built by the default "how to make a Pi"
boot partition and copy the rest of the card to the much larger ext4
partition using rsync etc.
process to work first then I might try the above to get 'my' files on
it but at the moment I can't even get a pristine new Raspberry Pi
image to boot.
On 15/12/2021 15:27, Chris Green wrote:
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
I'm rather ignorant of Linux OS config. Why would you want to move the
boot off SD. Move your apps off the SD, sure, it is quite nice to have a separation between apps and OS. Apps often do a lot of disk IO.
I've always assumed the OS itself doesn't do a bunch of writing to the
SD card. No swapping, maybe a few logfiles. (note to self) I should check.
The apps themselves can be in docker containers and hence the OS needs
very little config, The SD can easily be swapped in case of disaster.
You can script up provisioning if you are really keen, or just have a
git repo, with all the key files.
Pancho <Pancho.Dontmaileme@outlook.com> wrote:
On 15/12/2021 15:27, Chris Green wrote:
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
I'm rather ignorant of Linux OS config. Why would you want to move the
boot off SD. Move your apps off the SD, sure, it is quite nice to have a
separation between apps and OS. Apps often do a lot of disk IO.
I've always assumed the OS itself doesn't do a bunch of writing to the
SD card. No swapping, maybe a few logfiles. (note to self) I should check. >>
The apps themselves can be in docker containers and hence the OS needs
very little config, The SD can easily be swapped in case of disaster.
You can script up provisioning if you are really keen, or just have a
git repo, with all the key files.
Yes, I could just boot off the SD /boot partition and then have
everything on the spinning disk but that's a much messier (and
actually more difficult to configure) way than just 'boot off the USB'.
If the boot off the USB worked (well, it does from the stick) then
it's just a matter of removing the SD card and putting a USB drive
with the system image on it into the Pi and it "just works". Which it
does with a USB stick, but not with a drive.
Add rootdelay=5 to cmdline.txt on /boot partitions if it is not already there. This allows the HD time to spin up. Flash devices respond quick
enough but physical drives need time to become active. $0.02
On Wed, 15 Dec 2021 17:29:51 +0000
Chris Green <cl@isbd.net> wrote:
Pancho <Pancho.Dontmaileme@outlook.com> wrote:
On 15/12/2021 15:27, Chris Green wrote:
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
I'm rather ignorant of Linux OS config. Why would you want to move the
boot off SD. Move your apps off the SD, sure, it is quite nice to have a >> separation between apps and OS. Apps often do a lot of disk IO.
I've always assumed the OS itself doesn't do a bunch of writing to the
SD card. No swapping, maybe a few logfiles. (note to self) I should check. >>
The apps themselves can be in docker containers and hence the OS needs
very little config, The SD can easily be swapped in case of disaster.
You can script up provisioning if you are really keen, or just have a
git repo, with all the key files.
Yes, I could just boot off the SD /boot partition and then have
everything on the spinning disk but that's a much messier (and
actually more difficult to configure) way than just 'boot off the USB'.
If the boot off the USB worked (well, it does from the stick) then
it's just a matter of removing the SD card and putting a USB drive
with the system image on it into the Pi and it "just works". Which it
does with a USB stick, but not with a drive.
Just as a matter of interest have you tried it with an SSD drive?
Well now I'm really stumped.
I'm trying to get my Pi 4 to boot from a (fairly small, 500Gb) hard
disk. I've tried creating the image various ways (dd on Linux,
rpi-imager, etc.) and nothing worked.
So I tried creating an image on a USB stick (an 8Gb Kingston one) and
that works perfectly OK.
I've compared the contents of the USB stick and the USB drive and they
look identical, they both mount without problems on the Pi when it's
running from its SD card.
When I try and boot from the USB disk I get the error code for "Kernel
image not found".
The only thing I can think may be happening is that the eeprom boot
code isn't as 'clever' as the normal disk mounting code in the OS and,
thus, for some reason can't mount and read from the USB disk but can
mount and read the USB stick.
However I'm a bit stuck now, I don't really want to go and buy another
USB disk and find that doesn't work either.
Power the HD using external power. Power up the rpi a few seconds after starting the drive. Does that work? I boot from SD with root on the USB
HD so I needed the rootdelay to give the HD time to be ready.
The Natural Philosopher <tnp@invalid.invalid> wrote:
How is the 500GB drive partitioned? And what format are its partitions?It was created directly by copying the Pi distribution image to it,
You need a small boot partition in FAT32 format and the rest can be an EXT4. >>
that creates it as above. I tried with dd directly and using
rpi-imager, they both produced the same as far as I can see.
Connecting through a USB hub makes it work but that's only USB 2.
On Wed, 15 Dec 2021 19:07:08 +0000, Chris Green <cl@isbd.net> declaimed the following:
Connecting through a USB hub makes it work but that's only USB 2.
USB-3 hubs are available... The trick is to find one that doesn't revert all ports to the slowest device connected.
Chris Green <cl@isbd.net> wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:
How is the 500GB drive partitioned? And what format are its partitions?It was created directly by copying the Pi distribution image to it,
You need a small boot partition in FAT32 format and the rest can be an EXT4.
that creates it as above. I tried with dd directly and using
rpi-imager, they both produced the same as far as I can see.
Did you update /etc/fstab and whatever disk configuration bits are in /boot? The Raspberry Pi's SD card slot is /dev/mmcblk0, but a hard drive connected over USB will be /dev/sda. Without the appropriate updates, the kernel
won't find the root filesystem and will hang.
| Sysop: | Rempala |
|---|---|
| Location: | Richlands, NC |
| Users: | 106 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 41:10:20 |
| Calls: | 205 |
| Files: | 6 |
| Messages: | 111,123 |