draz

After 5 minutes of idling after a reboot to obtain the information needed for this post. Syslog had been written to again. Nov 19 03:18:47 SALLY kernel: ata8: hard resetting link Nov 19 03:18:49 SALLY kernel: ata8: SATA link down (SStatus 0 SControl 300) Nov 19 03:18:49 SALLY kernel: ata8.00: link offline, clearing class 1 to NONE Nov 19 03:18:49 SALLY kernel: ata8: EH complete Nov 19 03:18:49 SALLY kernel: ata8.00: detaching (SCSI 8:0:0:0) Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Synchronizing SCSI cache Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Stopping disk Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] START_STOP FAILED Nov 19 03:18:49 SALLY kernel: sd 8:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Nov 19 03:18:49 SALLY kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen Nov 19 03:18:49 SALLY kernel: ata8: irq_stat 0x00000040, connection status changed Nov 19 03:18:49 SALLY kernel: ata8: SError: { CommWake DevExch } Nov 19 03:18:49 SALLY kernel: ata8: hard resetting link Nov 19 03:18:50 SALLY kernel: ata8: SATA link down (SStatus 0 SControl 300) Nov 19 03:18:50 SALLY kernel: ata8.00: link offline, clearing class 1 to NONE Nov 19 03:18:50 SALLY kernel: ata8: EH complete Nov 19 03:18:50 SALLY kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Nov 19 03:18:50 SALLY kernel: ata8: irq_stat 0x00000040, connection status changed Nov 19 03:18:50 SALLY kernel: ata8: SError: { DevExch } Nov 19 03:18:50 SALLY kernel: ata8: limiting SATA link speed to 1.5 Gbps Nov 19 03:18:50 SALLY kernel: ata8: hard resetting link

Unraid version 4.7 I am having a rather strange problem after replacing a dead disk. I replaced a 1.5tb drive with a 2tb drive recently. After powering the machine down and then booting it back up expecting to just be able to format the drive and then check the box to do a parity rebuild. Instead, both the new drive and the parity are showing as orange with the new disk showing as "unformatted" (shown in main.png). When I check the the box to confirm that I want to do this and attempt to format the new disk it appears to start formatting and then immediately after clicking refresh it is back at the same prompt as main.png. In that time, various errors have been output to syslog (syslog-error.txt). I have tried doing a pre-clear on /dev/sda.. the new disk but the status of the main page has not changed afterwards. The array comes online but I am unable to bring the new 2tb drive into the array and too scared to write any more data to it with the parity drive in its current state. My understanding is that orange on a parity drive means that a parity rebuild is in place... Not really sure how to proceed here since the drive has been in this state for a week now. Any help is appreciated Thanks. Al. syslog-error.txt

Cheers, I'll give both of them a go and report back

Pretty sure I am staring at the problem in these logs.. just can't put my finger on the fix.

Hello Unraid forum. Having a bit of an issue with my unraid server after replacing the parity drive yesterday. The parity was a 1.5tb samsung and was upgraded to a 2tb WTD. As expected after physically replacing the disk the new parity drive came up with the blue indicator and I brought the array online and ticked the checkbox to complete a parity rebuild / sync. It all seemed to be working okay... 1200 minutes eta. Job done me thinks.. Woke up this morning and the parity drive is listed offline with the red indicator and about 127 errors on the UI main page. I don't seem to be able to get this disk online now. If I unassign the disk, then reassign it, the indicator for the parity turns blue again and I can attempt another parity rebuild.. however now it fails almost instantly and takes the disk offline again (red). Throwing a great deal of write errors into the dmesg. I have attached two files and was hoping that someone might be able to give me some assistance with what is occurring here. dmesg_boot.txt - output from dmesg after the unraid server is booted dmesg_parity-rebuild.txt - output from dmesg after the parity rebuild is issued again and fails almost instantly. I'd appreciate any assistance I can get with troubleshooting the problem. Thanks in advance. Draz. dmesg_boot.txt dmesg_parity-rebuild.txt

Hi, I recently upgraded from 4.5.x to 4.7. Following the instructions in the readme in the release and copying the three files to the flash drive of my already running NAS. After a reboot, I have two disks with a red dot and two with a blue dot. The array was running fine pre upgrade but now won't start due too too many missing or disabled disks. I have seven drives and all seven are showing in the devices tab. I've tried unassigning and re-assigning all the disks to no avail. All drives including red and blue are showing their SMART data, temps and sizes. Is it possible to provide some more useful log files that may help indicate what is occuring. I am not sure what log files would be most useful. Regards, Draz.