[SOLVED] what /dev/device is associated with an Areca RAID card?

bucovaina78 · 12-31-2011, 05:42 AM

I'm running a computer with Windows 7 as a main OS. I've got Debian 6.0.3 installed on a separate partition since I prefer working with Debian myself. Anyway there is a big RAID Array running from an Areca card, partitioned as NTFS.

How can I find that out which device is associated with the raid array? Currently I'm running:

Code:

grep --ignore-case areca /proc/

(only feedback is not sufficient memory in /proc/kcore)

I already tried

Code:

fdisk -l

but it doesn't show up there

onebuck · 12-31-2011, 08:45 AM

Hi,

What do you see with 'lspci -vv'?

ongte · 12-31-2011, 08:55 AM

There's a kernel module 'arcmsr' that supports most of the Areca RAID cards.
See if this is loaded with

Code:

# lsmod | grep arcmsr

If not, just load it with

Code:

# modprobe arcmsr

bucovaina78 · 12-31-2011, 10:24 AM

Well it does show up in the lspci w/o -vv so it's recognized. If you still need the output I'll post it later on (the ol' folks are working on the pc now)

I can't seem to find a block device that I can use to mount. On the top of my head I did:

Code:

user@box:~$ ls /sys/block
loop0  loop1  loop2  loop3  loop4  loop5  loop6  loop7  sda  sdb sdc sdd sde sdf
user@obx:~$

If I try to 'cat' the last 4 devices I got an error and no output so that's not the 4 disks attached to the controller. With the sda and sdb (being 2 physical present discs) I got the expected "messy" output.

ongte · 01-03-2012, 02:07 AM

lspci just shows whatever is plugged in. It doesn't mean it's detected and working. With the -vv option you might see if a kernel module has been loaded to support it.

onebuck · 01-03-2012, 08:46 AM

Hi,

Quote:

Originally Posted by ongte

lspci just shows whatever is plugged in. It doesn't mean it's detected and working. With the -vv option you might see if a kernel module has been loaded to support it.

Just one of the commands that can help identify things to aid in troubleshooting. Sometimes errant loads or misconfiguration can be identified.

bucovaina78 · 01-04-2012, 05:35 AM

sorry for the late response. Here's the output of lspci -vv

Code:

root@media:# lspci -vv | grep --ignore-case areca --after-context 32
02:00.0 RAID bus controller: Areca Technology Corp. ARC-1680 8 port PCIe/PCI-X to SAS/SATA II RAID Controller
	Subsystem: Areca Technology Corp. Device 1212
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at fa610000 (32-bit, non-prefetchable) [size=8K]
	Expansion ROM at fa600000 [disabled] [size=64K]
	Capabilities: [98] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [d0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 <1us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 256 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x8, ASPM unknown, Latency L0 <128ns, L1 unlimited
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Kernel driver in use: arcmsr

bucovaina78 · 01-04-2012, 08:40 AM

Might be of help, the output of

Code:

dmesg | grep scsi

Code:

user@media:~$ dmesg | grep scsi
[    1.535446] scsi0 : Areca SAS Host Adapter RAID Controller( RAID6 capable)
[    1.537905] scsi 0:0:0:0: Direct-Access     Areca    ARC-1212-VOL#000 R001 PQ: 0 ANSI: 5
[    1.538561] scsi 0:0:16:0: Processor         Areca    RAID controller  R001 PQ: 0 ANSI: 0
[    1.541807] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.541826] scsi 0:0:16:0: Attached scsi generic sg1 type 3
[    1.754821] scsi1 : ahci
[    1.754855] scsi2 : ahci
[    1.754887] scsi3 : ahci
[    1.754918] scsi4 : ahci
[    1.754948] scsi5 : ahci
[    1.754979] scsi6 : ahci
[    1.755291] scsi7 : ahci
[    1.755329] scsi8 : ahci
[    1.755611] scsi9 : ahci
[    1.755650] scsi10 : ahci
[    2.114477] scsi 2:0:0:0: CD-ROM            HL-DT-ST BD-RE  BH10LS30  1.00 PQ: 0 ANSI: 5
[    2.114593] scsi 2:0:0:0: Attached scsi generic sg2 type 5
[    2.643005] scsi 10:0:0:0: Direct-Access     ATA      INTEL SSDSA2CW08 4PC1 PQ: 0 ANSI: 5
[    2.643078] sd 10:0:0:0: Attached scsi generic sg3 type 0
[    2.649437] scsi11 : SCSI emulation for USB Mass Storage devices
[    2.672746] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.672860] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    7.644671] scsi 11:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
[    7.645170] scsi 11:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
[    7.645668] scsi 11:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
[    7.646167] scsi 11:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
[    7.646401] sd 11:0:0:0: Attached scsi generic sg4 type 0
[    7.646467] sd 11:0:0:1: Attached scsi generic sg5 type 0
[    7.646539] sd 11:0:0:2: Attached scsi generic sg6 type 0
[    7.646625] sd 11:0:0:3: Attached scsi generic sg7 type 0
user@media:~$

Code:

root@media:/home/user# mount /dev/sg0 /mnt/RAID/
mount: /dev/sg0 is not a block device

(I tried all from /dev/sg0 to /dev/sg8)

bucovaina78 · 01-05-2012, 07:24 AM

Is just over 24h too soon to bump?

ongte · 01-05-2012, 09:21 AM

Try /dev/da?

lithos · 01-05-2012, 09:39 AM

Hi,

It could be that you need fuse-3g 'driver' for mounting NTFS volume.
Like mounting ntfs in debian/
or maybe here (more explanation)

good luck

bucovaina78 · 01-05-2012, 04:24 PM

Quote:

Originally Posted by lithos

Hi,

It could be that you need fuse-3g 'driver' for mounting NTFS volume.
Like mounting ntfs in debian/
or maybe here (more explanation)

good luck

Spot on Lithos!!!

I downloaded the latest stable fuse (2.8.5 I thought it was) and did ./configure && make && make install && reboot

I've got a new device /dev/sda and I could mount it!!

Can someone explain why the device didn't show up at first?