Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

scsictl equivalent for SATA

1 view
Skip to first unread message

Edgar Fuß

unread,
Aug 1, 2011, 6:43:03 AM8/1/11
to
I've got a hot-pluggable SATA drive in a RAID1 that failed.
I've never been into this with SATA, only with SCA.
What do I do after physically replacing the drive to make the new one known to the kernel?
I do know how to re-build the RAID, but what's the analogous to scsictl detach/scan?

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

Manuel Bouyer

unread,
Aug 1, 2011, 8:04:27 AM8/1/11
to
On Mon, Aug 01, 2011 at 12:43:03PM +0200, Edgar Fu� wrote:
> I've got a hot-pluggable SATA drive in a RAID1 that failed.
> I've never been into this with SATA, only with SCA.
> What do I do after physically replacing the drive to make the new one known to the kernel?
> I do know how to re-build the RAID, but what's the analogous to scsictl detach/scan?

There is none at this time (unless something changed recently I didn't
notice). But if you plugged the new drive in the same slot as the old
one, you should be able to use it without extra steps.

--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--

Edgar Fuß

unread,
Aug 1, 2011, 8:18:36 AM8/1/11
to
> But if you plugged the new drive in the same slot as the old
> one, you should be able to use it without extra steps.
In the meantime, I figured out that the supposedly failed drive is OK.
There seems to be something wrong with the SATA channel it was attached to:

[...]
svwsata0 at pci1 dev 14 function 0
svwsata0: ServerWorks HT-1000 SATA Controller (rev. 0x00)
: DMA
svwsata0: using ioapic0 pin 11 (irq 11) for native-PCI interrupt
svwsata0: primary channel wired to native-PCI mode
atabus0 at svwsata0 channel 0
[...]
svwsata0 port 0: device present, speed: 1.5Gb/s
[...]
wd0 at atabus0 drive 0: <ST3250310NS>
wd0: quirks 2<FORCE_LBA48>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 232 GB, 484521 cyl, 16 head, 63 sec, 512 bytes/sect x 488397168 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(svwsata0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
svwsata0 port 1: PHY offline
[...]
svwsata0:0:0: lost interrupt
type: ata tc_bcount: 16384 tc_skip: 0
svwsata0:0:0: bus-master DMA error: missing interrupt, status=0x21
svwsata0:0:0: device timeout, c_bcount=16384, c_skip0
wd0a: device timeout writing fsbn 61002880 of 61002880-61002911 (wd0 bn 61002943; cn 60518 tn 12 sn 43), retrying
svwsata0 channel 0: reset failed for drive 0

Also ``atactl /dev/atabus0 reset'' also resulted in ``reset failed''.
How do I fix this short of re-booting the machine?

Paul Goyette

unread,
Aug 1, 2011, 8:19:30 AM8/1/11
to
drvctl should work for you - this was added in the last couple of
months.

On Mon, 1 Aug 2011, Manuel Bouyer wrote:

> On Mon, Aug 01, 2011 at 12:43:03PM +0200, Edgar Fuß wrote:
>> I've got a hot-pluggable SATA drive in a RAID1 that failed.
>> I've never been into this with SATA, only with SCA.
>> What do I do after physically replacing the drive to make the new one known to the kernel?
>> I do know how to re-build the RAID, but what's the analogous to scsictl detach/scan?
>

> There is none at this time (unless something changed recently I didn't
> notice). But if you plugged the new drive in the same slot as the old
> one, you should be able to use it without extra steps.
>
> --
> Manuel Bouyer <bou...@antioche.eu.org>
> NetBSD: 26 ans d'experience feront toujours la difference
> --
>

> !DSPAM:4e3696682351153699719!
>
>
>

-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer | | pgoyette at netbsd.org |
-------------------------------------------------------------------------

Edgar Fuß

unread,
Aug 1, 2011, 8:29:09 AM8/1/11
to
> drvctl should work for you - this was added in the last couple of
> months.
The server in question is on 4.0.1.

Manuel Bouyer

unread,
Aug 1, 2011, 8:58:12 AM8/1/11
to

I would try to unplung/replug the drive.
I would also look at SMART datas (using the smartmontool package, atactl from
4.0 won't report all details).

--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--

--

Edgar Fuß

unread,
Aug 1, 2011, 9:06:30 AM8/1/11
to
> I would try to unplung/replug the drive.
I already did that.

> I would also look at SMART datas (using the smartmontool package, atactl from
> 4.0 won't report all details).

OK, I'll re-attach the drive to another machine. I already did attach it to a desktop machine to check it does spin up (you can't tell in the server room because of the ambient noise) and it started to boot.

Manuel Bouyer

unread,
Aug 2, 2011, 9:49:01 AM8/2/11
to
On Tue, Aug 02, 2011 at 02:53:11PM +0200, Edgar Fu� wrote:
> > OK, I'll re-attach the drive to another machine.
> I did that and the SMART status is OK.
>
> So, anything short of re-booting the server to unlock the locked up SATA port? I'll be losing 455 days of uptime!

I'd see if it reacts to reset again after replugging in the initial slot.
If it does not, I fear a reboot in required.

--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--

--

Edgar Fuß

unread,
Aug 2, 2011, 8:53:11 AM8/2/11
to
> OK, I'll re-attach the drive to another machine.
I did that and the SMART status is OK.

So, anything short of re-booting the server to unlock the locked up SATA port? I'll be losing 455 days of uptime!

--

0 new messages