Hello,

i am new here and make my first steps with unraid. I've build a server with an Asrock ION T3 mini ITX, a fat power supply and some disks from stock. All disks are connected on a new AOC-SAS2LP-MV8-O-P. OS is ok, can reach the tower via browser an see the GUI. BUT....while booting the green lights on the supermicro board flashing a short time and go then dark. In the GUI i can see no disk. If the disks will connected on the onboard sata's, i can see them in the GUI.

Now i am a bit confused and would be very afraid about some 'input'.

 

greetings matze

It would be very helpful if you could post a syslog http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

fine, fast answers here

syslog attached, hope it is the correct one!

syslog.zip

See this in your syslog

Jan 10 11:22:41 Tower kernel: FAT-fs (sda1): error, fat_free_clusters: deleting FAT entry beyond EOF
Jan 10 11:22:41 Tower kernel: FAT-fs (sda1): Filesystem has been set read-only

This will prevent you from configuring anything on your system.

 

Put your flash drive in your PC and run checkdisk on it.

 

 

thank you, give me half an hour.....

New syslog attached, the samsung and the wd5000 are connected to onboard sata, otherwise nothing changes.

 

matze

syslog2.zip

In your syslog I see this every once in a while.  I'm not sure if that because the file is corrupted, or if its just never been created (ie: you've never started the array).  Perhaps someone more knowledgeable can pipe in.

 

Jan 10 12:07:19 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Jan 10 12:07:19 Tower kernel: md: could not read superblock from /boot/config/super.dat
Jan 10 12:07:19 Tower kernel: md: initializing superblock

 

But, I do have a question regarding the SAS2LP.  When you have drives connected to it, does it identify the drives connected to it during boot up?

super.dat contains the array configuration. Since it is not included in the Limetech download, I think it is probably created the first time the array is started.

the only thing i see on the SAS2LP is one red LED (after last reboot) and flashing green LEDs, one after the other, while booting the system

can i start the array without any detected disk?

and must the disks be empty or can they have content?

If you connect a monitor to the server, do you see during a cold boot the sas2lp's BIOS identifying the disks?

 

If you hit CTRL-M during the the identification process, do you see the attached drives?

 

For all we know, the controller isn't recognizing any attached disks at all (hence why unRaid wouldn't see them) due to a bad or wrong type of cable

during cold boot i see a message that contains some words about the marvell controller an so on, after that the system boots

in the tools/system devices i see the following -02:00.0 RAID bus controller: Marvell Technology Group Ltd. Device 9485 (rev c3)-

cables are these www.sona.de/.1939726910-Supermicro-CBL-0116L-Multilane-Breakout-Kabel-SFF8087-auf-4x-SATA

Maybe its just me, but I don't see whether those cables are forward breakout or reverse breakout  (you need forward to go from the card to the drives)

 

If you don't see something like this picture during bootup, then the card isn't recognizing the drives at all.  Either cables, bad card, possibly need to reflash, etc.

 

absolut nothing from this i can see

forward or reverse, are ther different cables?

If you don't see a list of the identified drives, then unRaid is not going to see the drives because as far as the controller card is concerned there are NO drives connected

 

Forward / Reverse Breakout cables look identical but are not the same.

 

Forward breakout go from the 8087 connector on your card to Sata connectors on the drives

 

Reverse breakouts go from Sata connectors on your motherboard to an 8087 connector on a hotswap backplane.

 

I tried looking at a number of different websites for those cables, and all I could see was multilane crossover.  Not sure what that exactly means in this case.  All the other manufacturers label them as either forward or reverse breakout.

From this post, it certainly appears that the cable you have is reverse breakout not forward

 

http://lime-technology.com/forum/index.php?topic=6982.msg67775#msg67775

ok, i think the same, the wrong cables are the reason for this (i hope so)

i will call my dealer on monday and ask for it

 

thank you for your trouble, i come back monday

 

good night!

 

matze

Ok, i'm back. Today the correct cables arrives. Within 5 minutes mounted, switched on the tower and

All HDD's where detected and on!

So thank you for trouble again and bye!

 

Matze