kaiguy
Members-
Posts
723 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by kaiguy
-
Good catch. Shame it came up late, though. There's probably a lot of people who don't monitor that (or this) thread.
-
I throw my hat in the ring for Denon. They aren't exactly cheap, but they are beasts of a receiver. My previous receiver was an Onkyo of similar price level, but I absolutely prefer the Denon. I have the last gen model, AVR-2310ci, and it handles all my HDMI content with ease. The upconversion chip is pretty awesome for SD content, though I must admit I don't watch a whole lot of SD media, and my TV does a fine job with the upconversion as well. The Audyssey automatic speaker setup is crazy! Deals are to be had online for sure. Regardless on what model you decide on, go and check out avsforum.com before you buy. That is a great resource, but will also take up hours of our life reading through your options Good luck!
-
No offense, but the voiding of the warranty statement is inaccurate. Take a look here at solution #3: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5357 In addition, there are posts on the official WDC forum by a moderator stating clearly that he spoke with WDC techs and confirmed it can be run on an EARS drive and it will not void the warranty (don't have a link for that, but I'm sure a search can find it). I RMA'd two of my WD20EARS drives because of super high load/unload counts. Could it have been mechanically fine? According to WDC, it can reach into the millions without issue. Personally, I think that's adding a lot of mechanical wear on the drives. I ran wdidle on all my EARS drives, changing the setting from 8 seconds to 5 minutes. Everything working just fine here, and though I may sacrifice a bit of power savings, I think the longevity of the drives are worth it.
-
I got Couchpotato running on unRAID without much effort, but I also found that it, unlike Sab and Sickbeard, could not be configured to not constantly spin up my cache drive. So I opted to run Couchpotato from my HTPC instead, just referencing my unRAID IP instead of localhost for the SAB host. Personally, I prefer my method, but others may be fine with their drives constantly spinning up.
-
No problem! Sorry the Forced-FDD didn't work for you, but glad its working overall for you. I think you'll like this board. It's been rock solid for me.
-
Outstanding. Thanks, Rajahal. I went ahead and just pulled the plug with my running-as-normal setup. Aside from the annoying beeps and high-pitch static sound from the UPS, everything worked perfectly. After some time, the apcupsd 3.14.3 package stopped the array and shut everything down. After reboot, all is back--no parity check! I don't know why I've waited so long to test this, but it definitely gives me peace of mind now, as I have had quite a few blackouts in the last 6 months (thanks SDG&E!). It's also pretty cool I always like running things at the newest version of everything, but since the older apcupsd package worked perfectly, I think I'm not going to mess around with that.
-
Question to the community regarding a UPS test (and sorry if it is semi-hijacking): It seems to be good form to stop the array (in the event that something doesn't work and the server isn't shutdown properly). However, I want to test if the clean powerdown package will appropriately kill anything that is active. For example, I need to shutdown sabnzbd+ before I stop the array, as it prevents unmounting. In a blackout scenario, I might not be around to shut it down. Any suggestions on how I can test this? Or perhaps should I just call the clean powerdown from a terminal session to test that part? Thanks!
-
USB Header adapters - Keep your USB FOB inside your computer
kaiguy replied to mikechy's topic in Good Deals!
I use the first one, and it works fine. Worth it for peace of mind, having the flash drive nice and secure inside the case. -
The majority of my drives are WD20EARS drives. The fastest I've done a preclear on it was about 26 hours (before I ever added a disk to the array). The slowest was over 30 hours. It seems to me that as I add more disks, the preclear time goes up. Also, when I've precleared two or more drives of the same size at the same time, they usually finish right around each other. My most recent preclears had one end hours after the other (and the late one I started first). So I think it can just vary for a variety of reasons.
-
2 TB Seagate Barracuda LP ST32000542AS Firmware Issues
kaiguy replied to BRiT's topic in Storage Devices and Controllers
In the event there were others like me that didn't have an optical drive in their unRAID server and didn't want to or couldn't move the drive to another machine to update the firmware... I picked up this external CD-ROM from Amazon, less than $12: http://www.amazon.com/External-Slim-CD-ROM-Drive-Black/dp/B001B1796U/ref=sr_1_3?ie=UTF8&qid=1292287589&sr=8-3 Worked fine on my already-in-use disk. Though, like everyone else, I did have to force the flash. I noticed the software was dated in February 2010, so my guess is until they release another firmware version, you'll definitely have to force it for this model. -
Just wanted to make a note about BIOS config for this board, as I forgot exactly how I set it up to boot from the flash (then today, as I had to make some changes to update the firmware on a Seagate drive, I had issues getting it back to normal). You need to enable Forced-FDD emulation for the unRAID USB drive (I can't recall the exact menu option, but it's USB configuration near the chipset stuff). Then, under Boot | Hard Disks, disable all disks except for the flash drive (yeah, it shows up there, for whatever reason). Finally, under boot order, enable the USB flash drive as the first and only device. That should make everything work perfectly! This is likely a similar process for other recent ASUS boards. On a different note, I haven't read about anyone else using this board, but I still plan on certifying this at level 2. I think I'm at the point where I'm no longer making major config changes, rebooting, etc., so I should be able to have this running for a month straight.
-
roastdawgg, those are awesome pictures. Really clean build! I don't know how you guys get your cables looking so neat--I can't do them with just zipties. On a different note, I noticed your RAM is installed in different colored slots/directly next to each other. If you'd like to run it in dual channel mode (which I think you would considering you have a matched pair), you're going to want to install them in the A1 and B1 slots.
-
2 TB Seagate Barracuda LP ST32000542AS Firmware Issues
kaiguy replied to BRiT's topic in Storage Devices and Controllers
Has anyone managed to update the firmware via a flash drive instead? I have one of these LP's precleared and installed in my array, but now I'm thinking I should just go ahead and update the firmware from CC34 to 35. I just really don't want to have to pull the drive out of my box and switch it over to a computer with a CD-ROM. -
I have been running the ASUS P7H55-M LE for about two weeks now. Newegg link: http://www.newegg.com/Product/Product.aspx?Item=N82E16813131661 ASUS link: http://www.asus.com/product.aspx?P_ID=R6oEda1Jsq2P67Ft Quick specs: Core i7/i5/i3; 2 slots DDR3, 6 SATA, 1x PCI-e 2.0 16x, 1x PCI-e 4x, 2x PCI, HDMI, etc. I originally had 8 drives going (including cache), but I had to remove 3 for RMA replacement. So, at the moment, here's my config, running on unRAID Pro 4.6-rc3: ASUS P7H55-M LE Intel Core i3-540 G.Skill 4GB DDR3 Corsair 650TX Supermicro AOC-SASLP-MV8 3x WD20EARS (including Parity) 1x WD15EARS 1x WD1001FALS (cache) The attached syslog is from 11/25/2010, up until now (4 days). In my limited opinion, this board is absolutely compatible with unRAID. Gigabit works great... onboard SATA is solid (I am running 4 of my drives on the 6 onboard ports, the other on the SM SASLP)... I have not found even one board-related issue. Hope this helps the community! syslog-2010-11-28.txt
-
In an effort to streamline my startup and shutdown process, I am trying to take advantage of rc.* scripts to start and stop items such as sabnzbd, sickbeard, etc. I have browsed quite a few threads on this topic (http://lime-technology.com/forum/index.php?topic=5611.0, to name one), but still don't quite know the best practices. I also write this post with the understanding that 5.0 will probably have some standards in place, but I'm still working on an rc of 4.6. Currently, I have a few rc.* scripts saved on my flash drive, all of which respond to start and stop commands. My go script copies those files to /etc/rc.d and makes them executable. The go script also calls those rc.* scripts with the start command. Not sure if this is the recommended method, but that's how I have it. What I don't know is how to insert the stop commands for these rc.* scripts in the rc.local_shutdown. I believe it needs to be inserted before rc.unRAID is called, correct? Or can I just make my own rc.local_shutdown script that is copied over in the go script. My assumption is this is not a good idea, in case something else modifies the rc.local_shutdown script. Any direction would be greatly appreciated!
-
After a little more experimentation, I believe the problem to my cache drive not spinning down is actually SickBeard. I have set the log directory to /var/log, but SB still seems to write to its cache on a somewhat regular basis. I'm now thinking my best bet is to get a lower-power cache drive and just live with it. Though it would be nice if SickBeard had more options for its search other than every 'n' hours (like only search every 'n' hours during this span of time). Perhaps I'll try a feature request
-
Nope. I don't have a watched dir.
-
Hmm... well, I made the setting to 200MB, put the log directory under /var/log, made sure I don't have a watched folder, and haven't downloaded anything (or copied anything to my array) and the cache drive still won't spin down. My guess is its the general cache folder which stores "admin" items. I wonder if I could just set the cache directory to the ramdisk... but then again I only have 4 GB of RAM. Anyone have any thoughts? My cache drive is a Caviar Black, so it's the most power hungry in the box. It would be a shame if it's spinning 24/7.
-
It's a total of 5 files, of which only 3 are actually used for my setup, and those files are 31.1 KB, 11 bytes and 14 bytes accordingly. One file is for RSS data, which is updated every 15 minutes. I agree that this will increase writes to the flash drive, but I think I'm safe with at least a million possible writes to a memory cell before it starts to fail. Did you ever try the setting "Article Cache Limit", by chance? It allows you to specify a size to cache to memory. I am thinking about trying that after I confirm my cache drive is not sleeping (need to let me queue finish, as that will definitely keep my cache up and running).
-
Thanks everyone! My apologies as I'm still trying to wrap my head around this--and I love step-by-steps --but basically, what I would need to do is the following, correct? - Create, for example, an rc.sabnzbd script that will launch sabnzbd called with a "start" command, and kill the process when called with a "stop" command. - Edit rc.local_shutdown to make "stop" calls to the program-specific rc.* scripts - Edit rc_files.auto_install (if I have one… I am at the airport right now so I can't look) to copy the appropriate rc.* scripts to /etc/rc.d - unraid_addon_control.auto_install (which already exists in my go script) should take care of the rest... Or am I completely off? BRiT, any chance I could see your rc.sabnzbd file? Thanks again! (Edited to correct a typo).
-
Good to know that's taken care of! Thanks!
-
So it's logical to conclude that SABnzbd will also prevent my APC UPS from shutting down the server during a power outage? That blows.
-
Hello all. I just migrated the duties of sab and sickbeard from my Mac Mini (HTPC) over to unRAID. Seems to be working great so far. Only issue I ran into was the known problem of the sickbeard cache folder using the flash drive. I believe I have that all sorted out now. What I am finding interesting is that I think sabnzbd (even idle) is preventing me from unmounting the array. Every time I've tried to unmount, the cache drive seems to get stuck on unmounting. If I browse to sab and shut it down, then the array becomes unmounted. Anyone else experience this? Am I just going to need to get in the habit of manually shutting down sab (and maybe even sickbeard) when I need to unmount/reboot? Thanks!
-
I also believe the drives you wish to use wdidle on MUST be through the onboard SATA.