June 18, 201115 yr Tried Joe L.'s new preclear, which ran successfully. However, when I tried to add the disk to unRAID, it proceeded to clear the disk anyway. Here is a link to the post that I explained what happened and posted the syslog. Preclear Disk Not Recognized
June 18, 201115 yr Looks like an unRAID bug accepting a precleared disk >2TiB. I verified with Joe L. that the preclear signature was correct. > dd if=/dev/sdd count=1 2>/dev/null | od -x -A x 000000 0000 0000 0000 0000 0000 0000 0000 0000 000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 I believe what is happening is that unRAID is recognizing the precleared disk, adding the GPT, but not completing the process of adding the disk to the array. When I try a second time to add the same disk to the array, the preclear signature iss no longer in place, so unRAID begins its own clearing process. Tom, please let me know if there is other info I can provide. Thanks!
June 18, 201115 yr Looks like an unRAID bug accepting a precleared disk >2TiB. I verified with Joe L. that the preclear signature was correct. > dd if=/dev/sdd count=1 2>/dev/null | od -x -A x 000000 0000 0000 0000 0000 0000 0000 0000 0000 000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 I believe what is happening is that unRAID is recognizing the precleared disk, adding the GPT, but not completing the process of adding the disk to the array. When I try a second time to add the same disk to the array, the preclear signature iss no longer in place, so unRAID begins its own clearing process. Tom, please let me know if there is other info I can provide. Thanks! Here is a syslog from trying to add a 3T precleared disk to an array. syslog-2011-06-18.zip
June 19, 201115 yr just took the plunge. all of my drives are labeled as missing... should i just reassign to the proper slots and restart array? Near the start button, there's a warning: "Too many wrong and/or missing disks!" when I tried to reasing the slots, it goes from "missing" to "wrong". I should note that I am using the ESXi RDM method, if that might have anything to do with this.
June 19, 201115 yr Axeman, what version were you running before 5.0b7? thanks BRiT.. 4.7 - followed these directions: Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network: Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there. If present, delete these files from the flash (sorry, you will have to re-enter all your users after booting this release): config/passwd config/shadow config/smbpasswd 2. Reboot your server.... from the change log. I didn't have a config/shadow, but did have the other two. Also, I used the flash share...
June 19, 201115 yr Syslog is attached. Edit: even if i put things in the right slots, i can't start the array. so should i just press the new config button? data right now isn't critical - it's all test stuff... BUT I would like to see how to fix this w.o. going brute on it. syslog.txt
June 20, 201115 yr I stopped my array, and just overwrite the two bz* files (from 5.0b6a), rebooted,l and it automatically started up. I guess maybe I should have shut off "auto-start" also?
June 20, 201115 yr I was coming from 5.0Beta6 and discovered that two things are not working anymore: "MySql for XBMC" implementation doesn't seem to work anymore (use of MySql as centralized database) Time Machine seems not to be supported anymore: http://lime-technology.com/forum/index.php?topic=11547.0 Anyone having the same issues? I'm asking myself if I need to run the "New Permission" script again?
June 20, 201115 yr I was coming from 5.0Beta6 and discovered that two things are not working anymore: "MySql for XBMC" implementation doesn't seem to work anymore (use of MySql as centralized database) Time Machine seems not to be supported anymore: http://lime-technology.com/forum/index.php?topic=11547.0 Anyone having the same issues? I'm asking myself if I need to run the "New Permission" script again? Mysql works normal for me no issues at all can't help you with timemachine.... not a mac user
June 20, 201115 yr Summary of my issues with 5.0b7: 1 - Sync errors after drive rebuild (occurs in 4.7 as well) 2 - Adding 3T precleared disk to array not working 3 - "Trust my parity procedure" (initiconfig / mdcmd set invalidslot 99) not working
June 20, 201115 yr Syslog is attached. Edit: even if i put things in the right slots, i can't start the array. so should i just press the new config button? data right now isn't critical - it's all test stuff... BUT I would like to see how to fix this w.o. going brute on it. So I went back to 4.7 by following the steps backwards. The array is online, and functional. It decide to run a parity check on first boot, and is about 30% done. I'll try again to go to 5.0b7 - but if the results are the same, what options do I have?
June 20, 201115 yr Summary of my issues with 5.0b7: 1 - Sync errors after drive rebuild (occurs in 4.7 as well) 2 - Adding 3T precleared disk to array not working 3 - "Trust my parity procedure" (initiconfig / mdcmd set invalidslot 99) not working Is #3 anything to do with 3T drive(s)? or 5.0Beta7 in General (before u added a 3TB drive)?
June 20, 201115 yr I've experienced errors every time I've done a Parity Check. If they're corrected, is this a big deal? Why would I experience errors? And are the number of errors listed, a running total, or the errors encountered in the last parity check?
June 20, 201115 yr I've experienced errors every time I've done a Parity Check. If they're corrected, is this a big deal? Why would I experience errors? And are the number of errors listed, a running total, or the errors encountered in the last parity check? You should *never* get parity errors. "Fixing" a parity error by updating the parity bit could be wrong as a parity error does not indicate which bit is wrong (parity bit or one of the data bits on any drive). Any parity errors should be fixed by deciding wether you trust your data or you trust your parity drive. The number is the number of errors in the last parity check.
June 20, 201115 yr Is #3 anything to do with 3T drive(s)? or 5.0Beta7 in General (before u added a 3TB drive)? Unrelated to 3T drives. I have not had to use the trust procedure in a while, but had an idea to add a precleared disk using a modified trust procedure technique and learned that it did not work. I expect this problem affects other prior 5.0 betas as well.
June 20, 201115 yr Hmm, not good How can I figure out the problem files/bits? Use the NOCORRECT parity check. Read the actual bits of each word on all the disks, perform the mental xor to verify parity, rinse/lather/repeat (many times for a 3TB drive) Seriously, verify you have the correct clock speed timing, and voltage setting on your memory strips. That is by far the biggest cause. After that, it could be any one of your disks, repeated checksums of files of blocks of data read from the disks should result in identical checksums. A difference on only one disk might isolate the issue to a single disk.
June 20, 201115 yr Hmm, not good How can I figure out the problem files/bits? Use the NOCORRECT parity check. Read the actual bits of each word on all the disks, perform the mental xor to verify parity, rinse/lather/repeat (many times for a 3TB drive) Seriously, verify you have the correct clock speed timing, and voltage setting on your memory strips. That is by far the biggest cause. After that, it could be any one of your disks, repeated checksums of files of blocks of data read from the disks should result in identical checksums. A difference on only one disk might isolate the issue to a single disk. Where do I check this? Also, not sure if I have it auto-correct or not--but it says my parity is valid. I'll have to double check when I go home tonight.
June 20, 201115 yr Hmm, not good How can I figure out the problem files/bits? Use the NOCORRECT parity check. Read the actual bits of each word on all the disks, perform the mental xor to verify parity, rinse/lather/repeat (many times for a 3TB drive) Seriously, verify you have the correct clock speed timing, and voltage setting on your memory strips. That is by far the biggest cause. After that, it could be any one of your disks, repeated checksums of files of blocks of data read from the disks should result in identical checksums. A difference on only one disk might isolate the issue to a single disk. Where do I check this? Bios settings. Also, not sure if I have it auto-correct or not--but it says my parity is valid. I'll have to double check when I go home tonight. It has never had the wording fixed so it says anything else, even when in nocorrect mode and errors are found. If you are not fixing them then it might be the same error again and again. Again though, you don't know if you should be fixing the data disk, it the parity disk. It all depends on where/how the errors are being detected... Joe L.
June 20, 201115 yr Use the NOCORRECT parity check. Read the actual bits of each word on all the disks, perform the mental xor to verify parity, rinse/lather/repeat (many times for a 3TB drive) I read this - and for a quick second said - hmmm maybe UnRaid isn't the tool for me. You got me good! good thing your next sentence started out with the word "seriously".
June 20, 201115 yr okay - so 2nd try and same thing. i'm going to try on a brand new flash, and will copy over the "shares" config over. hopefully that works. starting to get a little annoyed now. even though it isn't production data, i was hoping it would be pretty seamless.
June 20, 201115 yr how many disks in your server? Did you perform a memory test yet? These issues have nothing to do with the 5.0beta7 release if you are getting random parity errors. You can test each of your disks in turn by running md5 checksums on the blocks failing in the parity checks. Open a thread in the general support forum and continue the diagnosis there. Post a syslog.
June 20, 201115 yr Whatever is the problem, is appears to be related to specific configurations. Seems to be the case, thanks for trying and posting the results. I am running on: SuperMicro X8SI6-F-O (Xeon 3470) Kingston Fully Buffered ECC (2 x 4GB RAM) Onboard SAS2008 (LSI) LSI SAS 9201-16i (Add-on card) Various HD's from 2TB->160GB Hitachi Deskstar's (from 7K -> 5k) (1) Seagate 7K 250GB (1) WD 10K 80gb Reboot your server. You mentioned it is not in 'auto start' mode - good. (If not and array is started after reboot, then Stop array before next step). You need to run 'reiserfsck' on all of your data disks; and this is simpler since you don't have a parity disk. For each of your data disks: 1. Make a note of which linux device identifier it has been assigned to. This is the string in parenthesis under Identification on the Main page. For example (sdj). 2. Type this command in a telnet session: reiserfsck /dev/sdj1 <-- you put the string identified above and added a '1' The program will ask you to confirm the operation, to which you type Yes (exactly like that - upper case Y, lower case e and lower case s - hit return. The program make take several minutes to run and will output a report. If there are errors it will tell you how re-invoke reiserfsck using certain switches to correct the error - follow those instructions. Do this for all your data disks. Once complete, Start the array and repeat your testing. Note to others reading this post: These specific instructions only apply if you don't have a Parity disk. If you do have a parity disk and you invoke 'reiserfsck' in this manner, it will invalidate Parity. Thank you Tom, I have just completed the reiserfs checks on all the drives, attaching log "reiserfs_log.txt" to this post for your review. I only notice there was a journal replay on the cache drive (the last drive in the log). It only has 2 directories on it. I never had a hung system with these drives before until testing this release. Probably this jornaling on this one drive was caused by this. In either case, what do you recommend I do now. Proceed to start the array and test again? I dont believe the reiserfs log shows anything that would cause unRAID to behave like it is doing so. But I will proceed to do whatever you recommend, let me know. P.S. unless i am mistaken (first time ever running reiserfsck) I did not see anything calling/requesting for a repair. I repeated all steps today after running and posting the 'reiserfsck' log. This time reboot succeeded. Attaching a full tail log from beginning to end, should Tom wish to review it to see and notice anything else for the future. I hope this ends the issue I ran into and never comes back , I will keep monitoring and testing forward. If the journaling on the cache drive is what caused this (and no repair was required) then I am OK with it, not sure how it could have happend thought. On to 3TB preclear testing now. I hot added my new 3Tb drive, started a preclear with the beta version of preclear 1.12beta that should accomidate drives larger than 2.2TB. after 2 cycles 66 hours. the drive successfully precleared. The array was running this whole time and all drives spun down. I decided I would reboot the box before adding the new preclear 3TB drive into the array. Once again, facing same problem, I clicked "Stop" array stopped. I clicked "Reboot" server is hung. Tom I have not done a single thing since I ran the reiserfsck checks on all disks as you requested (granted a 66 hr preclear). What do I do to troubleshoot. My goal was it was supposed to reboot and I was going to add the 3TB drive into the array and see if it accepts the drive as cleared already. If you notice the 80GB WD 10k cache drive even though is on a SAS controller seems to be being sent a hpdarm command not the native linux command, dont know if that has something to do with it. Console is showing its stuck at "mdcmd (48): spinup 20" it been like this for an hour already.
June 20, 201115 yr I'm sure this was not the intention, Beta7 now spinup/spindown the drives in VMWare ESXi using mapped raw disks, but temperatures still a non go. The tests were done using either LSI Logic SAS controller (mptsas driver) and Paravirtual controller (pvscsi driver with recompiled kernel). If you, Tom, could fix this little temperature bug, we can dramatically improve the usability of unRAID, since the users could consolidate router / PVR / home automation / storage appliances into one physical machine. For one of your drives that don't report temps, note what it's linux device identifier is, e.g., "sdc", and type this command from a telnet session: smartctl -A /dev/sdc <-- replace 'sdc' with correct device identifer Then post the output here. My dumps: root@Tower:~# smartctl -A /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 234016408 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2771 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 40744490 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6860 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 88 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032834 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 057 045 Old_age Always - 28 (Min/Max 27/29) 194 Temperature_Celsius 0x0022 028 043 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 046 040 000 Old_age Always - 234016408 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 230193067201874 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 290482469 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3868205915 root@Tower:~# smartctl -A /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 165814427 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 440 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3284118 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1627 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 35 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 063 045 Old_age Always - 28 (Min/Max 26/28) 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 050 045 000 Old_age Always - 165814427 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 144392505524929 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1838164866 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2032970711 Loaded modules: root@Tower:~# lsmod Module Size Used by md_mod 44397 0 xor 12961 1 md_mod ata_piix 17455 0 mptsas 29873 0 mptscsih 14072 1 mptsas mptbase 49478 2 mptsas,mptscsih scsi_transport_sas 16613 1 mptsas piix 3524 0 e1000 75710 0 This is not same issue i see with shire's post above. Please type this command instead and post the output: smartcl -n standby -s on -A /dev/sda Sorry for the long quote, Tom, but I will leave it there so you can remember the issue easely. The command above result in the following: root@Servidor:~# smartctl -n standby -s on -A /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Device is in STANDBY mode, exit(2) I'm sure the device wasn't in standby because I was running a parity check at the same time. The odd is that the green ball reflects the power mode (steady when awake and blinking when in stanby) , but the temperature isn't displayed.
Archived
This topic is now archived and is closed to further replies.