TUMS

Last checked on Wed 11 May 2016 05:39:02 AM MST (two days ago), finding 0 errors. Duration: 18 hours, 53 minutes, 30 seconds. Average speed: 117.7 MB/sec I've got mostly all 8TB & 4TB wd reds, dual parity. My smallest HDD is 4TB.

Thanks garycase, agree totally. I just don't want to throw away perfectly good drives when I don't have to for a few bad sectors. Sometimes it's hard to tell how long a drive is going to last if all that's showing bad in smart is reallocated sectors. I've had drives with 50+ reallocated sectors (in desktop pc's) and they still operated just fine for months/years afterwords. One nice thing about having a backup server, takes a little bit of the pressure off. You can afford to take a few more risks than you would otherwise.

what is the point in leaving a dead drive in the array. Once you get any write errors to a drive unRAID will stop writing to it so no point in keeping it in the array. You also increase the chance of encountering a multiple drive failure scenario which will lead to data loss. . I meant keeping it in till it dies. As in reallocated sectors could go into the 100's and you'd still keep running with it. my experience is that if the reallocated sectors keeps growing then the drive is likely to fail. There is nothing intrinsically wrong with having a significant number of reallocated sectors as long as the number stays relatively stable. It is regular increases which are a sign of trouble. As has been mentioned of far more importance is the value for pending sectors as any non-zero value means you may not be able to recover a different disk that fails without some level of data corruption Thanks. I'd probably be tempted to run it up into the 100's (reallocated sectors) if I had dual parity. I mean if I can get a few more months out of the drive then hell, why not. Especially if I had a backup server. Without that I wouldn't try it. Also depends if the drive is still under warranty or not, if it is, probably best to get it replaced sooner rather than later.

what is the point in leaving a dead drive in the array. Once you get any write errors to a drive unRAID will stop writing to it so no point in keeping it in the array. You also increase the chance of encountering a multiple drive failure scenario which will lead to data loss. I meant keeping it in till it dies. As in reallocated sectors could go into the 100's and you'd still keep running with it.

What's wrong with leaving a drive in the array until it's totally dead? Dual parity support might make this safer no? Reading the freenas zfs forum that's what a lot of those users do. Or is this tactic not really advisable with unraid?

I'm getting the same thing happening. Once with a Hitachi drive and now with a WD red. These are being precleared from an IBM 1015. Afaik this timeout signal 9 killed log message shows right before post-read starts. Guess i'll have to try my onboard intel ports next time.

I'm having the same issue.... See post #3 if it's still not working then attach supervisord.log That did it. Somehow I missed this. Thanks binhex!

I'm having the same issue....

sas2flsh -list and sas2flsh -o -listall You can try both of these commands. OK. It showed up. I used the Dell 6gbpsas and that' what is reported as the vendor/product ID. It does not say anywhere that it is an (IT). Guess the next step is to try it in a box. Thank you! If you boot into unraid with it installed you should be able to go to tools->system log. Then scroll down and look for LSISAS2008. It should list wether it's in IT mode or not.

sas2flsh -list and sas2flsh -o -listall You can try both of these commands.

Sorry but I can't answer your question. Maybe someone else can help answer since I've never flashed a Dell Perc 310. I would try using Fireballs H310 instructions here http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006 and try using the bottom pcie slot.

I don't do anything special. I've never seen the message. What I do is follow BetaQuasi's instructions here (he has the same motherboard btw). https://lime-technology.com/forum/index.php?topic=26774.0 I download his boot file (https://www.dropbox.com/s/ezeqcbu2tlfub6a/M1015_X9SCM_BOOT_P17.zip), unzip, add it all to the root directory of my bootable usb, then I go to the Avago website and download the latest 9211-8i P20 firmware, add it to the usb drive replacing the older firmware that's on the usb. I don't flash a bios on any of my cards, only firmware.

Seriously? I have one of those boards. Is the process the same or do I need to modify anything? That's an old board. Can it run UEFI? Wow coincidence. You should have no problem then. No uefi. Just flash in dos. I use the bottom pci-e slot. I've never specifically flashed a Perc 310 but I imagine it should be the same. It should definitely work for you. I've flashed like 5 LSI 9220-8i controllers so far with this motherboard.

I've heard of people needing to try 3 or 4 motherboards before they found one that would work. But yeah definitely try flashing from uefi shell. I'm going to be flashing another M1015 for somebody this morning from my Asus P6X58D Premium. Works like a charm.

