On Tue, 01 May 2012 13:31:34 +0000, Camaleón wrote: > On Tue, 01 May 2012 11:53:27 +0000, Ramon Hofer wrote: > >> I'm using Debian Squeeze and would like to use a Supermicro >> AOC-SASLP-MV8 as controller for a software raid. Unfortunately the >> system crashes when I try creating a filesystem on the md device. > > JFYI, Google reports tons of problems with that card using mvsas driver > in linux, maybe you should consider using a different controller :-(
Thanks for your info. I wasn't aware of that :-( Can you recommend something better? It was very nice because it's quite cheap and I don't need a hardware raid card. >> And I can access the disks. Create an ext3 and ext4 filesystem on them >> seperately. But they don't like be be in the raid. >> >> When the system crashed I got this dmesg but I can't find anything in >> there: >> http://pastebin.com/raw.php?i=ZFdkcS8p > > There are some interesting entries there: > > [ 12.028337] md: md1 stopped. > [ 12.029374] md: bind<sdc> > [ 12.034155] md: bind<sdd> > [ 12.034275] md: bind<sdb> > [ 12.034986] raid5: device sdb operational as raid disk 0 [ > 12.034988] raid5: device sdc operational as raid disk 1 [ 12.035246] > raid5: allocated 3230kB for md1 [ 12.035270] 0: w=1 pa=0 pr=3 m=1 a=2 > r=3 op1=0 op2=0 [ 12.035272] 1: w=2 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0 > [ 12.035275] raid5: raid level 5 set md1 active with 2 out of 3 > devices, algorithm 2 [ 12.035378] RAID5 conf printout: > [ 12.035380] --- rd:3 wd:2 > [ 12.035382] disk 0, o:1, dev:sdb > [ 12.035383] disk 1, o:1, dev:sdc > [ 12.035406] md1: detected capacity change from 0 to 4000794542080 [ > 12.035940] md1: unknown partition table > > Those are related to md1 and your raid5 volume. And this looks ok or is there a problem? > [ 12.244499] PM: Starting manual resume from disk [ 12.244502] PM: > Resume from partition 8:3 [ 12.244503] PM: Checking hibernation image. > [ 12.244599] PM: Error -22 checking image file [ 12.244602] PM: > Resume from disk failed. > > And this comes from a resuming operation. Do you hibernate your system? No I don't. I usually do `sudo halt` to shut it off. But maybe I pressed the power button of the case before I collected the dmesg report. But usually I don't hibernate. >> On the screen I saw this: >> http://666k.com/u.php >> (Sorry it's a photograph) > > I can't load the image :-? Sorry I posted the wrong link. This one should work: http://666kb.com/i/c3f6nbmalagytqujw.jpg >> What else can I do? > > I would report it, although I'm afraid this is a well-known issue. Where should I report it? I've written a mail to Supermicro. Should I also create a Debian bug report? > Maybe you can try with an updated kernel to see if there's any > imprevement with the driver (mvsas) but to be sincere, I would be very > reluctant in setting a raid 5 level with a hard disk controller that is > not rock-solid, you are exposing your system to a data loss :-/ > >> There are Red Hat ad SUSE drivers and firmware on the Supermicro >> homepage. Should I take them from there? > > Sadly, Supermicro does not build binaries for Debian/Ubuntu but maybe > you can ask them for the sources to compile the driver by your own. I found this pages: ftp://ftp.supermicro.nl/driver/SAS/Marvell/MV8/SAS1/Driver/Linux/3.1.0.7/ But it doesn't seem as if it's what I need. And the supermicro support sent me the link to this zip file: ftp://ftp.supermicro.nl/driver/SAS/Marvell/MV8/SAS1/Firmware/3.1.0.21/ Firmware_3.1.0.21.zip It contains some win files and I have no clue what to do with them. So I hope I get an answer from them what to do with it... Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jnoshn$3u4$1...@dough.gmane.org
