Traxxus

http://lime-technology.com/forum/index.php?topic=14424.0 And it's on sale.

Well I have never used chrome, but to get around typing tower, login on your unraid box, and type ifconfig eth0 This will return a bunch of information about the network. The second line after inet addr: is the ip address for your server. You can type in the address into your browser and that should work. Make sure it isn't being blocked by noscript or something similar. Edit: Oh missed there was a second page.

I don't list disk 1 or 2 or anything, those can change, and all you need is the serial number. I put the size, model, and last 6 #s of the serial. I do have a different color sata cable on my parity drive as a reminder.

I had no idea it could do that! I'll have to check that out. Definitely comes in handy for those late night sessions.

I'll need to pick one of these up eventually, only have 2 slots left on my motherboard for HD's. How do you cable these? Does it take a breakout cable of some sort? Or are there just 8 SATA ports on it that you use as normal?

I ran smartctl -T permissive -d ata -a /dev/sdc and got smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) === START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 1 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Aug 1 08:44:27 2011 EDT SMART is only available in ATA Version 3 Revision 3 or greater. We will try to proceed in spite of this. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Think I'll try a different cable, the sata cable used has been sitting in a box for 8 months. this worked, it now returns a proper smart report, running preclear again, I'll report back, probably just a loose cable Edit: Since it's a new page, last post on last page is my first post with syslog and stuff.

So I have issues with a new EARS drive I'm adding to the server. No jumper, upgraded to 4.7 recently in order to take advantage of the new AF formatting, and I do have it enabled in settings. Syslog is 540 MB in size, mostly the same error repeating over and over with this Aug 1 05:11:04 Tower kernel: sd 3:0:0:0: [sdc] Unhandled error code Aug 1 05:11:04 Tower kernel: sd 3:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 05:11:04 Tower kernel: sd 3:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 e2 25 cf 68 00 04 00 00 Aug 1 05:11:04 Tower kernel: end_request: I/O error, dev sdc, sector 3794128744 I took the end and beginning of the syslog and attached it. The preread appeared to go fine, took 8 hours, then failed on the write portion I presume. Smart test returns this. (full text) smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I double checked the cables and they look good, assuming that isnt the problem since the read portion appeared to go fine. Oh, and the preclear script returned this during the test. Sorry disk sdc MBR could not be precleared == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.7715e-05 s, 0.0 kB/s 0000000 == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.7715e-05 s, 0.0 kB/s 0000000 Elapsed Time: 7:40:08 dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00104791 s, 0.0 kB/s Edit: Think I fucked up that code somewhere, putty was being funny about c/p some of it. syslog.txt smart.txt

After, the parity drive will slow down the transfer. Install all your data drives, transfer files, then put in your parity drive. I always preclear anything going in the server, no downtime adding the drive, and plus, a used drive could have anything on it, deleting or formatting a drive doesn't actually erase the files. Also, year three is when failure rate goes up, so its nice to catch marginal hardware.

As someone else said, XBMC sets uses sorttitles to do what you want. http://wiki.xbmc.org/index.php?title=Movie_Sets I use Ember Media Manager for this (well its a bonus, I use it anyway to generate all my additional movie files, I prefer media streamers to have read only access just in case, so I generate everything for my stuff and copy it over in batches), it hasn't been updated in a while, but it still does it's job. It has a simple field to fill in the sort title and it will modify your nfo for you. You'll need to use this for a lot of movies, so you'll learn it fairly quickly.

Yeah it's a little expensive, but after running the free version for ~8 months (until it started filling up) and having 100% uptime with zero problems I was convinced.

What are you using to copy with? I would use Teracopy, it also has the ability to verify copies have the same hash as the original. I never have issues copying with it, even when the target disks are spun down (which could be the issue).

