Trying to install arch with jumpdrive, but jumpdrive isn't booting

Trying to install arch with jumpdrive, but jumpdrive isn't booting - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Arch Linux on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=159)
+---- Thread: Trying to install arch with jumpdrive, but jumpdrive isn't booting (/showthread.php?tid=14872)

Trying to install arch with jumpdrive, but jumpdrive isn't booting - pineuser0 - 09-12-2021

I'm getting pine64-pinephone.img.xz from Releases · dreemurrs-embedded/Jumpdrive · GitHub [/url] [url=https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz]
After I run "sudo dd if=pine64-pinephone.img of=/dev/sda2 status=progress", I have jumpdrive on my microSD card, but when I insert it into my turned off pinephone, the pinephone boots into Plasma Mobile, not jumpdrive.
What could mitigate this problem so that I can end with an arch linux installation on my pinephone?

RE: Trying to install arch with jumpdrive, but jumpdrive isn't booting - 8bit - 09-12-2021

Code:
of=/dev/sda2

should be

Code:
of=/dev/sda

RE: Trying to install arch with jumpdrive, but jumpdrive isn't booting - pineuser0 - 09-12-2021

(09-12-2021, 08:03 AM)8bit Wrote:
Code:
of=/dev/sda2
should be

Code:
of=/dev/sda

The correct information was written to the microSD card, that was simply sda # stacking up from previous usb mountings.

Jumpdrive is safely installed on the microSD card, the output(which could've prevented your misunderstanding) is the following:
39522816 bytes (40 MB, 38 MiB) copied, 4 s, 9.9 MB/s
83968+0 records in
83968+0 records out
42991616 bytes (43 MB, 41 MiB) copied, 5.0879 s, 8.4 MB/s

This indicates that it was written to a drive, while the only drive attached to any sda was the microSD card

tl:dr - still looking for suggestions on how to successfully install arch linux on my pinephone

RE: Trying to install arch with jumpdrive, but jumpdrive isn't booting - linmob - 09-12-2021

(09-12-2021, 08:03 AM)8bit Wrote:
Code:
of=/dev/sda2
should be

Code:
of=/dev/sda

Please don't follow this advice, /dev/sda may well be your main hard drive, rendering your PC unbootable.

But: Depending on your experiences with dd and the terminal in general, it may be better to use GNOME Disks or Etcher to make this easier and make sure that you write to the correct device. Also: Did you put the SD card into the correct (upper) slot?

RE: Trying to install arch with jumpdrive, but jumpdrive isn't booting - kqlnut - 09-12-2021

The point being that /dev/sda2 is most likely not your SD card. At best that device doesn't exist, at worst you will irreversebly overwrite an existing partition on your machine without a warning. Your SD card will probably show up as /dev/mmcblkX. Don't blindly copy and run commands and make sure that you are writing to the correct device (check with lsblk for example). You can find installation instructions here (there is also a link to more detailed instructions if needed).

RE: Trying to install arch with jumpdrive, but jumpdrive isn't booting - wibble - 09-14-2021

(09-12-2021, 08:11 AM)pineuser0 Wrote:
(09-12-2021, 08:03 AM)8bit Wrote:
Code:
of=/dev/sda2
should be

Code:
of=/dev/sda

The correct information was written to the microSD card, that was simply sda # stacking up from previous usb mountings.

Jumpdrive is safely installed on the microSD card, the output(which could've prevented your misunderstanding) is the following:
39522816 bytes (40 MB, 38 MiB) copied, 4 s, 9.9 MB/s
83968+0 records in
83968+0 records out
42991616 bytes (43 MB, 41 MiB) copied, 5.0879 s, 8.4 MB/s

This indicates that it was written to a drive, while the only drive attached to any sda was the microSD card

tl:dr - still looking for suggestions on how to successfully install arch linux on my pinephone

I believe it's you that is misunderstanding. If you wrote to /dev/sda2 you wrote to the second partition on device /dev/sda, not to the raw device, so the data was written to the wrong place on the device and won't be bootable.