17 messages in org.freebsd.freebsd-scsiRe: Invalidating pack messages| From | Sent On | Attachments |
|---|---|---|
| Nick Slager | Jun 20, 2000 12:27 am | |
| Don Lewis | Jun 20, 2000 12:53 am | |
| Scott Donovan | Jun 20, 2000 1:51 am | |
| Nick Slager | Jun 20, 2000 1:59 am | |
| Nick Slager | Jun 20, 2000 2:02 am | |
| Ian West | Jun 20, 2000 7:48 am | |
| Nick Slager | Jun 20, 2000 9:35 pm | |
| Don Lewis | Jun 22, 2000 12:29 am | |
| Steve Passe | Jun 22, 2000 2:27 am | |
| Don Lewis | Jun 22, 2000 2:33 am | |
| Steve Passe | Jun 22, 2000 2:40 am | |
| Nick Slager | Jun 23, 2000 12:38 am | |
| Wilko Bulte | Jun 23, 2000 10:12 am | |
| Thomas Zenker | Jun 26, 2000 2:08 am | |
| Nick Slager | Jun 26, 2000 10:45 pm | |
| Thomas Zenker | Jun 28, 2000 1:03 am | |
| Nick Slager | Jun 28, 2000 5:43 am |
| Subject: | Re: Invalidating pack messages | |
|---|---|---|
| From: | Nick Slager (nic...@albury.net.au) | |
| Date: | Jun 20, 2000 1:59:30 am | |
| List: | org.freebsd.freebsd-scsi | |
Thus spake Don Lewis (Don....@tsc.tdk.com):
On Jun 20, 5:28pm, Nick Slager wrote: } } I have swapped out, individually, one at a time, each component of the SCSI } subsystem - controller, cable, drive and terminator. I'm still getting the } error message.
You left out the power supply and power cable to the drive.
A good point; I'll swap power supplies tomorrow. Thanks for the suggestion.
I believe this error means that the drive has gone away (power failure) and come back (and has told FreeBSD that it has freshly powered up) in such a way that FreeBSD has no way to tell if the drive it was talking to before is the same drive that it is talking to now. To avoid severe filesystem damage, FreeBSD prevents further access to the drive.
Imagine the havoc you could cause by unplugging a drive that held a mounted filesystem that was being written to and hooking up another drive containing important data in its place if FreeBSD didn't detect this condition.
Yes, this would certainly be sub-optimal.
The sporadic nature of this fault has been particularly frustrating. Often the system will run fine, all the time doing hefty reads/writes to various parts of the filesystem, for a whole day before it dies.
One more thing I meant to mention in the original post: when the error occurs the small green LED on the front of the drive flashes in a peculiar pattern. It's hard to record exactly *what* the pattern is, as I have no reference point and the sequence is fairly lengthy.
Seagate support insist they have no idea what the pattern represents, and "not even an engineer would know". Needless to say, it's not in the manual for the drive. :-(
Has anyone come across a reference to the LED flash patterns on Seagate drives?
Regards,
Nick.
-- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey."
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message