MLD-5.x > Banana PI
Individuelle Installation auf Festplatte von Banana Pi geht nicht
silverado:
--- Quote ---Di Mai 3 21:39:25 CEST 2016
==write bootblock on and boot files on mmcblk0p1==
dd: can't open '/dev/': Is a directory
====== failed ======
--- End quote ---
clausmuus:
Hast Du bei dem Versuch vergessen die Boot Partition auszuwählen?
Claus
silverado:
Ne, war alles angegeben.
Habe es jetzt noch mal einen ganz neuen Versuch gestartet. Alle Angaben sind wie oben beschrieben, alle Häkchen gesetzt (nur nicht das zum Formatieren der Datenpartition, die möchte ich so behalten).
Ergebnis:
--- Quote ---Di Mai 3 21:57:03 CEST 2016
==Installation startet==
==unmount /dev/mmcblk0p1==
Di Mai 3 21:57:03 CEST 2016
==format disk mmcblk0p1==
mkfs.fat 3.0.27 (2014-11-12)
------ done ------
==unmount /dev/sda1==
Di Mai 3 21:57:04 CEST 2016
==format disk sda1==
Btrfs v3.17
See http://btrfs.wiki.kernel.org for more information.
fs created label (null) on /dev/sda1
nodesize 16384 leafsize 16384 sectorsize 4096 size 9.32GiB
------ done ------
Di Mai 3 21:57:04 CEST 2016
==upgrade system==
Reading package lists...
Building dependency tree...
The following packages will be upgraded:
base init
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 310 kB of archives.
After this operation, 4.096 B of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
base init
Authentication warning overridden.
Get:1 http://www.minidvblinux.de/download/5.1/files/ testing/main base armhf 0-99.5 [301 kB]
Get:2 http://www.minidvblinux.de/download/5.1/files/ testing/main init armhf 0-102.11 [9.112 B]
Fetched 310 kB in 2s (150 kB/s)
(Reading database ...
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 30%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 80%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 841 files and directories currently installed.)
Preparing to unpack .../archives/base_0-99.5_armhf.deb ...
Unpacking base (0-99.5) over (0-99.4) ...
Setting up base (0-99.5) ...
Installing new version of config file /etc/passwd ...
(Reading database ...
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 30%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 80%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 842 files and directories currently installed.)
Preparing to unpack .../init_0-102.11_armhf.deb ...
Unpacking init (0-102.11) over (0-102.9) ...
Setting up init (0-102.11) ...
------ done ------
Di Mai 3 21:57:13 CEST 2016
==install system on sda1==
Create subvolume '/mnt/sda1/@cache'
Create subvolume '/mnt/sda1/@data'
Create subvolume '/mnt/sda1/@root____________________'
------ done ------
Di Mai 3 21:57:17 CEST 2016
==partitioning disk sda1==
ls: /dev/sda1?*: No such file or directory
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 9546.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4):
/dev/sda1:
hdparm: BLKRRPART: Invalid argument
Disk /dev/sda1: 10.0 GB, 10010133504 bytes
255 heads, 63 sectors/track, 1216 cylinders, total 19551042 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/sda1 doesn't contain a valid partition table
------ done ------
Di Mai 3 21:57:19 CEST 2016
==write bootblock on and boot files on mmcblk0p1==
dd: can't open '/dev/': Is a directory
====== failed ======
--- End quote ---
clausmuus:
So, hab's gefunden.
Mach mal vor dem installieren ein Upgrade des Systems (das install paket ist neu). Dann sollte das Schreiben des bootblocks funktionieren.
Claus
silverado:
:) :) :)
Cool! Jetzt klappts! Viiieeelen herzlichen Dank für Deine Hilfe!
Navigation
[0] Message Index
[*] Previous page
Go to full version