I had this problem, the motherboard in my server doesn't use HPA but the hard drive in question was an old storage drive I used on a windows pc, which had an HPA on it. I had always ignored it since it wasn't an issue but the upgrade to 4.7 gave me the same problem. I just used the hdparm command to remove it and check it is correct, let unraid rebuild the drive (which was showing up as blue), and am now running a parity check which should fix the space left over from the HPA. I would not do the trust parity step you were talking about. Let unraid do it's thing. Rebuild, then parity check.

I have an older 300 GB HDD that I download everything to. There I rename, delete extranous files, add nfo files and artwork via Ember Media Manager, make sure subs are included and working, then transfer to unraid server. I do use sabnzbd, but not couch or sickbeard.

Yes that is pretty much the point of an unraid server.

If you want to do a heartbeat probe right, you need to attach a monitoring device on your body to measure your BPM, and set a thermite charge over your hard drives so it will go off and melt through all the drives in succession. Then you also need to think about a anti-tamper mechanism but I'm sure Joe can help you out with that.

During a pre-clear you should get 90, down to 60-70 as it gets to the outer edges of the disk. Only time I had it drop that low was when the drive was bad and getting media errors and i/o errors. I ended up RMAing that one. Mine on a 2 TB EARS with a jumper, was finished in about 32 hours. You are at 44 hours and still in the preread stage? You still got a write stage and another preclear to go. If you can hold out til it gets to the write stage it may start showing errors that will shine some light on the problem. I believe there is also a command parameter to skip the pre-read and go directly to the writing to the disk.

So got an RMA hard drive in for the one I posted about last time about a week or so ago. It went much faster, took about 30 hours with no errors except for the stuff at the end. Nov 27 17:36:29 Tower dhcpcd[1272]: sending DHCP_REQUEST for 192.168.1.101 to 192.168.1.1 Nov 27 17:36:29 Tower dhcpcd[1272]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 27 17:36:29 Tower dhcpcd[1272]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Nov 27 17:36:29 Tower dhcpcd[1272]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Nov 27 17:36:29 Tower dhcpcd[1272]: DHCP_ACK received from (192.168.1.1) and Nov 26 17:50:52 Tower preclear_disk-start[2172]: SMART Self-test log structure revision number 1 Nov 26 17:50:52 Tower preclear_disk-start[2172]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Nov 26 17:50:52 Tower preclear_disk-start[2172]: Nov 26 17:50:52 Tower preclear_disk-start[2172]: Nov 26 17:50:52 Tower preclear_disk-start[2172]: SMART Selective self-test log data structure revision number 1 Nov 26 17:50:52 Tower preclear_disk-start[2172]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 26 17:50:52 Tower preclear_disk-start[2172]: 1 0 0 Not_testing Nov 26 17:50:52 Tower preclear_disk-start[2172]: 2 0 0 Not_testing Nov 26 17:50:52 Tower preclear_disk-start[2172]: 3 0 0 Not_testing Nov 26 17:50:52 Tower preclear_disk-start[2172]: 4 0 0 Not_testing Nov 26 17:50:52 Tower preclear_disk-start[2172]: 5 0 0 Not_testing Nov 26 17:50:52 Tower preclear_disk-start[2172]: Selective self-test flags (0x0): Entire syslog and smart report is attached just in case. It will be the first parity drive for this new server with my two 2 TB drives. Not testing what and why not? syslog-2010-11-28.txt smart.txt

All right, thanks for the clarifications, havent seen a normal preclear yet so didn't really have a baseline for it. Hopefully the RMA will be up to snuff.

Yes you can just close it out it will be fine, it will start over from the beginning though when you restart.

