New user on FreeNAS - Need advice

Status
Not open for further replies.

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Yeah, Dell sucks with all their fricking letters after the model number. Like if Toyota called their Corolla the Car6/r, the Highlander the Car6/B, and the Tundra the Car6/XB.
 

KernnK

Dabbler
Joined
Jan 26, 2016
Messages
11
Thanks for all this advices .

I will buy PERC H200 to replace the 6/i RAID controller. :)
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
I will buy PERC H200 to replace the 6/i RAID controller

Make sure you get the correct cables as well. I think the SAS 6/IR uses SFF-8484 connectors while the H200 has mini-SAS (SFF-8087?) connectors, you will need to ensure you get the proper cabling. Not sure about the backplane on the PowerEdge R510 and what its connectors are; but since you have it in hand... :D
 

KernnK

Dabbler
Joined
Jan 26, 2016
Messages
11
Hi !

It's me, again.

I have set up my new H200 in my R510 and i flasheded the firmware with LSI IT P20. Thanw for your advice.

[root@freenas] ~# sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

Adapter Selected is a LSI SAS: SAS2008(B1)

Controller Number : 0
Controller : SAS2008(B1)
PCI Address : 00:02:00:00
SAS Address : 5842b2b-0-45bb-1c00
NVDATA Version (Default) : 14.01.00.08
NVDATA Version (Persistent) : 14.01.00.08
Firmware Product ID : 0x2213 (IT)
Firmware Version : 20.00.04.00
NVDATA Vendor : LSI
NVDATA Product ID : SAS9211-8i
BIOS Version : 07.39.00.00
UEFI BSD Version : 02.00.01.09
FCODE Version : N/A
Board Name : PERC H200I
Board Assembly : N/A
Board Tracer Number : N/A

Finished Processing Commands Successfully.
Exiting SAS2Flash.

The solution seems functional and disk are recognized at boot.

I have create 2 RAIDZ of 4 disk fort test.

But when i want make a test to replacing à failed drive (here da0) , i stop the device by the menu (Storage -> Volumes -> View Volumes -> “Offline” button) then i physically removed the disk.

/var/log/message :

Feb 17 13:22:02 freenas GEOM_ELI: Device da0p1.eli destroyed.
Feb 17 13:22:36 freenas mps0: mpssas_prepare_remove: Sending reset for target ID 0
Feb 17 13:22:36 freenas da0 at mps0 bus 0 scbus0 target 0 lun 0
Feb 17 13:22:36 freenas da0: <ATA WDC WD20EZRZ-00Z 0A80> s/n WD-WCC4M5JZ69R3 detached
Feb 17 13:22:36 freenas (da0:mps0:0:0:0): Periph destroyed
Feb 17 13:22:36 freenas mps0: IOCStatus = 0x4b while resetting device 0x9
Feb 17 13:22:36 freenas mps0: Unfreezing devq for target ID 0

But when i place the new disk in remplacement, it's not recognize automaticaly by the system (FreeNAS does not offer this alternative drive in the menu) and i must reboot the system for the disk is view.

Strangly, if i make the choice of not rebooting my system, when i execute the utility : /libexec/script# sas2ircu LIST, the system discovered the disk da0 :

[root@freenas] /libexec/script# sas2ircu LIST
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.


Adapter Vendor Device SubSys SubSys
Index Type ID ID Pci Address Ven ID Dev ID
----- ------------ ------ ------ ----------------- ------ ------
0 SAS2008 1000h 72h 00h:02h:00h:00h 1028h 1f1eh
SAS2IRCU: Utility Completed Successfully.

/var/log/message :

