On Saturday 2017-01-28 11:46, Alexander Graf wrote:
On 28/01/2017 10:55, Paul Neuwirth wrote:
Hello group, as I am really unlucky with sd cards, every one has bad sectors, data are partly not fully written without notice... ... I want to try to install openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2 image using a nfsroot. anyone who tried this?
I haven't but it should be reasonably straight forward.
my idea was first to install to an sdcard (hope this will work) then try to build a initrd with network/nfs support (or does the original already have?) modify boot params to use nfsroot (and of course put the rootfs on an nfs share).
Basically that should work. To generate a working initrd, just do it within the nfsroot chroot:
$ mount <nfs> /nfs $ for i in dev dev/pts sys proc; do mount --bind /$i /nfs/$i; done $ chroot /nfs $ mkinitrd
That way dracut has the chance to detect that your rootfs (/, which is really /nfs) is located on NFS and include network as well as NFS support.
The resulting initrd obviously resides on your NFS share then though ;).
even better would be a pxe-bootloader.. googling around i did not find such for arm/raspberry pi.. any hints?
There is full PXE support on the Raspberry Pi 3:
https://www.raspberrypi.org/blog/pi-3-booting-part-ii-ethernet-all-the-aweso...
But even with a normal SD based boot, U-Boot already has everything it needs to make PXE boot work. Try:
U-Boot# setenv boot_targets dhcp U-Boot# boot
that should try to load grub2 from dhcp rather than SD card. If you want to make this permanent, just remove your bootarm.efi binary on the ESP (/dev/mmcblk0p1).
Once you're in grub2, you can access file paths relative to the PXE loading location IIRC.
Alex
thanks, exactly the information i need. but i am still failing at the first step... copied image on sd card, installation (creating partitions, etc.) seemed to work, after a reboot system did not come up.. (uboot, grub2 worked, loading initrd -> nothing) now i wanted to check the ext-filesystem: # fsck.ext4 -c -f /dev/sdd2 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 1767649 blocks The physical size of the device is 1765641 blocks Either the superblock or the partition table is likely to be corrupt! good start :-/ ok several badblocks, but fsck succeeded not finding any fs errors.. boot... again nothing :( going to try next sd card -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org