July 10, 201312 yr unRAID Server Release 5.0-rc16c - Issue writing huge files in rc16c fork. http://lime-technology.com/forum/index.php?topic=28464.msg253352#msg253352
July 10, 201312 yr I upgraded to RC16c not too long ago, and let it run. Its been running fine for a handful of days, but today when I tried to copy the new Firefall Beta installer to my array, transfer speeds were abysmally slow (maxing out at 10mbps, attached screenshot shows 4mbps). Read speeds are fine, right around 40. I had put in some custom settings for md_num_stripes, md_write_limit, and md_sync_window (just randomly picked some numbers but made sure that num_stripes was equal to write_limit + sync_window), but I reset those to default, renamed all my plugin folders, and rebooted. I'm running stock unraid rc16c (except for unmenu and I forgot to rename my "extra" folder so I have Plex). Any ideas? Syslog attached. How were file transfers when you first booted RC16c were they good and then went slow after 3 days?? If so just booting up with that mem option may not mean anything as it would be the same as just rebooting you system. Also did you just use the stock menu mem boot option or did you modify it?? Sorry, I should have been more clear. RC16C started up fine, all my plugins worked, and I could copy/stream files with no problems. I didn't notice the slow speed issue because I didn't have anything to copy to my server until my first post. Dropped to 4096 MB RAM, speeds went way up. Thanks for the advice. Please repeat experiment on completely stock install. I reverted to stock install with 4096MB ram, speed topped out at 4mbps, and constantly fluctuated from 1mbps up to 4, and frequently dropped to 0. If you want me to try stock with my original 8192MB ram, I'll have to wait until I get home tonight after work. syslog.txt
July 10, 201312 yr I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again.
July 10, 201312 yr I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. I rebooted in unraid safe mode and limited ram to 4095. Write speeds on average are 6mpbs, peaking at 10. I also re-tested with all my plugins enabled and no memory restriction (running at 4096, as I have one 4GB stick installed) and my copy averages about 30mpbs, fluctuating from 15 up to 50. So it's not very consistent, but it's a lot faster. My normal syslog is too big to be attached, so I've put up links to each syslog in my dropbox folder. https://www.dropbox.com/s/jkasy3c73fhbjxc/syslog-4095-safemode.txt https://www.dropbox.com/s/488t00d8rthamej/syslog-normal-no_ram_restrictions.txt
July 10, 201312 yr Author I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. This should not be necessary.
July 10, 201312 yr Author I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. I rebooted in unraid safe mode and limited ram to 4095. Write speeds on average are 6mpbs, peaking at 10. I also re-tested with all my plugins enabled and no memory restriction (running at 4096, as I have one 4GB stick installed) and my copy averages about 30mpbs, fluctuating from 15 up to 50. So it's not very consistent, but it's a lot faster. My normal syslog is too big to be attached, so I've put up links to each syslog in my dropbox folder. https://www.dropbox.com/s/jkasy3c73fhbjxc/syslog-4095-safemode.txt https://www.dropbox.com/s/488t00d8rthamej/syslog-normal-no_ram_restrictions.txt Nothing wrong in the syslogs. How full is your target disk? This is not an -rc16c issue.
July 10, 201312 yr I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. I rebooted in unraid safe mode and limited ram to 4095. Write speeds on average are 6mpbs, peaking at 10. I also re-tested with all my plugins enabled and no memory restriction (running at 4096, as I have one 4GB stick installed) and my copy averages about 30mpbs, fluctuating from 15 up to 50. So it's not very consistent, but it's a lot faster. My normal syslog is too big to be attached, so I've put up links to each syslog in my dropbox folder. https://www.dropbox.com/s/jkasy3c73fhbjxc/syslog-4095-safemode.txt https://www.dropbox.com/s/488t00d8rthamej/syslog-normal-no_ram_restrictions.txt Nothing wrong in the syslogs. How full is your target disk? This is not an -rc16c issue. The disk has 641.69 GB free space, and the share I'm writing to only exists on that disk. The cache drive has 270.7 GB free as well.
July 11, 201312 yr Other discussion about PAE http://lime-technology.com/forum/index.php?topic=28487.msg253509#msg253509 Ok folks, I've moved your PAE/Windows discussion out of this thread into the lounge. While some of the questions and information have merit, it's not really something with this particular release.
July 11, 201312 yr I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. I rebooted in unraid safe mode and limited ram to 4095. Write speeds on average are 6mpbs, peaking at 10. I also re-tested with all my plugins enabled and no memory restriction (running at 4096, as I have one 4GB stick installed) and my copy averages about 30mpbs, fluctuating from 15 up to 50. So it's not very consistent, but it's a lot faster. My normal syslog is too big to be attached, so I've put up links to each syslog in my dropbox folder. https://www.dropbox.com/s/jkasy3c73fhbjxc/syslog-4095-safemode.txt https://www.dropbox.com/s/488t00d8rthamej/syslog-normal-no_ram_restrictions.txt Nothing wrong in the syslogs. How full is your target disk? This is not an -rc16c issue. The disk has 641.69 GB free space, and the share I'm writing to only exists on that disk. The cache drive has 270.7 GB free as well. whats the health status of your cache disk?
July 11, 201312 yr I believe you need to limit RAM to 4095 (this was explained in another thread), or use the built-in safe mode at unRAID boot....then test again. I rebooted in unraid safe mode and limited ram to 4095. Write speeds on average are 6mpbs, peaking at 10. I also re-tested with all my plugins enabled and no memory restriction (running at 4096, as I have one 4GB stick installed) and my copy averages about 30mpbs, fluctuating from 15 up to 50. So it's not very consistent, but it's a lot faster. My normal syslog is too big to be attached, so I've put up links to each syslog in my dropbox folder. https://www.dropbox.com/s/jkasy3c73fhbjxc/syslog-4095-safemode.txt https://www.dropbox.com/s/488t00d8rthamej/syslog-normal-no_ram_restrictions.txt Nothing wrong in the syslogs. How full is your target disk? This is not an -rc16c issue. The disk has 641.69 GB free space, and the share I'm writing to only exists on that disk. The cache drive has 270.7 GB free as well. whats the health status of your cache disk? Currently I'm finishing a parity check. I figured with all the rebooting I've been doing lately, should probably run one. How do I check the health status? The only way I know is to use unmenu, but I'm in safe mode at the moment.
July 11, 201312 yr Currently I'm finishing a parity check. I figured with all the rebooting I've been doing lately, should probably run one. How do I check the health status? The only way I know is to use unmenu, but I'm in safe mode at the moment. Apparently unmenu is still available when booted in safe mode. Smart attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 185119076 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 159 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 231028177 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24206 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 124 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 - 21 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 1014 190 Airflow_Temperature_Cel 0x0022 070 055 045 Old_age Always - 30 (Min/Max 25/31) 194 Temperature_Celsius 0x0022 030 045 000 Old_age Always - 30 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 051 031 000 Old_age Always - 185119076 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 - 270110493269636 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2411685787 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 534815259
July 11, 201312 yr Apparently unmenu is still available when booted in safe mode. hmm that should not be the case... Smart attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 185119076 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 159 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 231028177 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24206 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 124 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 - 21 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 1014 190 Airflow_Temperature_Cel 0x0022 070 055 045 Old_age Always - 30 (Min/Max 25/31) 194 Temperature_Celsius 0x0022 030 045 000 Old_age Always - 30 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 051 031 000 Old_age Always - 185119076 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 - 270110493269636 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2411685787 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 534815259 Which drives is this?
July 11, 201312 yr Currently I'm finishing a parity check. I figured with all the rebooting I've been doing lately, should probably run one. How do I check the health status? The only way I know is to use unmenu, but I'm in safe mode at the moment. Apparently unmenu is still available when booted in safe mode. Smart attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 185119076 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 159 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 231028177 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24206 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 124 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 - 21 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 1014 190 Airflow_Temperature_Cel 0x0022 070 055 045 Old_age Always - 30 (Min/Max 25/31) 194 Temperature_Celsius 0x0022 030 045 000 Old_age Always - 30 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 051 031 000 Old_age Always - 185119076 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 - 270110493269636 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2411685787 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 534815259 You have a relocated sector, you may want to keep an eye on that drive. 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1
July 11, 201312 yr Which drives is this? It's my cache drive. You have a relocated sector, you may want to keep an eye on that drive. I have a handful of spare drives laying around. I plan on replacing it when I get home.
July 11, 201312 yr So Tom, how's it looking in your opinion RC16C? The best candidate yet for 5 final release? ETA for 5 final?
July 11, 201312 yr So Tom, how's it looking in your opinion RC16C? The best candidate yet for 5 final release? ETA for 5 final? http://lime-technology.com/forum/index.php?topic=28482.0 There are no longer any "release stopper" issues left. As soon as I finish the documentation I will release 5.0 "stable". If I can throw in a few 'cosmetic' type fixes before then I will but primary focus now is finishing docs to aide new users and those moving from 4.7.
July 13, 201312 yr Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that.
July 13, 201312 yr Author Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that. You should use the 'powerdown' script which calls emhttp to initiate the shutdown. The reason you want to do that is because emhttp will generate all the proper shutdown events that plugin event handlers are possibly waiting for.
July 13, 201312 yr Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that. You should use the 'powerdown' script which calls emhttp to initiate the shutdown. The reason you want to do that is because emhttp will generate all the proper shutdown events that plugin event handlers are possibly waiting for. and this is the included one with 5.x ? /sbin/powerdown #!/bin/bash # # Helper script to gracefully power-down unRAID server. # Works only if webGui is running and listening on port 80. # Access a blank page in case this is first request since startup. /usr/bin/wget -q -O - localhost/update.htm >/dev/null # Have emhttp do all the work as if user clicked 'shutdown' in webGui. /usr/bin/wget -q -O - localhost/update.htm?shutdown=apply >/dev/null so what if the array is running (does it stop it, then do shutdown)? what happens if its doing a parity check? or if webgui isnt listening? and finally, can we make this be called if the user hits the power button (not holding it down).
July 13, 201312 yr Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that. You should use the 'powerdown' script which calls emhttp to initiate the shutdown. The reason you want to do that is because emhttp will generate all the proper shutdown events that plugin event handlers are possibly waiting for. and this is the included one with 5.x ? /sbin/powerdown #!/bin/bash # # Helper script to gracefully power-down unRAID server. # Works only if webGui is running and listening on port 80. # Access a blank page in case this is first request since startup. /usr/bin/wget -q -O - localhost/update.htm >/dev/null # Have emhttp do all the work as if user clicked 'shutdown' in webGui. /usr/bin/wget -q -O - localhost/update.htm?shutdown=apply >/dev/null so what if the array is running (does it stop it, then do shutdown)? what happens if its doing a parity check? or if webgui isnt listening? and finally, can we make this be called if the user hits the power button (not holding it down). Take a look at this for powerbutton integration: http://lime-technology.com/wiki/index.php/Powerdown_script
July 13, 201312 yr Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that. You should use the 'powerdown' script which calls emhttp to initiate the shutdown. The reason you want to do that is because emhttp will generate all the proper shutdown events that plugin event handlers are possibly waiting for. and this is the included one with 5.x ? /sbin/powerdown #!/bin/bash # # Helper script to gracefully power-down unRAID server. # Works only if webGui is running and listening on port 80. # Access a blank page in case this is first request since startup. /usr/bin/wget -q -O - localhost/update.htm >/dev/null # Have emhttp do all the work as if user clicked 'shutdown' in webGui. /usr/bin/wget -q -O - localhost/update.htm?shutdown=apply >/dev/null so what if the array is running (does it stop it, then do shutdown)? what happens if its doing a parity check? or if webgui isnt listening? and finally, can we make this be called if the user hits the power button (not holding it down). From my experience it is called on stock unraid when I hit power button and yes it seems to gracefully stop array and shutdown properly, if no file is in use/open, else it will wait... exactly as when you stop array from webgui.
July 13, 201312 yr Tom, what is the proper way to cleanly shutdown unraid from the command line? (no webui) Reason I ask is because for the apcupsd package.. ideally I want to have it just mimic what the webui is doing - but not have to rely on using that. From my experience it is called on stock unraid when I hit power button and yes it seems to gracefully stop array and shutdown properly, if no file is in use/open, else it will wait... exactly as when you stop array from webgui. When stopping the array in a power failure, it is NOT a good idea to wait forever for disks to be idle. (The UPS won't last that long)
July 13, 201312 yr I use 5.0 beta14 for over a year, without any issue, today upgrade to RC16c, this release work very well. I use the plugins: Servio, APC My system is 12T , 7 hard drive 2T each. Good work. Thanks
July 14, 201312 yr I'm getting an error when trying to open the downloaded rc16 zip file....is anyone else?
July 14, 201312 yr I'm getting an error when trying to open the downloaded rc16 zip file....is anyone else? Download the file again, and/or test the MD5 of the downloaded file.
Archived
This topic is now archived and is closed to further replies.