I’ll reproduce the commands here, as there are a couple of differences.
The SSD even presented it as /dev/sda, the same as on that machine.
The procedure I followed was remarkably similar to that I used for the Kimsufi box.
#WIPEFS RASPBIAN INSTALL#
Normally here you’d probably create a configuration.nix and do nixos-rebuild to make the system you want, but I wanted to install to my SSD so I had a little more work to do. I didn’t entirely pay attention here and ended up writing the compressed image to the SD card and trying to boot that–this predictably failed, and I re-read the instructions and uncompressed it first before trying again.īooting this results in it resizing to fit the SD card, and then drops you into a terminal. This ended up being one built in July–images since then appear to have had some build failures due to something related to ZFS. I grabbed the latest NixOS 21.05 new_kernel image I could find on Hydra. I did consider trying to install it from the existing Raspbian OS that was on the SD card already, in a similar fashion to how I did so using the Kimsufi recovery OS, but as I believe it was running a different architecture I wasn’t sure how that would work.
#WIPEFS RASPBIAN UPDATE#
sudo rpi-eeprom-update # Read the output of this before proceeding sudo rpi-eeprom-update -d -a # Actually do the update sudo raspi-config # Go to Advanced Options and enable USB boot Installation process The first thing I did before getting started was boot Raspbian, update it, and then use it to update the firmware to a version that properly supports USB boot, as my Pi 4 was old enough not to have that out of the box. I also wanted to use the AArch64 architecture instead of the armv7 that I believe Raspbian had been using. I could quite easily have just dded the SD card image onto the drive and booted that and called it a day, but I wanted to make life difficult for myself really wanted to use ZFS. This would give me a bit more space and probably stand up to more use than the SD card would, so I got one. Previously I’d not been keen doing that on an SD card because I still have a perception that Pis running Linux can chew them up pretty quickly, although I suppose reinstalling them from a reproducible OS would be less painful were this to happen.Īs it happens, last week a vendor sent me an email saying that they had a sale on the Argon ONE m.2 case, which would accept an m.2 SATA SSD.
As is evident by the number of posts I have on here about installing Nix on every computing device I can get my hands on, I wanted to put NixOS on it. One way to zero while eMMC, however that will take lot of time.I have been wanting to find a more permanent home for the DNS server I built before which was on a Pi 4 running Raspbian. I tried wipfs -a but it has the same behavior. Now question is how can we remove this last mounted information from partition? with e2fsprog version 1.42.8įrom release note of e2fsprog-1.42.13 I see that last mounted is added to some structure. Last mounted on /mnt/rfs_src on Fri Feb 16 13:52:18 2018
Now while formatting a partition mkfs.ext4 complains that partition has filesystem on it and it was mounted at particular date in past and ask if it should proceed ? /dev/mmcblk0p15 contains a ext4 file system labelled 'rootfs' Partitions gets deleted however script re-partitions eMMC again in the same number of partitions.Īfter that it tries to format each partition using mkfs.ext4 (e2fsprogs version 1.42.13). Script erases gpt partition table using following commands #Delete primary gpt (first 17KiB)ĭd if=/dev/zero of=/dev/mmcblk0 bs=1024 count=17ĭd if=/dev/zero of=/dev/mmcblk0 seek=3735535 bs=1024 count=17
#WIPEFS RASPBIAN SOFTWARE#
We have script to flash software on the board. We have Beaglbone black based custom board with 256MB RAM and 4GB eMMC.
0 kommentar(er)
