I just treated all of the new 'greenish' drives as 4k - created GPT partitions and used gnop accordingly when building the zpool.
Am getting good performance on a 10 x 2TB raidz2. Using Samsung, Seagate, Hitachi & WD drives.
No problem - good luck.
Keep in mind like I said that quite a few people have had issues, etc getting the right combo of tools to do the flashing. This worked for me so hopefully helps you as well.
Do you mean the kernel's default 'mps' driver and LSI's 'mpslsi' driver?
If so, yes...just don't add anything to /boot/loader.conf and you'll be using the stock driver.
If there is an actual 'mpi' driver - I don't know what that is...once the card's are flashed only way to get them back to...
Here's procedure I used to setup FreeBSD boot-drive off of a 64GB Crucial SSD.
Mainly based off of this article a few others mentioned + a few other sources. http://www.ateamsystems.com/blog/FreeBSD-Partition-Alignment-RAID-SSD-4k-Drive
Was done during the system installation...exiting to...
I came over to this side of the fence mainly for ZFS. I found ZFS most attractive long-term filesystem in regards to its data integrity framework + hardware redundancy. If BTRFS wasn't still in petri dish we liklely wouldn't be having this conversation.
I'm not running any production services...
HDD's were at fault - both were failing smartctl parameters and longtests once looked into.
This did not make the mps driver for SAS2008 chipset happy, which in turn ZFS got fed-up and booted the HDD's from the array. This wasn't always the 2 faulty HDD's directly which is why it took me...
Yes - these cards work well...I had issues with 2 x defective HDD's causing instability, but once replaced has been very fast and stable cards to use. Notes on what I am using below:
[cpu] Intel Xeon E3-1220-V2
[mobo] Supermicro X9SCM-F (bios 2.0a)
[ram] (4x) Crucial CT51272BA1339 [4GB DDR3...
This is now SOLVED - thanks all for the assistance.
Turns out root cause of the issue was 2 of 10 dud HDD's. The dud drives each had approx 300 hours before problem popped up. One was 2TB Seagate ST2000DL003 and other was 2TB WD WD20EARX. They both had 'Current_Pending_Sector' and...
Forgive my ignorance please, but is it just a timing issue with the lack of the 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/' branch?
Does this typically get created sometime after a new RELEASE and its just not yet present hence all current 'pkg_add -r <package>'...
This is still in the TBD phase...have loaded the v15 mpslsi driver with both v14 and then v15 of the IT fw on the SAS2008 cards.
Still having issues, HOWEVER, I now have a CONFIRMED dead HDD after latest mpslsi freakout...it brutally fails both short and long smartctl tests - to be RMA'd...
Thanks Peetaur.
I have my SSD - Crucial M4 64GB (fw 000F) - running off the SATA3 port on the mobo so use-case here is different. I am going to try manually loading the new mpslsi module into 9.0-RELEASE and will let you know if it makes any difference for me as well.
In my case there is one...
@Sfynx, @gkontos
Thank you both for your reply.
I will try loading the LSI module manually for now - and potentially move up to 9.1-RELEASE once official. I have everything ready just need to test and will report back.
peetaur
So if I read your posts here correctly the only way you got your SSD's to operate correctly is by removing them from the LSI card?
I am having a similar issue with 3 x IBM M1015's and HDD's dropping out: http://forums.freebsd.org/showthread.php?t=36196
Did you find any other better...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.