January 1, 201016 yr Here is my syslog. Can someone tell me what happend to unraid early this morning. It was working fine when I went to bed early this morning. Thx
January 1, 201016 yr Here is my syslog. Can someone tell me what happend to unraid early this morning. It was working fine when I went to bed early this morning. Thx The syslog appears to be after you rebooted. There are no clues to analyze, since they were in the previous syslog (if they were there at all)
January 12, 201016 yr Joe is right, this is a syslog just *after* a crashed session and reboot. You do have something else of concern here. Both sdh (WDC_WD10EADS-00M2B0_WD-WMAV50195436) and hdc (ST3500410AS_5VM09ACH) have HPA's, and worse, were unlocked in this syslog. As we know from another recent case, this indicates a region at the far end of the drive that has been and will continue to be clobbered by the BIOS. It is just a little more than a megabyte, at the very end of the drive, so it is out of the way, but I would not be surprised to see parity errors at the very end of the parity check. The best solution is to find a BIOS update that allows you to disable this 'feature'.
Archived
This topic is now archived and is closed to further replies.