Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: SOLVED (maybe?) Re: Can't configure new disk



OH BOY!  I get dumber by the minute the card I had/have the disks plugged into is a Silicon Image SATALINK 3512 (not a Highpoint/Promise card).  The OS boot disk and the SSD are plugged into the motherboard directly.  The Hitachi disk is connected to the SATALink card and is currently not visible in /var/log/boot.dmesg.

On Sun, Mar 12, 2017 at 7:07 PM, pimin inwa <pimininca%gmail.com@localhost> wrote:


On Wed, Mar 1, 2017 at 12:59 PM, pimin inwa <pimininca%gmail.com@localhost> wrote:
Running:
NetBSD gemini.wan.vpn 6.99.31 NetBSD 6.99.31 (GEMINI) #0: Sun Feb 16 19:11:21 PST 2014  root@:/usr/src/BUILD_OBJ/sys/arch/i386/compile/GEMINI i386

From boot.dmesg I see:

wd0 at atabus4 drive 0
wd0: <ST31000528AS>
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: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1 at atabus4 drive 1
wd1: <Hitachi HDS721010CLA332>
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
wd1: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd1(piixide0:0:1): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
boot device: wd0
root on wd0a dumps on wd0b

I can't run fdisk, disklabel, etc ... because wd1d isn't configured?   ls shows:

# ls -l /dev/wd1*
brw-r-----  1 root  operator  0,      8 Feb  1  2014 /dev/wd1a
brw-r-----  1 root  operator  0,      9 Feb  1  2014 /dev/wd1b
brw-r-----  1 root  operator  0,     10 Feb  1  2014 /dev/wd1c
brw-r-----  1 root  operator  0,     11 Feb  1  2014 /dev/wd1d
brw-r-----  1 root  operator  0,     12 Feb  1  2014 /dev/wd1e
brw-r-----  1 root  operator  0,     13 Feb  1  2014 /dev/wd1f
brw-r-----  1 root  operator  0,     14 Feb  1  2014 /dev/wd1g
brw-r-----  1 root  operator  0,     15 Feb  1  2014 /dev/wd1h
brw-r-----  1 root  operator  0, 524296 Feb  1  2014 /dev/wd1i
brw-r-----  1 root  operator  0, 524297 Feb  1  2014 /dev/wd1j
brw-r-----  1 root  operator  0, 524298 Feb  1  2014 /dev/wd1k
brw-r-----  1 root  operator  0, 524299 Feb  1  2014 /dev/wd1l
brw-r-----  1 root  operator  0, 524300 Feb  1  2014 /dev/wd1m
brw-r-----  1 root  operator  0, 524301 Feb  1  2014 /dev/wd1n
brw-r-----  1 root  operator  0, 524302 Feb  1  2014 /dev/wd1o
brw-r-----  1 root  operator  0, 524303 Feb  1  2014 /dev/wd1p

What am I forgetting to do?

Thanks,
Paul


DUMB! DUMB! Me.  The drive was plugged into a HighPoint (Promise?) card.  Plugging the SSD into the motherboard SATA adapter and it is now recognized.  The add-on card seems to be IDE only??  Although the previous drives plugged into that card claim to be SATA.  

Thanks for all the help.

Paul



Home | Main Index | Thread Index | Old Index