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.

Thanks it worked!

My Parity drive is one of the one that is on the onboard controller that does not get moved. So I should juts be safe to reassign the other drives and all is good?

4.7

No one knows the proper way to handle this?

Hey Guys, I am trying to add a 2 port SATA card to my system that already has 6 onboard and 4 port card. When I install it and reboot the server the 4 drives on the other card are removed from the raid. Something about being unrecognized. When I go to drive config the 4 slots are no longer filled but I can add drives back. The 2 new slots are also available. What the right way to do this? Thanks Mike

I changed out the failing drive and all seems to be good. Not sure what was the deal with the parity message.

Attached syslog-2012-02-18.zip

Here is the entries in my log. Feb 18 16:43:32 MS kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 18 16:43:32 MS kernel: ata10.00: failed command: IDLE Feb 18 16:43:32 MS kernel: ata10.00: cmd e3/00:00:00:00:00/00:00:00:00:00/00 tag 0 Feb 18 16:43:32 MS kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 18 16:43:32 MS kernel: ata10.00: status: { DRDY } Feb 18 16:43:32 MS kernel: ata10: hard resetting link Feb 18 16:43:33 MS kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 18 16:43:33 MS kernel: ata10.00: configured for UDMA/133 Feb 18 16:43:33 MS kernel: ata10: EH complete Feb 18 16:44:03 MS kernel: ata10.00: limiting speed to UDMA/100:PIO4 Feb 18 16:44:03 MS kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 18 16:44:03 MS kernel: ata10.00: failed command: SMART Feb 18 16:44:03 MS kernel: ata10.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 18 16:44:03 MS kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 18 16:44:03 MS kernel: ata10.00: status: { DRDY } Feb 18 16:44:03 MS kernel: ata10: hard resetting link Feb 18 16:44:09 MS kernel: ata10: link is slow to respond, please be patient (ready=-19) Feb 18 16:44:13 MS kernel: ata10: SRST failed (errno=-16) Feb 18 16:44:13 MS kernel: ata10: hard resetting link Feb 18 16:44:19 MS kernel: ata10: link is slow to respond, please be patient (ready=-19) Feb 18 16:44:23 MS kernel: ata10: SRST failed (errno=-16) Feb 18 16:44:23 MS kernel: ata10: hard resetting link Feb 18 16:44:29 MS kernel: ata10: link is slow to respond, please be patient (ready=-19) Feb 18 16:44:58 MS kernel: ata10: SRST failed (errno=-19) Feb 18 16:44:58 MS kernel: ata10: reset failed (errno=-19), retrying in 1 secs Feb 18 16:44:58 MS kernel: ata10: hard resetting link Feb 18 16:45:03 MS emhttp: disk_temperature: ioctl (smart_enable): Input/output error Feb 18 16:45:03 MS emhttp: stale configuration Feb 18 16:45:03 MS emhttp: shcmd (4): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Feb 18 16:45:03 MS emhttp: _shcmd: shcmd (4): exit status: 1 Feb 18 16:45:03 MS emhttp: shcmd (5): cp /etc/exports- /etc/exports Feb 18 16:45:03 MS emhttp: shcmd (6): killall -HUP smbd Feb 18 16:45:03 MS emhttp: shcmd (7): /etc/rc.d/rc.nfsd restart | logger Feb 18 16:45:03 MS kernel: ata10: SRST failed (errno=-16) Feb 18 16:45:03 MS kernel: ata10: reset failed, giving up Feb 18 16:45:03 MS kernel: ata10.00: disabled Feb 18 16:45:03 MS kernel: ata10: EH complete Feb 18 16:45:04 MS emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Feb 18 16:45:04 MS emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Feb 18 16:45:04 MS emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Feb 18 16:45:04 MS emhttp: shcmd (10): crontab /var/spool/cron/crontabs/root Feb 18 16:49:17 MS kernel: ata10: exception Emask 0x10 SAct 0x0 SErr 0x4190002 action 0xe frozen Feb 18 16:49:17 MS kernel: ata10: hotplug_status 0x44 Feb 18 16:49:17 MS kernel: ata10: SError: { RecovComm PHYRdyChg 10B8B Dispar DevExch } Feb 18 16:49:17 MS kernel: ata10: hard resetting link Feb 18 16:49:18 MS kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 18 16:49:18 MS kernel: ata10: EH complete Feb 18 16:49:18 MS kernel: ata10.00: detaching (SCSI 10:0:0:0) Feb 18 16:49:18 MS kernel: sd 10:0:0:0: [sdk] Synchronizing SCSI cache Feb 18 16:49:18 MS kernel: sd 10:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Feb 18 16:49:18 MS kernel: sd 10:0:0:0: [sdk] Stopping disk Feb 18 16:49:18 MS kernel: sd 10:0:0:0: [sdk] START_STOP FAILED Feb 18 16:49:18 MS kernel: sd 10:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Feb 18 16:49:25 MS emhttp: disk_spinning: open: No such file or directory Feb 18 16:49:25 MS emhttp: disk_temperature: open: No such file or directory Feb 18 16:52:16 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 16:58:44 MS ntpd[1442]: time reset +1.888529 s Feb 18 17:02:18 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 17:14:14 MS ntpd[1442]: time reset +1.822057 s Feb 18 17:15:16 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 17:31:20 MS ntpd[1442]: time reset +1.890804 s Feb 18 17:35:12 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 17:48:07 MS ntpd[1442]: time reset +1.892603 s Feb 18 17:49:19 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 18:03:12 MS ntpd[1442]: time reset +1.770663 s Feb 18 18:03:34 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 18:19:26 MS ntpd[1442]: time reset +1.868614 s Feb 18 18:20:11 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 18:36:12 MS ntpd[1442]: time reset +1.873725 s Feb 18 18:36:41 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2 Feb 18 18:50:09 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:09 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:50:12 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:12 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:50:12 MS emhttp: shcmd (12): /usr/local/sbin/set_ncq sda 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (13): /usr/local/sbin/set_ncq sdg 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (14): /usr/local/sbin/set_ncq sdc 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (15): /usr/local/sbin/set_ncq sdb 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (16): /usr/local/sbin/set_ncq sdd 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (17): /usr/local/sbin/set_ncq sde 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (18): /usr/local/sbin/set_ncq sdf 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (19): /usr/local/sbin/set_ncq hda 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (20): /usr/local/sbin/set_ncq sdh 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (21): /usr/local/sbin/set_ncq sdj 1 >/dev/null Feb 18 18:50:12 MS emhttp: shcmd (22): /usr/local/sbin/set_ncq sdk 1 >/dev/null Feb 18 18:50:12 MS emhttp: ckmbr: open: No such file or directory Feb 18 18:50:12 MS emhttp: writing mbr on disk 10 (/dev/sdk) Feb 18 18:50:12 MS emhttp: mkmbr: open: No such file or directory Feb 18 18:50:12 MS emhttp: ckmbr: open: No such file or directory Feb 18 18:50:12 MS emhttp: get_fstype: open /dev/sdk1: No such file or directory Feb 18 18:50:12 MS kernel: mdcmd (26): start RECON_DISK Feb 18 18:50:12 MS emhttp: mdcmd: write: No such device or address Feb 18 18:50:12 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:12 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:50:12 MS kernel: md: do_run: lock_rdev error: -6 Feb 18 18:50:13 MS emhttp: shcmd (23): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Feb 18 18:50:13 MS emhttp: shcmd (24): cp /etc/exports- /etc/exports Feb 18 18:50:13 MS emhttp: shcmd (25): killall -HUP smbd Feb 18 18:50:13 MS emhttp: shcmd (26): /etc/rc.d/rc.nfsd restart | logger Feb 18 18:50:13 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:13 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:50:30 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:30 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:50:55 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:50:55 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:51:27 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:51:27 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:51:40 MS emhttp: disk_spinning: open: No such file or directory Feb 18 18:51:40 MS emhttp: disk_temperature: open: No such file or directory Feb 18 18:52:50 MS ntpd[1442]: time reset +1.856061 s Feb 18 18:53:31 MS ntpd[1442]: synchronized to 208.69.56.110, stratum 2

Ok this is bizarre. I choose to rebuild and now its saying "new parity drive installed" immediately after I chose this. Drive 10 was the one that was flagged as New not the parity. What is going on.....

Just to add, the Array is currently stopped and it says "Stopped: Disabled Disk Replaced" and it gives me the option to start and rebuild array and expand file system is possible.