June 17, 200818 yr Last night, I upgraded to version 4.3.1 from 4.3.beta6 Everything went fine, UNRAID started without any problems. Then, I finally implemented the custom timezone feature and did a "reboot" of UNRAID. When it came back up, the last disk that I added a Smasung 750 GB disk, showed up as "unformatted". This is a brand new disk and I had replaced an old disk with this new one. During that replace, UNRAID did a rebuild and re-created data on this disk (I do not remember it going through a format process). That worried me and I decided to restart the array.I stopped it and started it and this time the disk showed up the way it was before. Anyway, I decided to do a parity check again and then went to sleep. When I woke up, it had completed, but showed that there was one error during parity check. I went through the syslog, but did not see any thing that would be cause to worry, but, I am not sure. Can someone take a look and see if everythings OK and If I need to do some preventive action. I have attached the syslog and a screenshot of the main page. I have also run "smartctl -a" on the disks and if needed I can attach them. Thanks, VJ
June 17, 200818 yr Last night, I upgraded to version 4.3.1 from 4.3.beta6 Everything went fine, UNRAID started without any problems. Then, I finally implemented the custom timezone feature and did a "reboot" of UNRAID. When it came back up, the last disk that I added a Smasung 750 GB disk, showed up as "unformatted". This is a brand new disk and I had replaced an old disk with this new one. During that replace, UNRAID did a rebuild and re-created data on this disk (I do not remember it going through a format process). This is normal, there is no need to format a disk when it is being used to replace an existing disk since the contents (and the formatting) of the existing disk will bring over the formatting. That worried me and I decided to restart the array.I stopped it and started it and this time the disk showed up the way it was before. Anyway, I decided to do a parity check again and then went to sleep. When I woke up, it had completed, but showed that there was one error during parity check. I went through the syslog, but did not see any thing that would be cause to worry, but, I am not sure. Can someone take a look and see if everythings OK and If I need to do some preventive action. I have attached the syslog and a screenshot of the main page. I have also run "smartctl -a" on the disks and if needed I can attach them. Thanks, VJ You are probably just fine. I would do another parity check just to be sure it is not a disk that is acting up. Then another set of smartctl on the disks will show if the process is detecting any bad sectors. Joe L.
June 17, 200818 yr Author Thanks! I will do what you have suggest tonight and keep you posted on the results. VJ
June 18, 200818 yr See this post. There are several reports like yours, of a drive unexpectedly showing as Unformatted, and a shutdown and restart seemed to clear it up. You either have exceptionally good cooling, or a faulty temp sensor on the CPU, or an incompatible sensor driver. The CPU temp shows as -269C in the line below! Tower kernel: ACPI: Thermal Zone [THRM] (-269 C) I'm curious what kind of cooler you have on that CPU! It's not an important issue, but it might be interesting on your next reboot to check the BIOS menus for a PC Health menu that shows the CPU temp. The parity error occurs very early in the check, so was probably due to the one drive appearing temporarily to be unformatted. Should be harmless.
June 18, 200818 yr Author Robj, I do not have any special CPU cooler. I used the one that I got when I bought the intel CPU. VJ
June 18, 200818 yr It's OK, just my poor attempt to be facetious. You would need a very expensive liquid nitrogen or better cooler to achieve -269C.
June 18, 200818 yr It's OK, just my poor attempt to be facetious. You would need a very expensive liquid nitrogen or better cooler to achieve -269C. -279C would even be more impressive. I think if that happens you'll actually go back in time. ;-) Bill
June 18, 200818 yr Author I re-ran the parity check and it came back successful without any errors. I also re-ran smartctl on my 3 disks. The 300 GB (seagate) one seems to have high read and seek error rate, but the document on SMART says that these values may be high for Seagate disks. I haven't had any problem with the disk. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 102 094 006 Pre-fail Always - 76601297 7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always - 467332648 At this time, I think this was just a one time occurrence and will just ignore it and continue. Thanks! VJ
Archived
This topic is now archived and is closed to further replies.