On Wed, Jun 01, 2016 at 11:26:33PM +0200, Farid Joubbi wrote:
> I was able to boot with the latest snapshot, and it finds both disks.
> Unfortunately I still get the "newfs: wtfs: write error on block 160:
> Input/output error".
>
> Using miniroot-am335x-60.fs 31-May-2016 SHA256:
> e72bd2b7289c845644e77c7a5f7e83e1463b766325a97ace898d0a74cc0dd5e0
>
>
I can confirm that above "error on block 160" is still true with:
SHA256 (miniroot-am335x-60.fs) =
246a058cb18bfa9637ec5d4342d920664044aa3202850b6bb9cceeb83442377a
No problem w/sdcard, but there might possibly be a regression in the
sdmmcbus below ommmc, as some other user wrote about working sdmmc in 5.9
that was not so anymore w/-current, on amd64 that is.
i believe these are from his 5.9 dmesg, to possibly help narrow down:
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe7630 (22 entries)
bios0: vendor Insyde Corp. version "V1.10" date 08/20/2014
bios0: Acer Aspire ES1-111M
sdhc0 at pci0 dev 18 function 0 vendor "Intel", unknown product 0x0f16 rev 0x0e:
apic 2 int 18
sdhc1 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x0f50 rev 0x0e:
apic 2 int 23
scsibus1 at sdmmc1: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed
sd0: 29824MB, 512 bytes/sector, 61079552 sectors
-Artturi
>
>
>
> On Mon, May 30, 2016 at 1:47 AM, Jonathan Gray <j...@jsg.id.au> wrote:
>
> > I think this is a result of the miniroot not flagging the fat fs
> > as active ("f 0" in fdisk). The miniroots that should be appearing
> > on mirrors soon have this added back.
> >
> > SHA256 (miniroot-am335x-60.fs) =
> > 09c55837fd44ad60ab126553bb0506b8ab4cf6d1db7c44a98faf510e8d78ee71
> >
> > On Sun, May 29, 2016 at 11:54:04PM +0200, Farid Joubbi wrote:
> > > Unfortunately the latest snapshot does not boot at all.
> > > It's the miniroot-am335x-60.fs 28-May-2016 09:47 18M md5sum:
> > > 3b6d31fa5325bbc063a2f9f78dc6e253
> > >
> > > All I get is CCCCCCCCCCCCC
> > >
> > >
> > >
> > >
> > > On Sun, May 29, 2016 at 4:19 PM, Jonathan Gray <j...@jsg.id.au> wrote:
> > >
> > > > On Sat, May 28, 2016 at 11:49:07PM +0200, Farid Joubbi wrote:
> > > > > Hi,
> > > > >
> > > > > Since it's not possible to install 5.9 release on the internal
> > storage, I
> > > > > figured that I will try the latest snapshot from May 27th.
> > > > >
> > > > > With the snapshot I am able to choose to install on both sd0 and sd1
> > > > which
> > > > > was not possible with 5.9.
> > > > > The installation goes for a while until I get "newfs: wtfs: write
> > error
> > > > on
> > > > > block 160: Input/output error".
> > > > > I think that the hardware is fine since I am able to install and run
> > > > debian
> > > > > on it without problems.
> > > > >
> > > > > Any ideas?
> > > >
> > > > Today's snapshot is built the below diff, I'd be curious if it changes
> > > > anything.
> > > >
> > > > Index: ommmc.c
> > > > ===================================================================
> > > > RCS file: /cvs/src/sys/arch/armv7/omap/ommmc.c,v
> > > > retrieving revision 1.21
> > > > diff -u -p -r1.21 ommmc.c
> > > > --- ommmc.c 20 May 2016 23:07:05 -0000 1.21
> > > > +++ ommmc.c 29 May 2016 14:17:03 -0000
> > > > @@ -393,8 +393,10 @@ ommmc_attach(struct device *parent, stru
> > > > saa.sct = &ommmc_functions;
> > > > saa.sch = sc;
> > > > saa.caps = SMC_CAPS_4BIT_MODE;
> > > > +#if 0
> > > > if (caps & MMCHS_CAPA_HSS)
> > > > saa.caps |= SMC_CAPS_MMC_HIGHSPEED;
> > > > +#endif
> > > >
> > > > sc->sdmmc = config_found(&sc->sc_dev, &saa, NULL);
> > > > if (sc->sdmmc == NULL) {
> > > >
> > > > >
> > > > >
> > > > > Here is the output:
> > > > >
> > > > > Available disks are: sd0 sd1.
> > > > > Which disk is the root disk? ('?' for details) [sd0] sd1
> > > > > Disk: sd1 geometry: 465/255/63 [7471104 Sectors]
> > > > > Offset: 0 Signature: 0xAA55
> > > > > Starting Ending LBA Info:
> > > > > #: id C H S - C H S [ start: size ]
> > > > >
> > > >
> > -------------------------------------------------------------------------------
> > > > > *0: 0C 0 1 2 - 2 11 9 [ 64: 32768 ]
> > Win95
> > > > > FAT32L
> > > > > 1: 00 0 0 0 - 0 0 0 [ 0: 0 ]
> > > > > unused
> > > > > 2: 00 0 0 0 - 0 0 0 [ 0: 0 ]
> > > > > unused
> > > > > 3: A6 2 11 10 - 465 13 60 [ 32832: 7438272 ]
> > > > > OpenBSD
> > > > > Use (W)hole disk$ or (E)dit the MBR? [whole]
> > > > > Creating a msdos partition and an OpenBSD partition for rest of
> > > > sd1...done.
> > > > > /dev/rsd1i: 32668 sectors in 8167 FAT16 clusters (2048 bytes/cluster)
> > > > > bps=512 spc=4 res=1 nft=2 rde=512 sec=32768 mid=0xf8 spf=32 spt=63
> > > > hds=255
> > > > > hid=2048
> > > > > newfs_msdos: /dev/rsd1i: Input/output error
> > > > > The auto-allocated layout for sd1 is:
> > > > > # size offset fstype [fsize bsize cpg]
> > > > > a: 879.7M 34816 4.2BSD 2048 16384 1 # /
> > > > > b: 239.5M 1836512 swap
> > > > > c: 3648.0M 0 unused
> > > > > d: 2144.1M 2327008 4.2BSD 2048 16384 1 #
> > /usr
> > > > > e: 367.7M 6718048 4.2BSD 2048 16384 1 #
> > /home
> > > > > i: 16.0M 2048 MSDOS
> > > > > Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a]
> > > > > /dev/rsd1a: 879.7MB in 1801696 sectors of 512 bytes
> > > > > 5 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
> > > > > newfs: wtfs: write error on block 160: Input/output error
> > > > > newfs: reduced number of fragments per cylinder group from 47056 to
> > 46872
> > > > > to enlarge last cylinder group
> > > > > /dev/rsd1e: 367.7MB in 752992 sectors of 512 bytes
> > > > > 5 cylinder groups of 91.55MB, 5859 blocks, 11776 inodes each
> > > > > newfs: wtfs: write error on block 160: Input/output error
> > > > > /dev/rsd1d: 2144.1MB in 4391040 sectors of 512 bytes
> > > > > 11 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
> > > > > newfs: wtfs: write error on block 160: Input/output error
> > > > > Available disks are: sd0.
> > > > > Which disk do you wish to initialize? (or 'done') [done]
> > > >
> >
> >
