From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan <alan@clueserver.org>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org
Subject: Re: Question on siig sata 3 controller
Date: Tue, 15 Jun 2010 16:53:42 +0200 [thread overview]
Message-ID: <20100615145342.GC26989@bitwizard.nl> (raw)
In-Reply-To: <20100615110748.4303a106@lxorguk.ukuu.org.uk>
On Tue, Jun 15, 2010 at 11:07:48AM +0100, Alan Cox wrote:
> > A reboot brings the disks back to life. So in theory, Linux should be
> > able to restore life into these drives by doing the right magic with
> > the hardware bits...
> We don't have power control of the drives. If the firmware crashes
> or a drive flakes out due to power problems or something similar
> occurs its game over until you hit the switch.
The thing is, the power didn't cycle. I just typed "reboot" from a
remote location. (Yes, in most cases leading up to yesterday's/this
morning's event I thought I had to powercycle to bring them back, but
I tried "just the reboot" this morning and it worked!)
The controller has TWO drives connected. BOTH drives became
inaccessible at exactly the same point in time. This has happened
before, with BOTH drives disappearing at the same moment.
The RAID superblocks on BOTH drives had info like:
RAID disk 1/8, raid is up 8/8
say for disk numbers 1,2.
All six other drives had
RAID disk 4/8, raid is broken 6/8
say, for disk numbers 0, 3,4,5,6,7
Next time this happens, I'll try removing and reinserting all the sata
modules (the machine is a file-server. It's NFS-root so it doesn't
depend on the storage modules for it's root fs.... :-) )
sata_nv 20758 0
ahci 36037 6
Is one of these modules the driver for this controller? I think it's
AHCI: lshw says it uses ports cc00 ... and a bunch of others, and
those ports are claimed by ahci according to /proc/ioports. Ah! I need
better eyes. lshw already mentions that it's ahci...
> > ata5: hard resetting link
> > ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 370)
>
> We tried the biggest hammer we had
Not big enough! De BIOS manages a bigger one!
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2010-06-15 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 4:39 Question on siig sata 3 controller Alan
2010-06-10 8:53 ` Jeff Garzik
2010-06-10 16:28 ` alan
2010-06-11 2:08 ` Alan
2010-06-15 6:57 ` Rogier Wolff
2010-06-15 10:07 ` Alan Cox
2010-06-15 14:53 ` Rogier Wolff [this message]
2010-06-15 15:01 ` Alan Cox
2010-06-15 17:25 ` Alan
2010-08-10 13:48 ` Rogier Wolff
2010-08-12 0:27 ` alan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100615145342.GC26989@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@clueserver.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox