-
Posts
195 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by shooga
-
Here's the zip. bunker-diagnostics-20151020-1128.zip
-
I'm having an issue where my parity drive goes in to an error state due to read errors after about one month of running. At first I thought it was an issue with the sas/sata cabe, but I've replaced that and it still comes back. I'm able to temporarily fix the issue by stopping the array and restarting. Then the disc shows back up and I can add to the array and do a fresh parity calculation. At this point I think it's time to RMA the drive (WD Red 6TB), but I thought I'd check in here to see if this is more likely to be an interface issue. The drive is connected via my AOC-SAS2LP-MV8. However, this card has been otherwise very reliable. This problem started when I upgraded some of my hardware (including the drive but not the card) and also upgraded to v6. Thanks for any advice!
-
I don't use the cache drive for my Backup share, which may help you get around the problem. But I'm not really sure what would be causing that.
-
Did some more reading on this and it looks like rsync can copy files that are open, but there does appear to be a flaw in using it without stopping docker. Based on what I've read, if a file is being written while rsync is running then rsync will simply copy what is there at that instant. So if an application is in the middle of a write then there's a chance the copy will be corrupt. This may be a very rare situation, but given that this is meant to be a backup it needs to be reliable. Glad you asked...I think it's probably best to switch back to a manual cron job that includes the command to stop/start docker in addition to the rsync command.
-
Should have mentioned before that if you're at all worried about websync you should test it first with some test folders to make sure it's doing what you want. I'm not stopping my dockers. My understanding is that rsync will miss files that are added or changed during the sync and I'm ok with that. Can just get those the next time. Shouldn't be any other downside to leaving dockers running.
-
It's a pretty simple setup with just a source folder (my apps folder on the cache), destination folder (a backup folder on the array), 2 flags (archive & hard links), and then a weekly schedule (Mondays at 2am). A screenshot of the weekly backup is attached. The monthly backup looks the same but with just a change in the schedule. 2015-09-17_6-29-24.pdf
-
Ah, ok. I have changed poll_attributes in disk settings from the default of 1800 (30 min) to 120 (2 min). Hopefully that won't cause a performance issue. Thanks!
-
Thanks for the reply, but I don't think that's it. I have the page update frequency set to real-time. It seems like the temp that is shown there isn't always in sync with what I see if I click on the drive and look at the output of smartctl shown there. Even if I manually reload the page. For example, when I booted the server my mSATA cache drive was showing as 30 C for several minutes and then just jumped to 55 C (very hot) in one step with nothing in between. In the past, I think I would see the temps changing more gradually.
-
After updating to v6.1.2 it seems like the disk temps shown on the Main page of the UI are updating slower. Anyone else notice this? Am I crazy? Seems like it's ~5 minutes now and I swear it was updating more often before.
-
FYI: I found the WebSync docker in sparklyballs' beta repository and am using it for my backups. Was easier to deal with for me than setting up cron jobs with rsync manually. I have one backup scheduled weekly and one monthly for some redundancy. I'm only backing up my app data so I'm not stopping docker. My understanding is that files that change after rsync has started will not be synced, which I'm ok with. Can get them the next time. EDIT: After more reading it looks like this may not be a good method for backing up app data. Based on what I've read, if a file is being written while rsync is running then rsync will simply copy what is there at that instant. So if an application is in the middle of a write then there's a chance the copy will be corrupt. This may be a very rare situation, but given that this is meant to be a backup it needs to be reliable.
-
FYI: I found the WebSync docker in sparklyballs' beta repository and am using it for my backups. Was easier to deal with for me than setting up cron jobs with rsync manually. I have one backup scheduled weekly and one monthly for some redundancy. I'm only backing up my app data so I'm not stopping docker. My understanding is that files that change after rsync has started will not be synced, which I'm ok with. Can get them the next time.
-
It's a new build with some airflow challenges through the cages, so I need to keep temp notifications on for now as I work through that. I may be able to turn them off once I'm confident that everything is under control. (FYI the iStarUSA S-917 has pretty terrible airflow with the case door closed.) I would think a fan blowing across the passive coolers would make a big difference, but I guess it depends which chips are generating the heat and which side of the board they are mounted on. Anyway, experimenting and dealing with stuff like this is part of the fun of building these servers. So I don't mind the tinkering. Thanks again.
-
Ok. Thanks all. I'm going to try to the passive coolers. Does anyone know if there's a way to change the temperature that causes the warnings in unRAID for this drive? I'm guessing not. Those emails that say my drive has overheated make me cringe every time. If the passive coolers don't quite tame the heat then I may have to point a fan at it just to make those stop...
-
Thanks Gary! It hadn't even occurred to me to add passive cooling (duh). I'll give these a try.
-
I think I found a bug in the Fan Auto Control plugin, but it's actually working as a feature for me - so please don't fix it unless you add a feature that allows the exclusion of certain drives from the temperature check. I just switched to an mSATA SSD cache drive and (eventually) noticed that the high temp it's reporting in the UNRAID dashboard isn't causing my fans to spin faster. I took a look at the source for the plugin and see that you are using grep to find the Temperature_Celsius attribute from the output of smartctl. However, manually running that command on my SSD returns nothing because this drive doesn't report temperature using the Temperature_Celsius attribute and instead uses the Airflow_Temperature_Cel attribute. This drive is a 500GB Samsung 850 EVO mSATA SSD and I bet there are other drives out there that report temperature in the same way via smartctl. So to fix this I think you could just modify the plugin so that if grep for Temperature_Celsius returns nothing then you look for Airflow_Temperature_Cel. However, in my case my SSD is running a bit hot and more importantly is not near the array drives/fans so it really shouldn't be driving the fan speed (unless it was a different fan). So if you do fix this please add the option to exclude a drive (or drives) from the temp check so they don't affect fan speed. I think it would be good for other people too because I see lots of people moving to SSD cache drives and PC cases often have the SSDs mounted in entirely different locations.
-
Wanted to add some more info here as I'm digging into it. It looks like the Fan Auto Control plugin isn't actually affected by my mSATA SSD cache drive because of the way it reports temperature via smartctl. I took a look at the source for Auto Fan Control and it's using grep to grab the temp from the output of smartctl by looking for Temperature_Celsius, which works for my HDDs. But my SSD reports temperature as Airflow_Temperature_Cel and doesn't report Temperature_Celsius at all, so it's ignored by the plugin. I'm not sure why it appeared that the SSD was driving the fan speed, but I'm glad it's not really an issue. Would be good to update the plugin to to read drives like my SSD correctly, but only if there's also an option added to ignore certain drives. I'd still like feedback on temps please!
-
What are the common guidelines on temps for mSATA SSDs? I recently switched to an mSATA SSD and it's not actively cooled so the temp is typically around 50 C. The operating range according to Samsung is up to 70 C, so I'm not sure if this is something to worry about or if it's typical for mSATA. Any thoughts? If this is typical, then it would be nice to change the heat alarms in Unraid to reflect it. Would also be nice if I could exclude it from the Dynamix Fan Auto Control since it's driving my HDD cage fans up in speed even though they aren't blowing on it. If it's best to have lower temps then I guess I need to find a cooling solution, so any recommendations would be appreciated. Seems like an Antect SpotCool could work. Thanks!
-
I recently upgraded my server and moved to an iStarUSA s-917. I used the iStarUSA BPN-DE350 cages, which use an 80mm fan. I installed Noctua NF-A8 ULN fans to lower the noise, but they didn't provide adequate cooling. My first parity check had one drive hit 50 degrees. So I did a bunch of research and ended up with a pretty simple solution. I switched to the Noctua NF-A8 PWM, which have more than 50% greater airflow at full speed. I'm controlling the speed of the fans using a 4-pin connector on my motherboard and the Dynamix System Temp and System AutoFan plugins. It allows the fans to move slow and quiet most of the time and then speed up to increase airflow as required automatically. I also researched the 80mm to 120mm adaptors, but read mixed reviews on their effectiveness. So if that still doesn't work for you, you may want to try a PWM version of the Noctua fan (either 80mm or 120mm) because they often have higher peak speeds and higher peak airflow. (I also found that with the front door closed on the s-917 the case is starving the fans and they're not able to move enough air. It's kind of annoying, but keeping the door cracked open all the time also helps a lot.)
-
I successfully moved from rfs to xfs using the process and commands from this thread. Thanks for the great info. Specifically, I used: rsync -av --progress --remove-source-files /mnt/diskX/ /mnt/diskY/ >rsync.log 2>rsync.err Those last two arguments (>rsync.log 2>rsync.err) send the output and errors to separate log files, which I monitored using the tail command: tail -f filename.ext I did this all in three screen sessions (one for the rsync and one for each tail command). Worked great and I was able to follow the progress while also capturing the output in case anything went wrong and I needed to refer to it later. Thankfully, there were no errors.
-
Is there a list of motherboards that are known to work with System Temp and System AutoFan? Also, what temp would be used to drive chassis fans and can this be adjusted? Edit: I was able to get this working based on a procedure on this thread. My motherboard only has one 4pin fan connector (CPU fan) so I'd still like to know if there's a list because AutoFan seems to only work with PWM. Which temp in SystemTemp is AutoFan using? Can anyone give any guidance on what the following temps are? These are my choices in System Temp: coretemp - Physical id 0 - 44.0 C coretemp - Core 0 - 45.0 C coretemp - Core 1 - 43.0 C coretemp - Core 2 - 45.0 C coretemp - Core 3 - 43.0 C w83627ugh - SYSTIN - 51.0 C w83627ugh - PECI Agent 1 - 44.0 C The coretemps are pretty obvious except for the Physical id 0. No idea where the w83627ugh temps would be measured though. Is PECI coming from the CPU? SYSTIN would be the motherboard? I'd be surprised if the motherboard is hotter than the CPU.
-
In case anyone is curious or finding this later via a search, this all works perfectly fine. My power supply had an EATX12V 4+4 pin 12V connector (pretty standard), so I used one of those 4 pin connectors (after testing to verify that the pin layout was correct). I also used the little jumper linked above. The only down side is that the HDDs spin up immediate after turning the power supply on because the supply is not switched by the MB. Otherwise, the system functions as normal.
-
So based on what MyKroFt said, wouldn't it be better to use this? #!/bin/bash #stop dockers /etc/rc.d/rc.docker stop #Backup cache via rsync date >/var/log/cache_backup.log /usr/bin/rsync -avrtH --delete /mnt/cache/.Programs/ /mnt/disk4/Backups/unRAIDweeklybackups/Cache/dotPrograms >>/var/log/cache_backup.log #start dockers /etc/rc.d/rc.docker start
-
[unRAID 6 beta14+] Unassigned Devices [former Auto Mount USB]
shooga replied to gfjardim's topic in Plugin Support
Is there a way to spin down unassigned devices? Doesn't seem to happen automatically. -
Thanks for the response. Got it working with that command. I'm totally new to docker but I see how to interact with them now.