I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
Now the question is "where do I need to change the UUID to match that of the new partition".
I know I need to change /etc/fstab, /boot/extlinux/extlinux.conf and perhaps /boot/grub/grub.conf, but do I also have to regenerate the initramfs images, and if so, what command would I use so they contain the correct UUID and drivers?
If I need to rebuild the initramfs, that would be a bit of a chicken and egg problem, because I would not be able to boot from the sata drive until I rebuilt it, but if I rebuilt it while running from the SD card, I'd guess the rebuilt initramfs would still reference the SD card.
Steve
Le ven. 7 juin 2019 à 17:24, Steven A. Falco stevenfalco@gmail.com a écrit :
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
Now the question is "where do I need to change the UUID to match that of the new partition".
I know I need to change /etc/fstab, /boot/extlinux/extlinux.conf and perhaps /boot/grub/grub.conf, but do I also have to regenerate the initramfs images, and if so, what command would I use so they contain the correct UUID and drivers?
Hello,
You do not need to regen the initramfs for the UUID, but more to have the appropriate sata driver (unless you already have a generic initramfs, which is not the default IIRC).
Unless you really want to re-use an existing installation, I would recommend to xzcat the image you want on sata from another host. You only need to have the bootloader on the mmc for the wanboard, (modern) u-boot can boot to sata directly even for /boot.
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
Now the question is "where do I need to change the UUID to match that of the new partition".
I know I need to change /etc/fstab, /boot/extlinux/extlinux.conf and perhaps /boot/grub/grub.conf, but do I also have to regenerate the initramfs images, and if so, what command would I use so they contain the correct UUID and drivers?
If I need to rebuild the initramfs, that would be a bit of a chicken and egg problem, because I would not be able to boot from the sata drive until I rebuilt it, but if I rebuilt it while running from the SD card, I'd guess the rebuilt initramfs would still reference the SD card.
Steve
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On 6/7/19 2:26 PM, Peter Robinson wrote:
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Steve
On Fri, Jun 7, 2019 at 7:28 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:26 PM, Peter Robinson wrote:
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Sort of. The pre generated images that we ship have "generic" initramfs which have a LOT of drivers so the images will boot on the vast majority of Arm devices, once the first kernel update is applied it automatically moves to a host specific initramfs so will then be a lot smaller, and hence much quicker to boot, but will not be a generic initramfs.
Peter
On 6/7/19 2:32 PM, Peter Robinson wrote:
On Fri, Jun 7, 2019 at 7:28 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:26 PM, Peter Robinson wrote:
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Sort of. The pre generated images that we ship have "generic" initramfs which have a LOT of drivers so the images will boot on the vast majority of Arm devices, once the first kernel update is applied it automatically moves to a host specific initramfs so will then be a lot smaller, and hence much quicker to boot, but will not be a generic initramfs.
Excellent! That is a good design.
Steve
On 6/7/19 2:38 PM, Steven A. Falco wrote:
On 6/7/19 2:32 PM, Peter Robinson wrote:
On Fri, Jun 7, 2019 at 7:28 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:26 PM, Peter Robinson wrote:
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Sort of. The pre generated images that we ship have "generic" initramfs which have a LOT of drivers so the images will boot on the vast majority of Arm devices, once the first kernel update is applied it automatically moves to a host specific initramfs so will then be a lot smaller, and hence much quicker to boot, but will not be a generic initramfs.
Excellent! That is a good design.
I am happy to report that it worked perfectly. My Wandboard is now running entirely from a SATA drive, with the tiny exception of U-Boot.
Steve
On Fri, Jun 7, 2019 at 10:58 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:38 PM, Steven A. Falco wrote:
On 6/7/19 2:32 PM, Peter Robinson wrote:
On Fri, Jun 7, 2019 at 7:28 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:26 PM, Peter Robinson wrote:
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Sort of. The pre generated images that we ship have "generic" initramfs which have a LOT of drivers so the images will boot on the vast majority of Arm devices, once the first kernel update is applied it automatically moves to a host specific initramfs so will then be a lot smaller, and hence much quicker to boot, but will not be a generic initramfs.
Excellent! That is a good design.
I am happy to report that it worked perfectly. My Wandboard is now running entirely from a SATA drive, with the tiny exception of U-Boot.
Excellent news, feel free to suggest any improvements that could be done to improve the process.
Peter
On 6/8/19 5:58 AM, Peter Robinson wrote:
On Fri, Jun 7, 2019 at 10:58 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:38 PM, Steven A. Falco wrote:
On 6/7/19 2:32 PM, Peter Robinson wrote:
On Fri, Jun 7, 2019 at 7:28 PM Steven A. Falco stevenfalco@gmail.com wrote:
On 6/7/19 2:26 PM, Peter Robinson wrote:
> I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
For the wandboard you can actually have the entire OS on SATA. The only thing that needs to be on a SD card is U-Boot.
So if you take a new image and DD it out to the sata device, then just dd out the U-Boot to a mSD card it should just all boot.
That is very interesting. So I think you are saying that the initramfs that is part of the Fedora 30 image already has the necessary drivers. Do I have that right?
Sort of. The pre generated images that we ship have "generic" initramfs which have a LOT of drivers so the images will boot on the vast majority of Arm devices, once the first kernel update is applied it automatically moves to a host specific initramfs so will then be a lot smaller, and hence much quicker to boot, but will not be a generic initramfs.
Excellent! That is a good design.
I am happy to report that it worked perfectly. My Wandboard is now running entirely from a SATA drive, with the tiny exception of U-Boot.
Excellent news, feel free to suggest any improvements that could be done to improve the process.
Is there a page where I could contribute some information, or is this already written up? In particular, I find that on a cold boot, it usually fails, because U-Boot is faster than the disk can spin up. :-) However, if I then hit the reset button it boots fine. Others might want to know that.
Steve
On 6/8/19 5:58 AM, Peter Robinson wrote:
I find that on a cold boot, it usually fails, because U-Boot is faster than the disk can spin up. :-) However, if I then hit the reset button it boots fine. Others might want to know that.
I'm using the following kernel options in case where the SATA disk needs to spin up first to become usable: rootwait rootdelay=5
On 7/4/19 3:52 AM, Damian Wrobel wrote:
On 6/8/19 5:58 AM, Peter Robinson wrote:
I find that on a cold boot, it usually fails, because U-Boot is faster than the disk can spin up. :-) However, if I then hit the reset button it boots fine. Others might want to know that.
I'm using the following kernel options in case where the SATA disk needs to spin up first to become usable: rootwait rootdelay=5
Thanks for the tip! I'll give that a try.
Steve
On 7/4/19 9:30 AM, Steven A. Falco wrote:
On 7/4/19 3:52 AM, Damian Wrobel wrote:
On 6/8/19 5:58 AM, Peter Robinson wrote:
I find that on a cold boot, it usually fails, because U-Boot is faster than the disk can spin up. :-) However, if I then hit the reset button it boots fine. Others might want to know that.
I'm using the following kernel options in case where the SATA disk needs to spin up first to become usable: rootwait rootdelay=5
Thanks for the tip! I'll give that a try.
Unfortunately, it turns out that rootwait/delay doesn't help. The problem occurs even earlier: U-Boot cannot find any bootable devices. Therefore, I need to add a delay in U-Boot.
But it is not a big deal - I very rarely power-cycle my Wandboard. It is on a UPS, and runs 24/7. It is only power-cycled if I have to replace hardware.
Steve
On 7/4/19 9:30 AM, Steven A. Falco wrote: Therefore, I need to add a delay in U-Boot.
There seems to be U-Boot equivalent of 'rootdelay' called: 'bootdelay'[1].
[1] http://processors.wiki.ti.com/index.php/Change_U-Boot_bootdelay_setting
On 7/6/19 3:35 AM, Damian Wrobel wrote:
On 7/4/19 9:30 AM, Steven A. Falco wrote: Therefore, I need to add a delay in U-Boot.
There seems to be U-Boot equivalent of 'rootdelay' called: 'bootdelay'[1].
[1] http://processors.wiki.ti.com/index.php/Change_U-Boot_bootdelay_setting
And that one works. I set it to 10 seconds, and the board booted properly. I could hear the disk spin up, and the heads loaded prior to U-Boot querying the drive.
Thanks very much for the assistance.
Steve
-
Damian Wrobel -
Nicolas Chauvet -
Peter Robinson -
Steven A. Falco