Indeed, just glad i decided to give it a try. The preclear finally moved onto the writing to disk stage, and started putting out a different error, this error kept repeating in the syslog until it was over a GB in size, and it was only 7% done, so I had to close it out, didn't want it to crash the server. Obviously cant post it all, but its basically just this repeating over and over added onto the previous syslog Nov 6 18:17:39 Tower kernel: Descriptor sense data with sense descriptors (in hex): Nov 6 18:17:39 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 6 18:17:39 Tower kernel: 05 ef 2f 68 Nov 6 18:17:39 Tower kernel: sd 1:0:0:0: [sda] ASC=0x0 ASCQ=0x0 Nov 6 18:17:39 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 05 ef 2f 68 00 04 00 00 Nov 6 18:17:39 Tower kernel: end_request: I/O error, dev sda, sector 99561320 Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: ata1: EH complete Nov 6 18:17:39 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 18:17:39 Tower kernel: ata1.00: irq_stat 0x40000001 Nov 6 18:17:39 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 6 18:17:39 Tower kernel: ata1.00: cmd 35/00:00:68:33:ef/00:04:05:00:00/e0 tag 0 dma 524288 out Nov 6 18:17:39 Tower kernel: res 61/04:00:68:33:ef/4d:04:05:00:00/e0 Emask 0x1 (device error) Nov 6 18:17:39 Tower kernel: ata1.00: status: { DRDY DF ERR } Nov 6 18:17:39 Tower kernel: ata1.00: error: { ABRT } Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: failed to enable AA(error_mask=0x1) Nov 6 18:17:39 Tower kernel: ata1.00: configured for UDMA/133 (device error ignored) Nov 6 18:17:39 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Nov 6 18:17:39 Tower kernel: sd 1:0:0:0: [sda] Sense Key : 0xb [current] [descriptor However, smart test for the drive shows up as fine with no errors, no sectors pending or reallocated. There are a bunch of other fault codes though. It is attached. smart.txt

I'll just wait, not in a huge hurry to add it and it's the weekend anyway. Kind of interesting to see what happens with bad hard drives so I can recognize them in the future. I'll RMA it on Monday. This is the third hard drive I have acquired for my server, but the first one I have used preclear on. It's a good thing I did, intended to use this one as a parity drive.

I'm having problems preclearing a new disk i got, it starts out fine on step one but after about 10 mins it slows down to a crawl, like ~4 MB/s down from ~100/s, it only updates the screen every 5 mins or so at this point as well, it should be doing so every 10 seconds I believe. I stopped the process and restarted a couple times, and restarted the server but it is still doing the same thing. This isn't how it should go is it? Syslog attached, let me know if there is another log somewhere that will help. Edit: It's been an hour now and only 3% into the pre read. Edit part deux: Now it's back up to 100/s, am I just being too impatient? Getting errors now, updated syslog here http://pastebin.ca/1983708

Excellent, I can finally add a parity drive to my new box, been getting a little nervous waiting for them to hit 80 again. (Also don't forget they don't include the jumper)

Name one that is an unstriped RAID5 implementation, which runs on off-the-shelf generic hardware. None? Do I win a lollypop? I'm not sure what you're getting at. I'm fully aware it will be a pain to 'fix' unraid, but it's all in the software. Not fixing it because 'its hard' isn't really a very good excuse. I should also add, as bjp999 said I'm not sure why people are getting so irate and argumentative. a) Whatever we discuss here doesn't fix or solve anything b) people seem to be diving down my neck for suggesting it would be nice to have a better idea of how limetech will handle it. The post linked to by bjp is almost 5 months old and we're now about to hit the conditionals for not doing it laid out in that post. I think that's a fairly reasonable thing to *ask* (note, not *demand*) an update for. Agreed, way too much hostility here over a simple question. If people forgot the original question that started this... The question wasn't will current hardware work with it, why won't AF drives work with unraid, what do you guys think about the problems, what drives can we just not use at all, or whatever other answers have been brought up. It was simply what is his plans for supporting hard drives that cannot currently be used (without workarounds).

I don't know the answer to your question. However, why use Windows at all? XBMC Live will boot and run much faster than XBMC on top of Windows. Indeed, would probably be a bit more user friendly for the not so tech savvy family members, but I use it for a lot more like hulu, netflix, emulators, etc.