From: Evan Felix <evan.felix@pnl.gov>
To: Richard Scobie <richard@sauce.co.nz>
Cc: linux-raid@vger.kernel.org
Subject: Re: 3ware JBOD
Date: Mon, 01 Mar 2004 12:50:20 -0800 [thread overview]
Message-ID: <1078174220.3010.13.camel@e-linux> (raw)
In-Reply-To: <40429940.9000408@sauce.co.nz>
You will have to look In the bios setup screens to make sure all the
drives are in the 'Available Drives' Section. If I remember right they
have to be here to show up in linux as separate drives.
It may be holding the drives as 'previously used' and not as availible.
These options may be different as I think we have different Cards than
you.
Evan
On Sun, 2004-02-29 at 18:00, Richard Scobie wrote:
> I have a 3ware 7506-4LP with 4 x 250 which when first installed showed
> up in the system as SCSI devices sda-d.
>
> I built and tested various software RAID arrays on it, then decided to
> try various hardware arrays, which tested fine.
>
> Wishing to go back and build some more linux software arrays, I used the
> 3ware CLI utility to delete the array.
>
> Now, when I boot up, although all 4 drives show up in the 3ware BIOS,
> dmesg now shows:
>
> SCSI subsystem driver Revision: 1.00
> 3ware Storage Controller device driver for Linux v1.02.00.037.
> 3w-xxxx: No valid units for card 0.
> scsi0 : Found a 3ware Storage Controller at 0x7000, IRQ: 28, P-chip: 1.3
> scsi0 : 3ware Storage Controller.
>
> Can anyone please tell me how I get to see sda-d again?
>
> Regards,
>
> Richard
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-03-01 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 2:00 3ware JBOD Richard Scobie
2004-03-01 20:50 ` Evan Felix [this message]
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=1078174220.3010.13.camel@e-linux \
--to=evan.felix@pnl.gov \
--cc=linux-raid@vger.kernel.org \
--cc=richard@sauce.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).