its an open plex issue, has been for a few weeks now. Yeah, all this time i've been wondering why my bluray rips weren't playing. Started a few weeks ago. Anyway I hope they fix it....

It would be nice to have an official statement in the unraid 6 manual.... Let's just say i'm not really a big fan of marvel controllers. First got burned on my X58 mainboard with a watered down SATA-III. I think they are generally a lower-end more buggy controller and the LSI chipset is mostly superior. You read around the internet in the other NAS forums and the LSI/M1015 controllers are pretty much the go to cards for NAS builds.

If cost is not a factor then by all means get the LSI card. Not worth the potential headaches imo. There are corruption issues, VM issues, and preclear issues with the marvel chipset in unraid. I got rid of my 2 SAS2LP cards because I was getting SMART timeout errors during preclear. The preclear would just stop like 30 seconds in.

I have an official APC serial cable (AP940-0625A) My supermicro board has an integrated serial port and I can't even get it to recognize my SMC1500 within unraid. I looked in bios and port is definitely active. Go to unraid and try all the different apcupsd settings including specify custom cable. No dice..... USB cable works fine but i'm still missing a bunch of reporting, can't get modbus to work over USB. I will try with my SMT1500 as soon as I can get the firmware updated.

Let me know if it works and if some what you used. sure np.

They sell pcie rs232 cards, i've ordered one so I can update the firmware on my SMT1500. I have a SMC1500 also. I will be testing both of these smart models within unraid soon. I normally run a APC Back-UPS RS 1500 with unraid and it obviously reports fine.

You can review unraid diagnostics and what not but if you don't have a smart-ups that supports MODBUS you're probably always going to get incomplete reporting/stats within apcupsd. You should try and contact APC to see if they have a firmware patch, they have released updates for some of their older model ups's. ....And then MODBUS has to be activated within the APC menu's on the unit itself (off by default see above post)

<snipped from apcupsd manual> MODBUS Driver MODBUS is APC's replacement for the aging 'apcsmart' (aka UPS-Link) protocol. It is recommended for modern (ex: SMT series) Smart-UPS models. As of 3.14.11, apcupsd supports the MODBUS protocol over RS232 serial interfaces. As of 3.14.13, apcupsd supports the MODBUS protocol over USB. Not all APC UPSes support MODBUS. New 2013 year Smart-UPS models are likely to support it out-of-the-box and firmware updates are available for some older models. APC/Schneider tech support is your best point of contact for determining if a certain model will support MODBUS. That said, APC knowledge base article FA164737 indicates MODBUS support is available for the majority of the SMC, SMT, and SMX model lines. The required apcupsd.conf settings for MODBUS are straightforward. For MODBUS serial RS232: ## apcupsd.conf v1.1 ## UPSCABLE smart UPSTYPE modbus DEVICE /dev/ttyS0 LOCKFILE /var/lock UPSCLASS standalone UPSMODE disable The DEVICE setting identifies the serial port to which the UPS is connected. This can take the form of COM1, etc. on Windows or /dev/XXX on UNIX systems. You should use the APC-supplied serial cable (P/N 940-0625A) that ships with the UPS. Other 'smart' type cables may work, but only 940-0625A has been formally tested at this time. For MODBUS USB: ## apcupsd.conf v1.1 ## UPSCABLE usb UPSTYPE modbus DEVICE LOCKFILE /var/lock UPSCLASS standalone UPSMODE disable The DEVICE setting can be left blank or, optionally, set to the serial number of the UPS. If DEVICE is blank, apcupsd will attach to the first APC UPS it finds, otherwise it will attach to the specific UPS identified by the serial number. Note that most UPSes ship with MODBUS support disabled by default. You must use the UPS's front panel menu to enable MODBUS protocol support before apcupsd will be able to communicate with the UPS. You may need to enable the "Advanced" menu option before the MODBUS protocol option will be visible.

I was reading a while back that APC smart-ups is not fully compatible with apcupsd. Something about APC using a proprietary protocol for the smart-ups series? I think the guys at apcupsd were complaining about it. Anyway you might want to try and research more about it. I just vaguely remember reading about it.

Correct. Needo docker uses plex pass.

I disagree that it's an unraid issue. My Synology 1513+ wasn't showing up with Win 10 just like my unraid server. Until I pin it to quick access, then everything is fine.