kizer
-
Posts
3,746 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kizer
-
-
And I'm curious about your AsRock ION 330 + XBMC Live setup...seriously considering a setup like that, but I've been waiting for the Boxee Box, as I really want the thing to be usable as a consumer electronic device, as it were - per remote control, as a couch potato. But it's not ready yet, and XBMC is very fine...
Yeah I love it. I just add content to my unRAID setup. Turn on my AsRock and it scans it to the Library and then I grab my old school Xbox remote and get sores on my butt from sitting to long. LOL
Plays 720 and 1080 content just fine.
Probably a subject that should be discussed in another thread or I'd glady talk with you via PM so we don't clutter this one up a lot. Plus the guys over on xbmc.org are awesome for very specific questions.
-
@Blofeld
I currently have the 590 case and really like it, however I dig the side loading of drives you have there with your case. Thats nice and really handy. On my 590 I have to pull out the OEM cage just to swap out a drive and thank god I labeled every cable and my drives so I know where each thing goes back in.
I think other than doing some cable zip tieing and cleaning up you have a nifty looking machine. I just kinda pushed some of my cables around to make it a bit more tiddy. I even took some electrical tape and wraped it around my usb cable to usb drive connection to make sure it doesn't come loose. Placed my usb stick on the very bottom under and behind everything so it doesn't get touched and unplugged. Been there before. LOL
-
-
Honestly the only real reasoning behind the way I did is the box showed blue arrow in and a red arrow out up top. So I figured hey that makes complete since to me. LOL
-
Yeah I'm running the Cooler Master 590 that has a dedicated fan to blow air across the Hard Drives. It forces air into the case. I do monitor the drives and cpu now and then just to trend it some. So far so good. I do plan on picking up another cage sometime so I could move that top drive that is sitting in the 3.5 adapter and of course that will add another fan and add additional air into the case. Will I eventually need another fan up top not sure as of yet, but as I add more I'm sure I'll continue to trend and see if flipping the PSU is needed, but for now I'm doing ok.
I think the only thing I ever hear from this machine is the CPU fan. I thought about installing a passive cooler so its silent, then I thought nah its not that loud, but if I did want a quiter fan I would, but its in my office and my rack makes more noise than this thing ever will.
Heres the photos hosting via Image Shack. I'm trying not to well take over this thread so I made them small and clickable.
--|-- 
--|-- 
-
I completely agree with "Both" of you. In my case the air is of decent temperature and I wanted the air entering the case to stay so it could be used across the components opposed to a negative pressure and rely solely on the rear exhaust to cool everything.
I'm sure if my case was full of drives it would be different, but for now I'm completely happy and Right/Wrong/In different Rajahal was spot on piecing my machine together in the Budget build. It works great and you can't even here it when its there or when a drive spins up with those WD Green drives.
-
Yeah the reason I went with the way it was supposed to be installed I noticed that when I only had the lower fan on and running air would enter the case and be sucked right out the back. There wasn't a chance for air to flow in and rise up so the upper fan could pull it out.
I'm sure when I throw in my drives or install a few more front fans the upper fan that is pulling air out would either need another top fan to exhaust.
Right now my CPU is running 20-21C and my drives average 23-30C.
Yeah those budget builds are an awesome guide to building a machine. I knew that I would be limited by the Board and the additional break out cards, but honestly I don't plan on having14+ drives. I think right now I'm good at the 6 drive limit and I'll keep an eye out for a good deal on the break out cards. Since I'm not in a rush or anything.
-
Before anybody mentions. Yes I did cut the tails off the zip ties after I shot those photos.
-
Its one of the Recommended Budget builds. I'm really happy with it as of now.
Cooler Master 590 Case
AMD 2.7ghz
BioStar Mobo
2gig ram
Corsair 400watt PSU
2TB WD Parity green
1.5TB WD green
1.5TB WD green
500GB WD green
500GB WD green
I went with some locking Sata cables from Monoprice.com I decided to use all black for data, blue for cache and red for parity. Not shown in this photo is I removed the Cache drive and went with just all data.
I tried to tuck everything and keep it as simple and clean as possible. I used the 3.5 drive mount at the top and brought it down low. I noticed that the temp went from 40degrees to around 30 just by moving it. I'm guessing its feeling the cooler air down low since Im not running additional fans other than what came with the unit. I plan on swaping out the 500's with a single 1.5TB or 2TB
-
Joe L,
That new machine looks pretty cool. I like it and a bargin to boot. I think the only thing I would do is put one of those wire grills over those fans unless you don't have kids like I do that see something spinning and have to shove their finger or whatever they can grab to see if they can in fact stop the spinning blades.
-
What Joe L said. I precleared a 2TB drive while using the server for normal file acess. Seemed to work just fine. As soon as it was done, which I belive was around 36hours I added it to the array.
-
Thanks guys. I try to read the threads looking for the obvious, but sometimes I don't catch it. Yeah I'll rip more through the results thread that I have been watching looking for things that stand out.
I figured it had to log it somewhere and obviously the syslog does sound like the logical location.
-
I hope this doesn't sound stupid, but I'm going to ask anyways.
I ran the preclear earlier on a test drive and my real drives are on the way. I ran the preclear from console and I often see people posting their results. I'm guessing they are posting them from a Putty window or telnet.
How do you or can post a log from console?
-
Sorry guys. Looks like I'm an idiot. It was plugged in and it looks like I had a bad splitter. I was snug enough to read at first and then started giving me errors. Ran through fine after a reboot.
Looks like these two IDE's I'm messing with our Dinosaurs anyways I'm guessing one might even be a 5400RPM LOL. Sata ripped through the preclear around 40-49MB, but these things are taking forever around 19MB. Like you said Joe L these drives are probably not even worth the effort, but at least I get to tinker with your script some which works pretty well and get lost in the settings for a bit until my other hardware arrives.
-
Of course I just tried to run fdisk and well it says it can't read the disk. OH boy......
root@Tower:/boot# fdisk /dev/hda Unable to read /dev/hda root@Tower:/boot#
Sorry for clogging up what seems like a great thread and I know this is trival since its a tiny drive and all and maybe its just a bad drive, but I could of sworn this ran fine the last time I pulled it out. As soon as my preclear of the other drive I have running finishes I'll give the machine a reboot and take another look.
-
Ok, I ran this on an IDE drive at the same time a Sata drive was running. I noticed the heat spiked on the Sata Drive so I grabbed 80MM fan and placed it right in front of the SATA drive. Shortly afterwords I could of sworn the IDE drive was making a clicking sound, but I wasn't sure if the drive decided to die of it was my stupidity of messing with things while it was running. I stopped the pre-clear on the IDE and then decided to give it another run. This is what I see when I try it.
=========================================================================== = unRAID server Pre-Clear disk /dev/hda = cycle 1 of 1 = Disk Pre-Read in progress: % complete = ( bytes of read ) = = = = = = = = = = Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 580059647)%() : syntax error: operand expected (error token is ") ") ============================================================================ == == Disk /dev/hda has been successfully precleared == ============================================================================ root@Tower:/boot#
I know that isn't right since it really hadn't had much time to run. It is only a 12gig disk, but I was using it as a test gineau pig just so I can do some parity stuff and see what damage I could do to the array. I figured I'd beat up a 120 Sata, 12gig IDE and a 40gig IDE. Well that was the plan at least.
My 120gig disk seems to be still going strong.
-
As I'm piecing my unRAID server together since I just stumbled upon this site I currently use and will be retiring a couple of toaster style NAS's for my.
* Media collection.
- DVD Rips
- Music Rips
- Home Videos
- Tons and Tons of Photographs
* Personal files
- Tax information, wife owns a little side business
- Applications I download for one reason or another and I realize I don't want to half to download them again.
- Backup's of drivers for various computers we have laying around the house
- Website file backup. I have a website and I often backup and store files for emergency restore
Most of the time I use my setup to stream to a Linux based XBMC install in my living room and sometimes I watch XBMC in my home office on a XP machine. Might as well since all the files are centrally based on a server huh?
Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add
in User Customizations
Posted
Just got a 2TB EARS drive and dropped it into my machine with Pin 7&8 Jumpered.
I started up the script and I get a
Clearing will NOT be performed
I ran the following
preclear_disk.sh /dev/sdf
This is what ls -l /dev/disk/by-id
Generated
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD15EADS-00S2B0_WD-WCAVY1371380 -> ../../sdc
lrwxrwxrwx 1 root root 10 Sep 23 23:02 ata-WDC_WD15EADS-00S2B0_WD-WCAVY1371380-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD15EADS-00S2B0_WD-WCAVY1447030 -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 23 23:02 ata-WDC_WD15EADS-00S2B0_WD-WCAVY1447030-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20201794 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep 23 23:02 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20201794-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0138511 -> ../../sdd
lrwxrwxrwx 1 root root 10 Sep 23 23:02 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0138511-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0241582 -> ../../sdf
lrwxrwxrwx 1 root root 9 Sep 23 23:02 ata-WDC_WD5000AAVS-00ZTB0_WD-WCASU0114518 -> ../../sde
lrwxrwxrwx 1 root root 10 Sep 23 23:02 ata-WDC_WD5000AAVS-00ZTB0_WD-WCASU0114518-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY1371380 -> ../../sdc
lrwxrwxrwx 1 root root 10 Sep 23 23:02 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY1371380-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY1447030 -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 23 23:02 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY1447030-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20201794 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep 23 23:02 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20201794-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0138511 -> ../../sdd
lrwxrwxrwx 1 root root 10 Sep 23 23:02 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0138511-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0241582 -> ../../sdf
lrwxrwxrwx 1 root root 9 Sep 23 23:02 scsi-SATA_WDC_WD5000AAVS-_WD-WCASU0114518 -> ../../sde
lrwxrwxrwx 1 root root 10 Sep 23 23:02 scsi-SATA_WDC_WD5000AAVS-_WD-WCASU0114518-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Sep 23 23:02 usb-SanDisk_U3_Cruzer_Micro_000016A078713815-0:0 -> ../../sdg
lrwxrwxrwx 1 root root 10 Sep 23 23:02 usb-SanDisk_U3_Cruzer_Micro_000016A078713815-0:0-part1 -> ../../sdg1
So I'm pretty sure I have the correct drive, but so far its not agreeing with me.