enetec

Try these... - flash on another mainboard - flash P11 first (with p11 flash command!), then, eventually, go with P19/20... It could be bad anyway...

Hi folks, I'm on 6.0.0 final with no issue BUT if I check for updates, it reports me that I'm 'up to date' and it doesn't show me 6.0.1 as available Is this a known bug? What could it because of? EDIT: it seems to be related to bad internet connectivity due to Jumbo Frame settings... LAN connectivity was perfect, but internet had issues... Anyway unRAID wasn't reporting any error during checks... (and I think it should do... even only for help troubleshooting! ) Found 6.0.1 & two more plugin updates now...

Read all in details. I bet on ext4 bad specs... Wanna bet some bucks?

If that... linux bug imho...

778 bad sectors already marked on first drive... Over 3K (and increasing...!) on second one!! I would NOT use these drives for my porn collection either...

Uh..?!

Pxx is the main release. Under that there are subreleases (bugfixes). For P20 we have v.20.00.00.00 (bugged) and v.20.00.02.00 (flawless). Under P20 I'm getting over 2 GB/s transfer speeds on my 4xSSD RAID0, so... I think 'slow' could be unappropriate term.... About your instructions, they are fine, BUT on some cards could be safer crossflashing with P11 at first and only THEN (simply) update to P19/P20... Anyway, as you report, this is not ever needed...

It seems an unexpected self-reset because of failing/having issues hardware to me... I would start with an accurate (read: long...) Memtest and with a doublecheck of fans and operative CPU temps... Even bad BIOS settings (e.g. overclocking, etc...) could be a cause of this too... (revert any changes eventually)

That suggests some sort of 'race' condition. How it might be identified I have no idea. Sorry, I was just askin'... BUT I think it could be this way... If so, Bonienl suggested CLI commands in my similar thread could be usefull to identify issue causes... https://lime-technology.com/forum/index.php?topic=40353.0

I think he's asking if you dropped one of the Samsungs. Those drives report G-shock and one of them looks like it took a bump but is otherwise ok. Yes, exactly. A VERY BAD bump... SMART value for that attribute is reporting 1 that is the worst possible value (e.g. a BUMP harder than hard drive specifications...) Anyway even one of your Seagates is reporting some reallocated sectors... I would check it's surface with a HDD Regenerator live CD before putting back it on production...

Is top command reporting emhttp @100% CPU usage?

Your card seems to be an LSI 2008 controller based, programmed with an IT firmware (even if I am not able to precisely catalog it...). If it's as I understood, YES, you need an IR firmware to get any RAID by card (from a Supermicro FAQ: " BPN-ADP-E16-L is in IT mode and supports JBOD only. ".) BUT be very carefull on what exactly version do you need to use...

Have you never fallen to the floor one of your Samsungs?

Congrats to all the devs team. Nice work. I love it.

Since what I have seen, if you on unRAID disk settings force NCQ disabled you should not have any problem with that firmware bug... I would not go with a firmware update on a disk containing data... Errors reported on those disks hardly are connected with that bug anyway...

http://ssd.userbenchmark.com/Compare/Samsung-850-Evo-120GB-vs-Crucial-MX100-128GB/m20032vs2618 Samsung rulez...

Go with an IBM 1015 and crossflash it to P20 IR firmware...

Maybe the card simply doesn't know what the heck TO are! . It only knows TB... (Yeah, ok, just jokin' a bit here... )

You can map them on controller bios as single/jbod to make them 'presented' to unRAID, but this limits unRAID control on them and it's not preferable...

Yes, this seems to be the main issue on Virtualbox too... https://lime-technology.com/forum/index.php?topic=37687.0 Some here seem to have fine working systems on ESXi using Plop to boot from USB, but this doesn't work fine on Virtualbox too...

Some have reported in the past some strange issues removing jumper after have used WDs with jumper for a while... Anyway, you can try with a HDD Regenerator 'Scan and repair' surface scan which doesn't require to cancel data from hard drive for the process...

+1

This instead could be a good external solution too... http://www.verbatim.it/it/prod/store-n-stay-nano-usb-drive-32gb-98130/?con=25 I've 8GB version and it has the needed valid serial for unRAID usage...

You have some pretty old drives and two of them are showing some issues... My tips: - change SATA cable and, if possible, SATA port, of your Maxtor HDD and then test its surface with a HDD Regenerator live cd. This drive has been logged for UDMA errors on both SMART and unRAID and seemed to become unresponsible since of bad connections or internal issues. Data wil not be touched during process; - make same surface test to your Seagate with serial ending with C4T8. It has already marked some bad sectors and expect to find more and/or a lot of delays (which aren't god too...); I would test them in two pass for safety reason: first one do a 'Scan only without repair'. If the disk tend to disconnect or hang during process immediately backup all its contens as fast as you can and substitute it with a new drive in array. If they end this first pass (even with delays or bad sectors found...), go for a second pass with repair enabled this time. Eventually post screenshots of stats result at the end before re-adding them to array.

Well... consider that you can start the array at first without a parity protecting it (not a very different situation that your actual one...) and, after trasferring your data to the array (even faster since of the lack of parity operations...), you can add a parity disk a make unRAID build parity to protect array on it.