3 messages in org.freebsd.freebsd-scsiRe: Controller Timed on a Hard Disk| From | Sent On | Attachments |
|---|---|---|
| Fanying Jen | Jun 17, 2000 11:08 am | |
| Mike Smith | Jun 17, 2000 11:41 am | |
| Wilko Bulte | Jun 17, 2000 12:03 pm |
| Subject: | Re: Controller Timed on a Hard Disk | |
|---|---|---|
| From: | Wilko Bulte (wk...@chello.nl) | |
| Date: | Jun 17, 2000 12:03:10 pm | |
| List: | org.freebsd.freebsd-scsi | |
On Sat, Jun 17, 2000 at 11:41:37AM -0700, Mike Smith wrote:
I finally got vinum to work, it turned out to be a bad hard disk. However, once I took the bad disk offline, another disk begins to acted up. Here is the diagram of the scsi chain.
cindy.fynet.com fanying.fynet.com [T] [T] / \ [AHA 2940UW]=== ===[AHA 2940UW] \ / --[WDE9100 (0)]--[WDE9100 (1)]--
The disk that is now acting up is WDE9100(1) and it is giving the error message below. I am wondering why is FreeBSD keep on hiccuping whereas Linux doesn't complain at all?
You don't say what you've set the IDs of the controllers to in this diagram. As a general rule, though, I think that what you're trying to do is probably not going to be possible (I see signs of "I can share this array between two machines" thinking above).
Assuming (e.g.) ID6 and 7 for the 2 Adaptecs it should work as far as SCSI goes. I don't like the use of SE SCSI for clustering-like setups but...
If you have a RAID array that can present multiple LUNs / storagesets you can give each machine it's own storage to bang onto. You are of course right in saying that just hooking up 2 machines to the same disk is a no-no (maybe you can get away with giving each machine it's own part[ition] of the disk
-- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wil...@freebsd.org http://www.nlfug.nl - Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message