dynamis_dk

I do have another few 4TB drives which I could pre-clear and use to rebuild disk1 but these disk are to become part of a 2nd server I'm building I with the plan of it being offsite and just bring it around once a month so if I use up a 4TB drive to rebuild disk1, I would want that back would as some point for the new server ideally so I'm presuming I would then just be in a position where I'd need to use the New Config tool to remove it down the line and would be in the same position without protection until the rebuild completed? As I've added 4TB storage (as I needed somewhere to copy my existing RFS 4TB data to), I had planned by the end to be able to remove 2x 2TB drives to remove some of the oldest disks leaving me with 1x Parity 4TB, 2x 4TB data disk and 3x 2TB giving me 14TB total which is the same as I started with. I have about 3.5TB free before starting this process so that arrangement would work fine and if I need more space in the future, I can upgrade both the main server and backup server at the same time to keep the total space the same. Sorry I never thought to mention plans for the 2nd server and what impact that may have to my options. This 2nd server will have a 6TB parity, 1x 6TB data and 2x 4TB data. Sadly disk1 isn't detecting at bios level so I think its just packed in completely, its making start-up sounds when powered but isn't detected and I've tried different cables, ports etc. I think its about 10yo so Its not done too bad so I think I'll just bid him farewell as I'm not sure I'd trust is even if it did start to detect again.

Hi, Its been a while as I've had my server down during decorating for around 6 months so on powering everything back up again I had OS upgrades to do, apps to upgrade etc and as part of it setup the common issues / fix app. On its advise I'm working on converting all my RFS disks to XFS. At the start my Parity is 4TB, one 4TB data disk and rest 2TB (5). I've installed a new pre-cleared 4TB to allow me to copy from existing 4TB, then i'd work down the 2TB drives like follows: Disk 7 (new disk formatted as XFS) Disk 4 (RFS 4TB) -> Disk 7 (4TB XFS) Disk 2 (RFS 2TB)-> Disk 4 (Now XFS 4TB) Disk 1 (RFS 2TB)-> Disk 4 (Now XFS 4TB) My plan was to replace disk 1 as it is fairly old so moved data from Disk 2 and Disk 1 onto the 4TB thinking Disk 1 could be removed and Disk 2 formatted to XFS to carry on the cycle. Towards the end of copying Disk 1 is redballed on me and as it was copying overnight I didnt notice until the morning so the copy process completed onto Disk 4 using emulated data. I've checked the hashes of the data copy from Disk 1 to Disk 4 and everything looks ok so I don't believe its caused an issue but I'm not really sure how best to get back to protected without emulation and carry on the move to XFS. Can I remove Disk 1 completely from the setup, allow it to build whatever parity it needs to again and then stop array, change Disk 2 to XFS and carry on? If so can someone outline the steps please? I've seen a few threads mention using new confg tool but I didn't want to start hitting buttons before getting advise on what I'm doing. I've been pretty lucky with Unraid over the years and I've needed to do very little to keep it going and I've only had a couple failures which were straight replacements but this ease of use has left me with little in the way of troubleshooting / fixing skills

Awesome, Cheers JorgeB, I'll leave well alone for now and just bookmark this thread just in case

Hi, I'm in the process of giving my unraid server a once over as I've had an old drive die and overall I've been fairly lucky over the years so I'm figuring out the process etc. I stumbled upon this thread via another users thread for support where someone noted via the syslog that their SAS controller was on an old firmware so it made me wonder about mine. I've been able to download the files etc as outlined in your guidelines and I've been left with the following so I know there is a newer update available for my card - question is, should I? Would you recommend always updating to latest firmware or is there an element of 'if its not broke, don't fix it'? Its one of the IBM 1015 cards Adapter Selected is a LSI SAS: SAS2008(B2) Controller Number : 0 Controller : SAS2008(B2) PCI Address : 00:02:00:00 SAS Address : 500605b-0-0474-f290 NVDATA Version (Default) : 0f.00.00.05 NVDATA Version (Persistent) : 0f.00.00.05 Firmware Product ID : 0x2213 (IT) Firmware Version : 15.00.00.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9211-8i BIOS Version : N/A UEFI BSD Version : N/A FCODE Version : N/A Board Name : SAS9211-8i Board Assembly : N/A Board Tracer Number : N/A Finished Processing Commands Successfully. Also, does the provided sasXflash version in the download from broadcom depend on the hardware its for as your guide mentions sas3flash but i've got sas2flash and it would seem to be working. many thanks

Thanks for the very quick answer - I Think given servers only got around 8gb free i'm really needing the space, and being a new drive out the bag i'll get it assigned. I too hope one day they make a standard if thats not the case - hard to believe i'm an IT tech by day lol Cheers Dave

Well done my first pre_clear on a brand new 1TB drive. As putting it off until i'd finished work on the case the server will live in but i'm short on space so needed to use it now. All went fine, a lot easier than i was expecting since i count myself as a bit of a unix'y noob. Few things on the SMART side i want to run over tho: at the end of the pre_clear i got a output of SMART stats, everything is on 'OK' for status but 2 have 'near_thresh' and am not sure if this should be a worrying sign. The two in question are: Spin_Retry_Count (New_Val=100, Old_Val=100, Failure_Threshold=97, Status=near_Thresh, Raw_Value=0) End-To-End_Error (New_Val=100, Old_Val=100, Failure_Threshold=99, Status=near_Thresh, Raw_Value=0) What does the near_thresh mean?? I would take this liturally saying something is near is threshold which in my mind would ring alarm bells Given my lack of real knowledge on SMART attributes can someone advice before i assign this drive for data.