This is an attempt to instal on a BeagleBone Black
using the latest snapshot via miniroot-am335x-60.fs.

The install goes fine up to creating the fylesystems:

/dev/rsd0a: 257.5MB in 527456 sectors of 512 bytes
5 cylinder groups of 64.11MB, 4103 blocks, 8320 inodes each
/dev/rsd0m: 2047.3MB in 4192960 sectors of 512 bytes
11 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0l: 2055.2MB in 4209024 sectors of 512 bytes
11 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0d: 1019.8MB in 2088448 sectors of 512 bytes
6 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0e: 2047.3MB in 4192960 sectors of 512 bytes
11 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0o: 1529.6MB in 3132672 sectors of 512 bytes
8 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0p: 1547.8MB in 3169920 sectors of 512 bytes
8 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
/dev/rsd0n: 1529.6MB in 3132672 sectors of 512 bytes
8 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
newfs: reduced number of fragments per cylinder group from 32128 to
31992 to enlarge last cylinder group
/dev/rsd0f: 251.0MB in 514080 sectors of 512 bytes
5 cylinder groups of 62.48MB, 3999 blocks, 8064 inodes each
newfs: reduced number of fragments per cylinder group from 32128 to
31992 to enlarge last cylinder group
/dev/rsd0g: 251.0MB in 514080 sectors of 512 bytes
5 cylinder groups of 62.48MB, 3999 blocks, 8064 inodes each
/dev/rsd0j: 125.5MB in 257024 sectors of 512 bytes
4 cylinder groups of 31.38MB, 2008 blocks, 4096 inodes each
newfs: reduced number of fragments per cylinder group from 65264 to
65000 to enlarge last cylinder group
/dev/rsd0k: 509.9MB in 1044256 sectors of 512 bytes
5 cylinder groups of 126.95MB, 8125 blocks, 16256 inodes each
/dev/rsd0h: 2047.3MB in 4192960 sectors of 512 bytes
11 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
Available disks are: sd1.
Which disk do you wish to initialize? (or 'done') [done]


Then it fails trying to mount them:

/dev/sd0a (59ea1aca5721b96d.a) on /mnt type ffs (rw, asynchronous, local)
/dev/sd0m (59ea1aca5721b96d.m) on /mnt/home type ffs (rw, asynchronous, local, 
nodev, nosuid)
/dev/sd0l (59ea1aca5721b96d.l) on /mnt/tmp type ffs (rw, asynchronous, local, 
nodev, nosuid)
/dev/sd0d (59ea1aca5721b96d.d) on /mnt/usr type ffs (rw, asynchronous, local, 
nodev)
/dev/sd0e (59ea1aca5721b96d.e) on /mnt/usr/local type ffs (rw, asynchronous, 
local, nodev)
mount_ffs: 59ea1aca5721b96d.o on /mnt/usr/obj: Input/output error

mount_ffs: 59ea1aca5721b96d.p on /mnt/usr/ports: Input/output error

mount_ffs: 59ea1aca5721b96d.n on /mnt/usr/src: Input/output error

mount_ffs: 59ea1aca5721b96d.f on /mnt/var: Input/output error

mkdir: /mnt/var/log: Input/output error
mount: realpath /mnt/var/log: Input/output error

mkdir: /mnt/var/mail: Input/output error
mount: realpath /mnt/var/mail: Input/output error

mkdir: /mnt/var/postgresql: Input/output error
mount: realpath /mnt/var/postgresql: Input/output error

mkdir: /mnt/var/www: Input/output error
mount: realpath /mnt/var/www: Input/output error

WARNING! The following filesystems were not properly mounted:
/mnt/usr/obj (59ea1aca5721b96d.o)
/mnt/usr/ports (59ea1aca5721b96d.p)
/mnt/usr/src (59ea1aca5721b96d.n)
/mnt/var (59ea1aca5721b96d.f)
/mnt/var/log (59ea1aca5721b96d.g)
/mnt/var/mail (59ea1aca5721b96d.j)
/mnt/var/postgresql (59ea1aca5721b96d.k)
/mnt/var/www (59ea1aca5721b96d.h)
Continue anyway? [no]


What could be possibly causing this?
I am pretty sure that the card is OK:
I read and wrote the whole card using dd
before using it for the installation.
And it is the third card where I get this kind of error.
I have been running obsd on this very same hardware
for about two years without any hardware problems.

(And I get the same kind of error trying to install on the internal MMC.
WARNING! The following filesystems were not properly mounted:
/mnt (309f7be0acf336f4.a)
Continue anyway? [no])

The card which boots the miniroot.fs is the same card
onto which I am installing. Is this a problem?
The installing ramdisk is in memory once loaded
so I can install on the card it was loaded from, right?

Is anyone else seeing this?

        Jan

Reply via email to