Base on Frank’s Images repo, I ran “./buildimg.sh bpi-r3 noble” in a Linux laptop in order to create Ubuntu sdmmc image as usual.
But it was reported NTFS related error as below capture. I just found out it appeared after mounting the specific loop devices.
It is weird that the filesystem should not be containing any NTFS stuff. Do you have experience on resolving this?
...
...
...
bpi
umounting tmpfs...
-rw-r--r-- 1 michael michael 7.3M Oct 3 19:39 bpi-r3_emmc.img.gz
-rw-r--r-- 1 root root 302M Oct 3 20:19 noble_arm64.tar.gz
unpack imgfile (bpi-r3_noble_6.12.47-main_sdmmc.img.gz)...
setting up imgfile to loopdev...
mounting loopdev...
NTFS signature is missing.
Failed to mount '/dev/loop0p5': Invalid argument
The device '/dev/loop0p5' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/loop0p5': Invalid argument
The device '/dev/loop0p5' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
mounting BPI-BOOT failed
real 37m43.463s
user 0m47.905s
sys 0m9.244s
> sudo mount /dev/loop0p5 mnt/BPI-BOOT/
NTFS signature is missing.
Failed to mount '/dev/loop0p5': Invalid argument
The device '/dev/loop0p5' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/loop0p5': Invalid argument
The device '/dev/loop0p5' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> sudo mount /dev/loop0p6 mnt/BPI-ROOT/
NTFS signature is missing.
Failed to mount '/dev/loop0p6': Invalid argument
The device '/dev/loop0p6' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/loop0p6': Invalid argument
The device '/dev/loop0p6' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> sudo fdisk -l
Disk /dev/loop0: 7.28 GiB, 7818182656 bytes, 15269888 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
Disklabel type: gpt
Disk identifier: 32D7F8C7-58A1-47F6-855F-B8ABBCFE18C9
Device Start End Sectors Size Type
/dev/loop0p1 34 8191 8158 4M Linux filesystem
/dev/loop0p2 8192 9215 1024 512K Linux filesystem
/dev/loop0p3 9216 13311 4096 2M Linux filesystem
/dev/loop0p4 13312 17407 4096 2M Linux filesystem
/dev/loop0p5 17408 222207 204800 100M Linux filesystem
/dev/loop0p6 222208 13739008 13516801 6.4G Linux filesystem
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: WDC PC SN520 SDAPNUW-256G-1006
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E76EFAA6-A53D-4B5E-816F-9B0A5D6CE98C
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 739327 737280 360M EFI System
/dev/nvme0n1p2 739328 1001471 262144 128M Microsoft reserved
/dev/nvme0n1p3 1001472 442804223 441802752 210.7G Microsoft basic data
/dev/nvme0n1p4 442804224 446431231 3627008 1.7G Windows recovery environment
/dev/nvme0n1p5 446431232 500107263 53676032 25.6G Microsoft basic data
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LX015-1U71
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2dca22c8
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1661140582 1661138535 792.1G 7 HPFS/NTFS/exFAT
/dev/sda2 * 1661140992 1662191615 1050624 513M ef EFI (FAT-12/16/32)
/dev/sda3 1662193662 1953523711 291330050 138.9G 5 Extended
/dev/sda5 1662193664 1953523711 291330048 138.9G 83 Linux
Partition 3 does not start on physical sector boundary.
> fdisk -l bpi-r3*
Disk bpi-r3_6.12.47-main.tar.gz: 94.68 MiB, 99278848 bytes, 193904 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 bpi-r3_emmc.img.gz: 7.24 MiB, 7587840 bytes, 14820 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 bpi-r3_noble_6.12.47-main_sdmmc.img: 7.28 GiB, 7818182656 bytes, 15269888 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
Disklabel type: gpt
Disk identifier: 32D7F8C7-58A1-47F6-855F-B8ABBCFE18C9
Device Start End Sectors Size Type
bpi-r3_noble_6.12.47-main_sdmmc.img1 34 8191 8158 4M Linux filesystem
bpi-r3_noble_6.12.47-main_sdmmc.img2 8192 9215 1024 512K Linux filesystem
bpi-r3_noble_6.12.47-main_sdmmc.img3 9216 13311 4096 2M Linux filesystem
bpi-r3_noble_6.12.47-main_sdmmc.img4 13312 17407 4096 2M Linux filesystem
bpi-r3_noble_6.12.47-main_sdmmc.img5 17408 222207 204800 100M Linux filesystem
bpi-r3_noble_6.12.47-main_sdmmc.img6 222208 13739008 13516801 6.4G Linux filesystem
Thanks.