Feb 17 17:43:29 freenas mps0: Calling Reinit from mps_wait_command
Feb 17 17:43:29 freenas mps0: Reinitializing controller,
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Warning: io_cmds_active is out of sync - resynching to 0
Feb 17 17:43:30 freenas mps0: Firmware: 20.00.04.00, Driver: 20.00.00.00-fbsd
Feb 17 17:43:30 freenas mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
Feb 17 17:43:30 freenas mps0: mps_reinit finished sc 0xfffffe0000ac6000 post 4 free 3
Feb 17 17:43:30 freenas mps0: Reinit success
Feb 17 17:43:30 freenas mps0: mps_user_pass_thru: invalid request: error 60
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 45703d45c8adb093
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 45703d45c8adb093
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 45713742c6acaa95
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 45713742c6acaa95
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 45703a45c5b3b093
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 45703a45c5b3b093
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 7e9536239eab8f8f
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 7e9536239eab8f8f
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 898637209f9f988a
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 898637209f9f988a
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 898637209fa0958b
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 898637209fa0958b
Feb 17 17:43:32 freenas mps0: SAS Address for SATA device = 8986371fa1a6968b
Feb 17 17:43:32 freenas mps0: SAS Address from SATA device = 8986371fa1a6968b
Feb 17 17:43:33 freenas mps0: SAS Address for SATA device = 45703d45c8b3a996
Feb 17 17:43:33 freenas mps0: SAS Address from SATA device = 45703d45c8b3a996
Feb 17 17:43:38 freenas da0 at mps0 bus 0 scbus0 target 7 lun 0
Feb 17 17:43:38 freenas da0: <ATA WDC WD20EARX-00P AB51> Fixed Direct Access SCSI-6 device
Feb 17 17:43:38 freenas da0: Serial Number WD-WCAZAD674170
Feb 17 17:43:38 freenas da0: 600.000MB/s transfers
Feb 17 17:43:38 freenas da0: Command Queueing enabled
Feb 17 17:43:38 freenas da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
Feb 17 17:43:38 freenas da0: quirks=0x8<4K>

The raid seems OK and online, but i has this alerte in Freenas : CRITICAL: Device: /dev/da0 [SAT], unable to open device.

Someone has an explanation ? Do you know why my disk is not automatticaly recognized (in hotplug) ?

Thanks by advance.
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
But when i place the new disk in remplacement
Does your system actually support "Hot Swap"? If not, I would suggest either shutting the machine down prior to manually replacing the drive or at least have a drive already in there (either as a "Warm Spare" or just not configured).

Also, are you using the same drive to emulate the remove/replace? If so, then you may need to "Wipe" the drive first before trying to add it back.
 

KernnK

Dabbler
Joined
Jan 26, 2016
Messages
11
Hi Mirfster,

Thanks for your answer.

Yes, i think because when i have executed the sas2ircu utility, the controller give à new SAS Address for SATA device and after system can view the disk without make a reboot.

I can see an alert in GUI FreeNas, but the POOL is not considerer like degraded and the new disk is "Online".

I have already wipe the new disk before, And i use 2 different disk to emulate the remove/replace. :/
 

KernnK

Dabbler
Joined
Jan 26, 2016
Messages
11
After reboot the message is cleared. But in my production environnement, i can't reboot the server (the service must continue 24/7). :/
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
But in my production environnement, i can't reboot the server (the service must continue 24/7). :/
So on a Production machine you are manually disconnecting drives in a system that does not have "Hot Swap" capabilities? If so, that doesn't make sense. Should be able to schedule down-time... :)
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
If your system properly supports hot swap you don't need to reboot. And with a normal non hot swap replace procedure you only have to reboot once.
 

KernnK

Dabbler
Joined
Jan 26, 2016
Messages
11
Hi ,

Thanks for your replies . But, i dont understand why disk is not autodetected by the system... I may be wrong, but it seems to me abnormal.

My hardware should be supporting the hot swap, because when i use the utility "sas2ircu LIST", the controller is reinitialized and the disk is detected with no reboot ( you can see my log file in my reply of Friday at 12:36 AM).

But when i choose to use this alternative method for detect the disk , i get the message alert in GUI, like in my last reply. However , the disk is well built and is the zpool online .

I use the backplane R510 with Perc H200 and Firmware LSI P20. There would not be a compatibility issue ? Nobody has had the same problem ?
 
Status
Not open for further replies.
Top