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...