HAVOC

Did you try a cold reboot after applying the fix with sea tools? I believe that is needed in order for the fix to take place.

Thank you for the fix. I had been running P19 firmware on my dual M1015 LSI cards for the last 4 years. I upgraded to P20 firmware last week and the errors started showing up with my 2 8TB ST8000VN004. One drive is 3 years old and the other is about 4 months old. Feb 6 03:10:09 Tower kernel: sd 1:0:3:0: device_block, handle(0x000c) Feb 6 03:10:11 Tower kernel: sd 1:0:3:0: device_unblock and setting to running, handle(0x000c) Feb 6 03:10:11 Tower kernel: sd 1:0:6:0: device_block, handle(0x000f) Feb 6 03:10:12 Tower kernel: sd 1:0:3:0: [sdf] Synchronizing SCSI cache Feb 6 03:10:12 Tower kernel: sd 1:0:3:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 6 03:10:12 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221104000000) Feb 6 03:10:12 Tower kernel: mpt2sas_cm0: removing handle(0x000c), sas_addr(0x4433221104000000) Feb 6 03:10:12 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(7) Feb 6 03:10:12 Tower kernel: sd 1:0:4:0: device_block, handle(0x000d) Feb 6 03:10:12 Tower kernel: sd 1:0:5:0: device_block, handle(0x000e) Feb 6 03:10:13 Tower kernel: sd 1:0:4:0: device_unblock and setting to running, handle(0x000d) Feb 6 03:10:13 Tower kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000e) Feb 6 03:10:13 Tower kernel: sd 1:0:6:0: device_unblock and setting to running, handle(0x000f) Feb 6 03:10:14 Tower kernel: sd 1:0:4:0: [sdg] Synchronizing SCSI cache Feb 6 03:10:14 Tower kernel: sd 1:0:4:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221102000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000d), sas_addr(0x4433221102000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(1) Feb 6 03:10:14 Tower kernel: sd 1:0:5:0: [sdh] Synchronizing SCSI cache Feb 6 03:10:14 Tower kernel: sd 1:0:5:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221106000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000e), sas_addr(0x4433221106000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(5) Feb 6 03:10:14 Tower kernel: sd 1:0:6:0: [sdi] Synchronizing SCSI cache Feb 6 03:10:14 Tower kernel: sd 1:0:6:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221107000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221107000000) Feb 6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(4) Feb 6 03:14:53 Tower kernel: sd 1:0:7:0: device_block, handle(0x0010) Feb 6 03:14:55 Tower kernel: sd 1:0:7:0: device_unblock and setting to running, handle(0x0010) Feb 6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#232 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=4s Feb 6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#232 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Feb 6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#233 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s Feb 6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#233 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Feb 6 03:14:56 Tower emhttpd: read SMART /dev/sdj Feb 6 03:14:56 Tower kernel: sd 1:0:7:0: [sdj] Synchronizing SCSI cache Feb 6 03:14:56 Tower kernel: sd 1:0:7:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 6 03:14:56 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221105000000) Feb 6 03:14:56 Tower kernel: mpt2sas_cm0: removing handle(0x0010), sas_addr(0x4433221105000000) Feb 6 03:14:56 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(6) Feb 6 03:40:01 Tower root: mover: started Feb 6 03:40:01 Tower root: file: //..4/... Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199808 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199816 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199824 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199832 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199840 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199848 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199856 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199864 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199872 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199880 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199888 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199896 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199904 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199912 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199920 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199928 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199936 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199944 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199952 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199960 Feb 6 03:40:07 Tower kernel: md: disk1 read error, sector=396199961

Quick question in regards to accessing unraid through the opnevpn docker. I have it all setup through the bridged mode. I can connect with my iphone. I have no access to unraid, I can access everything else with in my network such as other pc's through rdc. Im just curious if I have to edit anything in regards to the docker settings or open vpn. Thanks

Same problem with no luck

Tried your steps with the flash utility, but I get this error. Tower login: root Password: Linux 3.16.3-unRAID. Last login: Sun Nov 30 06:22:12 -0500 2014 on pts/0 from 192.168.1.4. root@Tower:~# cd /boot/linux root@Tower:/boot/linux# ls 2118it.bin* mptsas2.rom* sas2flash* root@Tower:/boot/linux# sas2flash -o -listall -bash: ./sas2flash: cannot execute binary file root@Tower:/boot/linux#

Haha I hear you on that. Maybe a Linux wizard can chime in?

Thank you very much! Not sure what this error is being cause by its a seg fault in the cron jobs .... Jan 25 11:47:01 Tower crond[1357]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jan 25 11:47:01 Tower kernel: crond[15712]: segfault at 4001e51c ip 4001e51c sp bf8d3ca8 error 15 in ld-2.11.1.so[4001e000+1000] (Errors) Jan 25 12:47:01 Tower crond[1357]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jan 25 12:47:01 Tower kernel: crond[16274]: segfault at 4001e51c ip 4001e51c sp bf8d3ca8 error 15 in ld-2.11.1.so[4001e000+1000] (Errors)

Installed without a hitch I also have it installed on UNRAID 5.0.5. Its actually running encoding faster then with the previous version looking at 3 hours now instead of 7 hours.

Thanks I'll give it a try. On a side note I have a 1230v2 xeon while using the old version of handbrake I was getting roughly 7fps. Well that improve with version .9.9?

Sorry to revive this thread. Any luck with compiling the .conf file for the latest handbrake version? I installed the .conf file that clunk compiled and installed with little skill by me. The problem is it won't let me encode the bluray mkv's. Thanks in advance.

Awesome I will be ordering the 5x3 and a xenon E3-1230 to take advantage of the ecc memory on my board. Wish I would have known that prior to purchasing but maybe I'll build another htpc.

Thanks prostuff. That was quick. I figured the norco would be the no brainier due to the case. Have you had any experience with the rpc 470?

I have a norco roc 470 case. I'm looking at getting a 5 in 3 cage to give me 15 usable drives. Any suggestions or preferably any one with the rpc 470. Thanks

I did the same with both of my M1015 cards....flashed P14 firmware.