Date: Tue, 17 Jan 2012 23:04:03 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Vinny Abello <vinny@abellohome.net>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0 and Intel MatrixRAID RAID5 Message-ID: <4F15E243.2030000@FreeBSD.org> In-Reply-To: <mailpost.1326821700.5568126.14545.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw> References: <CA%2BD9QhtZpPK%2Bqv%2BNg4b2Mc6wgwcdumiMH3LS-9e1dHHVe7Jp%2BQ@mail.gmail.com> <mailpost.1326821700.5568126.14545.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17.01.2012 19:03, Vinny Abello wrote: > I had something similar on a software based RAID controller on my Intel S5000PSL motherboard when I just went from 8.2-RELEASE to 9.0-RELEASE. After adding geom_raid_load="YES" to my /boot/loader.conf, it still didn't create the device on bootup. I had to manually create the label with graid. After that it created /dev/raid/ar0 for me and I could mount the volume. Only thing which I've trying to understand is the last message below about the integrity check failed. I've found other posts on this but when I dig into my setup, I don't see the same problems that are illustrated in the post and am at a loss for why that is being stated. Also, on other posts I think it was (raid/r0, MBR) that people were getting and trying to fix. Mine is (raid/r0, BSD) which I cannot find reference to. I have a feeling it has to do with the geometry of the disk or something. Everything else seems fine... I admittedly only use this volume for scratch space and didn't have anything important stor ed > on it so I wasn't worried about experimenting or losing data. > > ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 > ada0:<WDC WD4000YR-01PLB0 01.06A01> ATA-7 SATA 1.x device > ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 381554MB (781422768 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad4 > ada1 at ahcich1 bus 0 scbus3 target 0 lun 0 > ada1:<WDC WD4000YR-01PLB0 01.06A01> ATA-7 SATA 1.x device > ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 381554MB (781422768 512 byte sectors: 16H 63S/T 16383C) > ada1: Previously was known as ad6 > > GEOM_RAID: Intel-8c840681: Array Intel-8c840681 created. > GEOM_RAID: Intel-8c840681: Disk ada0s1 state changed from NONE to ACTIVE. > GEOM_RAID: Intel-8c840681: Subdisk ar0:0-ada0s1 state changed from NONE to ACTIVE. > GEOM_RAID: Intel-8c840681: Disk ada1s1 state changed from NONE to ACTIVE. > GEOM_RAID: Intel-8c840681: Subdisk ar0:1-ada1s1 state changed from NONE to ACTIVE. > GEOM_RAID: Intel-8c840681: Array started. > GEOM_RAID: Intel-8c840681: Volume ar0 state changed from STARTING to OPTIMAL. > GEOM_RAID: Intel-8c840681: Provider raid/r0 for volume ar0 created. > GEOM_PART: integrity check failed (raid/r0, BSD) > > Any ideas on the integrity check anyone? It is not related to geom_raid, but to geom_part. There is something wrong with your label. You may set kern.geom.part.check_integrity sysctl to zero do disable these checks. AFAIR it was mentioned in 9.0 release notes. > On 1/17/2012 6:57 AM, Matthias Gamsjager wrote: >> Not sure if geom_raid is implemented with cam. I remember a post a while >> back about this issue to happen with defaulting cam in 9. Did not follow it >> so not sure if something has been done about it. >> >> On Tue, Jan 17, 2012 at 11:53 AM, Alexander Pyhalov<alp@rsu.ru> wrote: >> >>> Hello. >>> On my desktop I use Intel MatrixRAID RAID5 soft raid controller. RAID5 is >>> configured over 3 disks. FreeBSD 8.2 sees this as: >>> >>> ar0: 953874MB<Intel MatrixRAID RAID5 (stripe 64 KB)> status: READY >>> ar0: disk0 READY using ad4 at ata2-master >>> ar0: disk1 READY using ad6 at ata3-master >>> ar0: disk2 READY using ad12 at ata6-master >>> >>> Root filesystem is on /dev/ar0s1. >>> Today I've tried to upgrade to 9.0. >>> It doesn't see this disk array. Here is dmesg. When I load geom_raid, it >>> finds something, but doesn't want to work with RAID: >>> >>> GEOM_RAID: Intel-e922b201: Array Intel-e922b201 created. >>> GEOM_RAID: Intel-e922b201: No transformation module found for Volume0. >>> GEOM_RAID: Intel-e922b201: Volume Volume0 state changed from STARTING to >>> UNSUPPORTED. >>> GEOM_RAID: Intel-e922b201: Disk ada2 state changed from NONE to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Subdisk Volume0:2-ada2 state changed from NONE >>> to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Disk ada1 state changed from NONE to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Subdisk Volume0:1-ada1 state changed from NONE >>> to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Disk ada0 state changed from NONE to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Subdisk Volume0:0-ada0 state changed from NONE >>> to ACTIVE. >>> GEOM_RAID: Intel-e922b201: Array started. >>> >>> No new devices appear in /dev. >>> How could I solve this issue? -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F15E243.2030000>