Netwotk boot of max2play ?

Max2Play Home Forums Max2Play Development (Ideas, Wishes) Netwotk boot of max2play ?

Tagged: 

Viewing 17 posts - 1 through 17 (of 17 total)
  • 9. April 2017 at 17:25 #28039

    Hi, has anybody max2play running on network boot?

    I successfully installed boot partition on nfs server and got max2play booting from network, similar to docu here: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net_tutorial.md

    But after some seconds it stops complete. Got no idea from logfiles so far.

    This would be great for managing the os partition on my nfs server (running on XEN), where I can use snapshots, backup and other mechanisms from my IT infrastructure also with my raspberry pi installations. With my out of the box jessi and kodi (openelec) this is running fantastic.

    Any idea or experiences on that?

    regards
    Michael

    • This topic was modified 7 years ago by mtk. Reason: specify nfs
    11. April 2017 at 13:58 #28104

    Hi mtk

    Could you send us the log files, we will have a look on it, and get back to you.

    Regards,
    Mohammad Mbydeen

    11. April 2017 at 17:54 #28108

    sorry, but I do not get logfiles, because I can#t access the pi anymore before it stops working.

    I just can see a only a few wanrings on the monitor connected to the pi.

    What I have done so far is

    modified cmdline.txt:
    root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.104:/nfs-server/max2play,udp,vers=3 smsc95xx.turbo_mode=N rw ip=dhcp rootwait elevator=deadline init=/bin/systemd

    tried that with and without init=/bin/systemd as discussed in a forum.

    removed sd card mounts in fstab:

    # proc            /proc           proc    defaults          0       0
    # /dev/mmcblk0p1  /boot           vfat    defaults          0       2
    # /dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
    
    proc /proc proc defaults 0 0
    # /dev/mmcblk0p1 /boot vfat defaults 0 2
    # /dev/mmcblk0p2 / ext4 defaults,noatime 0 1
    tmpfs /tmp tmpfs defaults,noatime,nosuid,size=200m 0 0
    tmpfs /var/tmp tmpfs defaults,noatime,nosuid,size=60m 0 0
    tmpfs /var/log tmpfs defaults,noatime,nosuid,mode=0755,size=200m 0 0
    tmpfs /var/run tmpfs defaults,noatime,nosuid,mode=0755,size=20m 0 0
    
    ##USERMOUNT
    # a swapfile is not a swap partition, no line here
    #   use  dphys-swapfile swap[on|off]  for that

    on nfs server side a made a copy with rsync of the / (root partition) to my nfs server.
    So this nfs mount is booting, but not working.

    Maybe you can make a simple test with one of your nfs server by your own?

    Would be a great feature to have at least the root file system on a central server.
    With Pi3 you can even boot without any SD card inside with a simple tftp boot server, which was quite simple.
    Mine is running as a VM within a (Citrix) XEN server. I take snapshots within a second of all of my pi installations or automaticly backup (rotating) the complete OS of all my raspis.

    kind regards
    Michael

    12. April 2017 at 12:39 #28152

    Hi Michael

    Unfortunately, we could not simulate your setup in our lab, the technical problem is more related to NFS server not to Max2Play, but we can provide you some links that could help you to configure the network boot:

    https://help.ubuntu.com/community/Fstab

    https://blogs.wcode.org/2013/09/howto-netboot-a-raspberry-pi/

    Regards,
    Mohammad Mbydeen

    12. April 2017 at 14:54 #28169

    Hi Mohammad

    I don#t think that is a nfs server related issue. My debian jessie installations and even some Kodi installations are running well on my setup.

    Even max2play is running. I can see max2play allready booting from nfs with my configuration created within max2play formerly on SD card.

    Maybe some community member will try do this …
    Here is some quik instruction:

    On nfs server (mine is debian):
    (m2p_image_241.img is image created with Win32DiskImager)

    fdisk -l m2p_image_241.img

    this will show partition start for offset calculation:

    Disk m2p_image_241.img: 4025 MB, 4025483264 bytes
    255 heads, 63 sectors/track, 489 cylinders, total 7862272 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x34e4b02c
    
                 Device Boot      Start         End      Blocks   Id  System
    m2p_balkon_241.img1            8192      131071       61440    c  W95 FAT32 (LBA)
    m2p_balkon_241.img2          131072     7462272     3665600+  83  Linux
    m2p_balkon_241.img3         7462273     7862271      199999+  83  Linux
    

    root partition starts at 131072 * 512 = 67108864

    mount -v -o loop,offset=<strong>67108864 </strong>m2p_image_241.img /mnt/m2p/

    now make a full copy of sd card root partition to nfs server:

    rsync -arv /mnt/m2p/ /nfs-server/max2play/

    On NFS Server I made some export within /etc/exports:

    
    /srv/nfs/jessie_light/ *(rw,sync,no_subtree_check,no_root_squash)
    /nfs-server/pixel/    *(rw,sync,no_subtree_check,no_root_squash)
    /tftpboot/22bddc11.elec *(rw,sync,no_subtree_check,no_root_squash)
    /nfs-server/hifi.elec   *(rw,sync,no_subtree_check,no_root_squash)
    /nfs-server/hifi.pix   *(rw,sync,no_subtree_check,no_root_squash)
    
    /nfs-server/max2play *(rw,sync,no_subtree_check,no_root_squash)
    

    and restarted nfs server

    Configuration on max2play sd card s described above …
    Now I can see the raspi booting and making a ping on it shows that he is there on network for quite some seconds.

    Then he stops working, no reaction on keyboard a.s.o.

    hope that was helpful
    Michael

    PS: hope this reply will not disappear again, got some problems on editing …

    18. April 2017 at 11:23 #28319

    Hi,

    meanwhile I tested also another cmdline.txt version with fixed ip definition instead og ip=dhcp, not working … 🙁

    root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.104:/nfs-server/max2play,udp,vers=3 smsc95xx.turbo_mode=N rw ip=192.168.1.151::192.168.1.200:255.255.255.0::eth0:off rootwait elevator=deadline

    where ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

    Is there any way to create a max2play on a clean/pure jessie installation?
    Maybe I can create a netboot capable version of max2play by using a working network bootable version of raspbian.

    By the way, max2play should be able to reproduce this in their lab. You just need a second raspi working as a nfs server in the first step, which is very easy to realize.
    With that you can boot the image from sd card and just boot root filesystem from network via cmdline.txt

    In a second step you might also implement a boot tftp server, which does not need some sd card on client anymore.
    You can share on big sd card for all of your max2play installations or you might place the shared folders on a usb stick or hdd/ssd.

    So I really would like to implement network boot with max2play. Please let me know, if you like, I will support you on that and we will do that close together. I am not familiar enough with max2play to do that by my own.

    Michael

    19. April 2017 at 11:12 #28340

    Hi mtk,

    Thank you for your information.

    We will consider your suggestion to implement the network boot, then we will contact you if you would like to offer some help 🙂

    Best Regards,
    Mohammad Mbydeen

    2. Mai 2017 at 11:15 #28652

    Network boot would be FANTASTIC!
    I have so many problems with SD cards, and it’s soo time consuming to fix these issues. Netboot would be really great.

    • This reply was modified 6 years, 12 months ago by okenny.
    4. Mai 2017 at 15:26 #28705

    until max2play will do that, we can create some own project to realize that 😉
    My project at home has some kind of Raspberry Nodes without any webinterface beside webmin (administration) or mjpg streamer (raspi or usb cam streaming server for my zoneminder VM).

    I realized the following functionality allready:
    1. raspbian jessie light with pixel (desktop) and Cairo dock (Menu)
    2. mjpg streamer experimental (supports also raspi cam)
    3. shairport-sync (supports synced streaming)
    4. MPD Server (used for FHEM automation and MPD clients on smartphones and tablets)
    5. pico2wave (text to speach engine)
    6. hostapd (WLAN APs in all rooms, bidged to get all shairport servers on my smartphone/tablets)
    7. openelec network boot (running xstream, logan, aluc, with different user management profiles on my server)

    There are still some TODOs, but I will use my thin installation in parallel for some clients and my own development.
    Its much more easy to return to a snapshot which is stable on my nfs server running as VM on my citrix server (6.5 free edition). I can use xencenter (free) or similar (scripted) to create or return to snaphots. And because homeautomation is a living thing this is the most usefull functionality when some updates/upgrades/development are causing problems.

    Hope that may2play will take up that aspect some day 🙂

    11. Mai 2017 at 14:26 #28793

    Hello mtk,

    Thank for your contribution to the forum, and we hope that we could find a common ground for cooperation with you to work on Max2Play related projects in the future.

    Best Regards,
    Mohammad Mbydeen

    23. Oktober 2018 at 12:50 #38791

    Any news about this topic?
    Is there a working network booted max2play possible in the meantime?

    Thanks,
    Norbert

    9. Juli 2019 at 20:15 #46231

    It’s me again. Is anyone, maybe max2play, working on network boot?
    Could it be, that raspberry4 makes it more possible to find a running setup?

    Regards,
    Norbert

    12. Juli 2019 at 10:01 #46299

    Hello Norbert,

    Thanks for chiming in again. Do you have any news regarding the Pi4 and network booting?

    28. Juli 2019 at 20:09 #46509

    Hello Heiner,

    no, I didn’t.
    I just wanted to bring the topic back into focus.

    Regards,
    Norbert

    28. Juli 2019 at 23:14 #46512

    I did not try that with m2p anymore. meanwhile I implemented a boot server as VM and made my own raspi nodes with snips, motioneye, webmin for administration, mpd a.s.o. for iobroker.

    14. Januar 2020 at 20:58 #47928

    For me it works.

    here my cmdline.txt

    dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=10.11.0.6:/data/nfs/max2play59 rw elevator=deadline rootwait ip=dhcp

    very important is ip=dhcp after that pi can mount the nfs.

    • This reply was modified 4 years, 3 months ago by Tschak.
    15. Januar 2020 at 16:49 #47931

    Hi, it is not really necessary to provide IP via dhcp, manual ip assignment is just another way to do this.
    When I tested network boot with max2play it was allmost running but after e specific time it allways stopped working.
    Maybe m2p was changed/improved meanwhile, so I dont know if it is running well now.

    Meanwhile I switched over to a bare raspian installation with my own functionality, which fits more to my purposes.
    My installation with network boot (without any SD card) from my PXE Server including snips (voice recognition), webcam via motioneye, mjpstreamer, MPD & yMPD (MPD Webinterface), TTS (text2Speech engine), USB redirector Server (used for CUL connection for my FHEM and ioBroker installation) a.s.o. So I left M2P some time time ago. Maybe I will retry in future …

Viewing 17 posts - 1 through 17 (of 17 total)

You must be logged in to reply to this topic.

Register here