ericwoud / buildR64arch

Build script for image for BananaPi R64 / R3 (R4) running Arch Linux
21 stars 5 forks source link

Error: Device not specified - Cannot write minimal ArchLinux image on sd card #12

Closed GiovanniBalestrieri closed 3 months ago

GiovanniBalestrieri commented 3 months ago

I cannot write the image on the sd card. I followed the steps provided in the README

$ ./build.sh -F
Current dir: /home/userk/development/git/buildR64arch
Compatible:
Host Arch: x86_64
rootdev=/dev/sda1 , do not use.
pkroot=sda , do not use.
1) bpir3 Bananapi-R3
2) Quit
Choose target to format image for: **1**
1) sdmmc SD Card
2) emmc  EMMC onboard
3) Quit
Choose atfdevice to format image for: **1**
 1) /dev/loop0 4K
66) /dev/sde 29.7G
67) Quit
Choose device to format: 66
Device=/dev/sde
Target=bpir3
ATF-device=sdmmc

Create root filesystem

1) RT       Router setup, SFP module eth1 as wan
2) RTnoSFP  Router setup, not using SFP module
3) AP       Access Point setup
4) Quit
Choose setup to create root for: **1**
Setup=RT
Enter ip address for local network (emtpy for default): 
IP=
KERNELS=="sde", ENV{UDISKS_IGNORE}="1"
cat: /sys/block/sde/device/preferred_erase_size: No such file or directory
Erase size = 4 MB
Model: Generic MassStorageClass (scsi)
Disk /dev/sde: 30437MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start    End       Size      File system  Name  Flags
 1      1.00MiB  30436MiB  30435MiB  fat32              msftdata

Are you sure you want to format /dev/sde???
Type <format> to format: **format**
/dev/sde: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/sde: 8 bytes were erased at offset 0x76e47fe00 (gpt): 45 46 49 20 50 41 52 54
/dev/sde: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
Warning: The resulting partition is not properly aligned for best performance: 34s % 2048s != 0s
Model: Generic MassStorageClass (scsi)
Disk /dev/sde: 31166976kiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start      End          Size         File system  Name              Flags
 1      17.0kiB    1024kiB      1007kiB                   bpir3-sdmmc-atf   legacy_boot
 2      1024kiB    196608kiB    195584kiB                 bpir3-sdmmc-fip
 3      196608kiB  31166464kiB  30969856kiB               bpir3-sdmmc-root

realpath: '': No such file or directory
blkdiscard: invalid option -- 'f'
Try 'blkdiscard --help' for more information.
realpath: '': No such file or directory
    Error: Device not specified

Usage: mkfs.f2fs [options] device [sectors]
[options]:
  -a heap-based allocation [default:0]
  -c [device path] up to 7 devices excepts meta device
  -d debug level [default:0]
  -e [cold file ext list] e.g. "mp3,gif,mov"
  -E [hot file ext list] e.g. "db"
  -f force overwrite the exist filesystem
  -i extended node bitmap, node ratio is 20% by default
  -l label
  -m support zoned block device [default:0]
  -o overprovision ratio [default:5]
  -O [feature list] e.g. "encrypt"
  -q quiet mode
  -s # of segments per section [default:1]
  -S sparse mode
  -t 0: nodiscard, 1: discard [default:1]
  -w wanted sector size
  -z # of sections per zone [default:1]
sectors: number of sectors. [default: determined by device size]
NAME   MOUNTPOINT LABEL PARTLABEL  SIZE UUID
sde                               29.7G 
|-sde1                            1007K 
|-sde2                             191M 
`-sde3                            29.5G 
Mountdev = 
Bootdev  = 
removed '/run/udev/rules.d/10-no-automount-bpir.rules

Any advice on how to proceed?

ericwoud commented 3 months ago

Does latest commit help?

GiovanniBalestrieri commented 3 months ago

Yes, I was able to boot the system. Closing the issue

GiovanniBalestrieri commented 3 months ago

Solved with commit