July 29, 201312 yr hi, sdv, a 4tb drive gives errorswhenever I want to fill it past approx 177 Gb still free. The filecopy just time-outs. Tried it several times. I did a reiserfsck, but everything was OK root@Media_Server:/mnt# reiserfsck --check /dev/md17 reiserfsck 3.6.21 (2009 www.namesys.com) Will read-only check consistency of the filesystem on /dev/md17 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Mon Jul 29 14:04:23 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/md17' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 915978 Internal nodes 5441 Directories 249 Other files 926 Data block pointers 926893847 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Mon Jul 29 14:10:46 2013 ########### What could be the problem, and how do I fix it (appart from copying the whole drive to another 4Tb drive, removing the empty drive from unraid and then readd it again to unraid (after a preclear))? I have an almost stock RC16c , only VMtools are installed, previous unraid version was rc6 and lower. Thanks, Wim
July 29, 201312 yr If you are dead set on filling the drive to 100%, you could copy the files to another drive on the server temporarily, then move them with midnight commander at a console (local or telnet) prompt. Very full drives often take too long to find the free spots left on the drive and time out the windows command. You could also try creating empty sub folders to copy the files to, as that sometimes helps.
July 29, 201312 yr Author If you are dead set on filling the drive to 100%, you could copy the files to another drive on the server temporarily, then move them with midnight commander at a console (local or telnet) prompt. Very full drives often take too long to find the free spots left on the drive and time out the windows command. You could also try creating empty sub folders to copy the files to, as that sometimes helps. I have 23 drives, if I have to leave 2 times the size of the largest file free, then I would loose about 2.3 Tb (about 3.4% of the array size). This is more than 1 2Tb drive. Unacceptable. I know all about the behaviour of unraid when the drive is almost full. I gets slow, sometimes so slow I have to try 2 times. That's not the problem here. The problem is: Unraid says the drive has 178 Gb free. But when I try to copy something to it, the copy hangs at around 177 Gb. It just crashes with a timeout I suspect a filesystem error. Thats why I did the reiserfsck. But it doesn't find anything? The drive itself is OK, no write errors or other in unraid. In the end, if I can not solve this any other way, I will copy the content of the drive on another external drive (I have on avarage 20 Gb free on the other 22 drives), get the drive out of the array, preclear it and then insert it again in the array. Then copy all the files from the external drive back to the array drive. But that's a whole lot of work/takes a lot of time. So my question: Is there some other way to solve this? Another option with reiserfsck? Anyone? Thanks, Wim
July 29, 201312 yr If you are dead set on filling the drive to 100%, you could copy the files to another drive on the server temporarily, then move them with midnight commander at a console (local or telnet) prompt. Very full drives often take too long to find the free spots left on the drive and time out the windows command. You could also try creating empty sub folders to copy the files to, as that sometimes helps. I have 23 drives, if I have to leave 2 times the size of the largest file free, then I would loose about 2.3 Tb (about 3.4% of the array size). This is more than 1 2Tb drive. Unacceptable. I know all about the behaviour of unraid when the drive is almost full. I gets slow, sometimes so slow I have to try 2 times. That's not the problem here. The problem is: Unraid says the drive has 178 Gb free. But when I try to copy something to it, the copy hangs at around 177 Gb. It just crashes with a timeout I suspect a filesystem error. Thats why I did the reiserfsck. But it doesn't find anything? The drive itself is OK, no write errors or other in unraid. In the end, if I can not solve this any other way, I will copy the content of the drive on another external drive (I have on avarage 20 Gb free on the other 22 drives), get the drive out of the array, preclear it and then insert it again in the array. Then copy all the files from the external drive back to the array drive. But that's a whole lot of work/takes a lot of time. So my question: Is there some other way to solve this? Another option with reiserfsck? Anyone? Thanks, Wim copy to the "disk" share.
July 29, 201312 yr Author copy to the "disk" share. I do use the disk share. I use win7 and copy from my SABdownloader to , in this case, disk17/bluray. I don't have a cache disk. It always gives a timeout at around 177 Gb free (I manually 'refresh' unraids main window every few seconds to see when it happens). I though it is some filesystem corruption. Maybe I deleted some files and the filesystem thinks those blocks are still in use? But a reiserfsck can't find any problems. I don't know what else to do, so any help is appreciated... Below is a screenshot of the main window. Thanks, Wim
July 30, 201312 yr Author Attach a syslog that includes a failed copy. Sadly nothing to see there. I started with a clean start, removed all files from the previous version (rc6). Flash drive was completly empty Copied vmtools to /extra and my key to the /config dir. I started unraid, it could not find any previous config, so I put all drives in the correct drive slots. Started a parity check When this was done (next day), added users and shares, misc settings (started the new permission script, time zone, etc...) I think i tried to copy it around this time: Jul 28 22:38:02 Tower kernel: mdcmd (178): spinup 23 Jul 28 23:38:07 Tower kernel: mdcmd (179): spindown 1 But nothing is visible in the syslog. I several times stopped and started the array later. I'm at work now, I'll try tomorrow to get a cleaner syslog. syslog.zip
August 24, 201312 yr Author My new 4Tb drive arrived and I ran a 3 pass preclear on it. I would now like to replace dsik 17 with the new drive. I don't want to just replace it, the 177Gb should be useable, so a 'failed disk' procedure is not wanted. What I would like to do is (unraid 5.RC16c): - stop the array - remove drive 17 from list of drives. - run in shell 'initconfig' to invalidate parity (drive 17 is forever removed from the array) - start the array, it should start to calculate parity - press cancel. stop array and insert the new precleared drive in slot 17 - press start again, now let the parity calculation finish - after finish parity calculation, start a parity check - copy all files from the original disk17 with the help of another computer back on the new disk17 ---the end Is this a valid sequence of events, should I let the first parity calculation finish? I know I have for some time a unprotected array, just as all data on the old disk17 is unprotected untill I copy it back to the array. Haven't done this before, so comments are wanted... Thanks
August 24, 201312 yr Assuming you have a 4TB parity disk... (and you MUST to be able to install a 4TB data disk in a single step) All you need t do is: Perform a parity check... (Just to make sure all is working before you replace drive 17) Then, stop the array Replace disk 17 with the newer larger 4TB drive. (preferable it was precleared so you can minimize the risk of an early demise of the drive) Start the array. unRAID will ask to t confirm you want the old contents rebuilt onto the replacement drive and it will first (on its own) partition the new drive, re-construct the old contents of disk 17 onto it, and then expand the file-system on it to use the full size of the 4TB drive. There is no need to copy the data from another PC. There is no need to set a new disk configuration. (in fact, you should NOT)
August 24, 201312 yr Yes, what he said. You can simply replace the drive and let unRaid rebuild the contents on to the new drive.
August 24, 201312 yr Author I think you misunderstood. disk17 has some sort of error, i can't fill this drive to full (please read previouos msg's for details). Replacing this drive and letting it rebuild would create a bit-to-bit exact copy, including this error. I want this error gone. Thats why this procedure. Is it correct? Thanks
August 24, 201312 yr Author Media_Server login: root Password: Linux 3.9.6p-unRAID. root@Media_Server:~# smartctl --all /dev/sdv smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: Hitachi HDS5C4040ALE630 Serial Number: PL1311LAG3J5EA Firmware Version: MPAOA3B0 User Capacity: 4,000,787,030,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Aug 24 21:15:38 2013 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (43005) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 134 134 054 Pre-fail Offline - 102 3 Spin_Up_Time 0x0007 126 126 024 Pre-fail Always - 553 (Average 550) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 219 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 111 111 020 Pre-fail Offline - 43 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3456 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 221 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 221 194 Temperature_Celsius 0x0002 250 250 000 Old_age Always - 24 (Min/Max 12/38) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@Media_Server:~#
August 24, 201312 yr Author There is some sort of filesystem corruption that a 'reiserfsck --check /dev/md17' can't detect. It's not something systemwide, no other 4Tb or other drive has this problem (see screenshot of my config a few msg's higher) The easiest (and thus far only, no other solutions have been suggested) solution seems to be to remove the drive, insert a new empty 4Tb drive, copy all data from old to new drive and then use the old 4Tb drive to upgrade a 2Tb drive to 4Tb. I bougth a 4Tb so I would be able to copy all data back to a 'new' disk17. Upgraded and installed drives a lot, never removed a drive, I am reasonable familiar with linux. Thanks
Archived
This topic is now archived and is closed to further replies.