marmot74

I'm not rebooting....it's frozen/crashed right after the last entry above.

Unraid parity keeps crashing and server freezes. Log shows read errors on TONS of drives at once. Used SSH to get active log during crash. Thoughts? Controller failing? Attached full log and here is last bit. Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311088 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311096 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311104 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311112 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311120 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311128 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311136 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311144 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311152 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311160 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311168 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311176 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311184 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311192 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311200 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311208 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311216 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311224 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311232 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311240 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311248 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311256 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311264 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311272 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311280 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311288 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311296 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311304 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311312 Dec 15 17:25:52 MS kernel: md: disk2 read error, sector=62311320 Dec 15 17:25:52 MS kernel: md: recovery thread: exit status: -4 Dec 15 17:25:52 MS kernel: sd 1:0:1:0: [sdc] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:1:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:2:0: [sdd] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:2:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:3:0: [sde] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:3:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:4:0: [sdf] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:4:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:5:0: [sdg] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:5:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:6:0: [sdh] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:6:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:52 MS kernel: sd 1:0:7:0: [sdi] Synchronizing SCSI cache Dec 15 17:25:52 MS kernel: sd 1:0:7:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000b), sas_addr(0x4433221103000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(0) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x0009), sas_addr(0x4433221100000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(3) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000a), sas_addr(0x4433221101000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(2) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000c), sas_addr(0x4433221102000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(1) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000d), sas_addr(0x4433221104000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(7) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000e), sas_addr(0x4433221105000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(6) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221106000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(5) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: removing handle(0x0010), sas_addr(0x4433221107000000) Dec 15 17:25:53 MS kernel: mpt2sas_cm0: enclosure logical id(0x500605b007554f60), slot(4) Log.txt

Disregard. Thanks

cron for user root /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >dev/null 2>&1 /bin/sh: dev/null: No such file or directory Thanks!

Hot damn! it worked. thanks friend. This worked for me as well. Thanks!

Argh. Also encountering the same issue after upgrading. No problem getting to unraid via browser but can not access any shares.

Mine is labeled as "HighPoint 8-Port PCI-Express 2.0 x8 SAS/SATA 6Gb/s non-RAID Controller Components Rocket 2720SGL" So NON RAID.

I am using the 2720SGL with no problems, really quick and supports 8 Drives. Did not have to flash anything or add any drivers. Running unraid 6.1.7

Mine did this as well. It was a BIOS setting that was something about detecting USB and booting up. I would check BIOS settings first.

I just rebuilt my server and put in a Highpoint Rocket 2720SGL. It required no script changes or anything. Was plug and play with 6.1.6.

Hey Guys, I upgraded my system from unraid 5 to the latest 6. During this process I realized I am using a super old motherboard that you can not turn HPA off. It has put the HPA on a old IDE 500GB drive that has been running for near 10 years. GO Seagate Caviar Blue! I am swapping Motherboards and also removing that drive. Anything I need to do or do I just stop the array, replace the hardware and after its back up remove the old drive and rebuild parity? Does it matter what ports I plug the drives back into or is unraid smart enough to know? Thanks! Mike

New Config and reassign all drives without the drive you want to remove. Make sure you don't assign a data drive to the parity slot. When you start the array unRAID will rebuild parity without the removed drive. Just out of curiosity, when you re-assign the drives does the order of the data drives matter or is it just the parity drive that matters?

Thanks! I was hoping it was that easy.

I am not replacing it. I have replaced lots of drives but this is the first time removing a drive completely.

Hey Guys, I have an old 500GB drive that I want to remove from array. Once I have copied all the data from it what do I do on the unraid WebUI to remove it from the array? I am running the latest v6 unraid.