On Thu, Dec 18, 2014 at 06:40:48PM -0500, MLH wrote: > > I recently installed amd64 current NetBSD 7.99.3 (GENERIC) #0 Mon > Dec 15 on a new disk running FFSv2: > > wd0 at atabus3 drive 0 > wd0: <ST1000DM003-1ER162> > wd0: drive supports 16-sector PIO transfers, LBA48 addressing > wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors > wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) > wd0(ahcisata1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 > (Ultra/133) (using DMA) > > file system: /dev/rwd0a > format FFSv2 > endian little-endian > > I have the same version of i386 current (NetBSD 7.99.3 (GENERIC) > Mon Dec 15 running on FFSv1 > > wd1 at atabus4 drive 0 > wd1: <ST500DM002-1BC142> > wd1: drive supports 16-sector PIO transfers, LBA48 addressing > wd1: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors > wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) > wd1(ahcisata1:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 > (Ultra/133) (using DMA) > > file system: /dev/rwd1a > format FFSv1 > endian little-endian > > The i386 version can access and mount both drives but the amd64 > version can't access the FFSv1 drive above. Any attempt to access > it results in "Device not configured", as in: > > $ disklabel wd1 > wd1: Device not configured
that's certainly not an ffsv1 vs ffsv2 issue; disklabel doesn't care. What does ls -l /dev/rwd1d show ? -- Manuel Bouyer <[email protected]> NetBSD: 26 ans d'experience feront toujours la difference --
