rxnelson

Apologies in advance but I have read the entire thread and don't think I saw an answer to this. Can the P4000x chassis support more than 8x3.5 drives? I've seen the posts that it can run 8x3.5 and 8x2.5 but that many 2.5 drives doesn't really interest me. Also, I'm not sure if anyone posted if one of the 5in3 cages will fit. Thanks for all the info in the thread guys. I'm looking to buy soon. Sent from my iPhone using Tapatalk

lol me too

The machine seems unresponsive to this command. I went and head and hit the reboot button. Now I guess it gets to check the parity. Are there other options to bring the system down when this command doesn't work/hangs that doesn't result in an "unclean" reboot? Thanks.

Thanks for the link. That is exactly what I was looking at. BobPhoenix, SageTV? Sent from my iPhone using Tapatalk

Any other comments on these drives? I was thinking of picking up a few but now... Sent from my iPhone using Tapatalk

No. At the risk of completely proving my ignorance I didn't know that was an option. I thought the config told the array what drives were where? Should I try something like that now?

I'll try this again then. I'm guessing nobody has noticed an appreciable difference from 4.7 to 5.x then?

I don't have Cat6 or a long enough crossover so I tested a longer Cat5e cable and a new Cat5e cable with the router in between and then just a gigabit switch in between. I'm still seeing it fall to around 12-15 MB/s for writes. Again the same cabling got over 50MB/s writing to a synology setup. What is the average (not cache) for writes on 5.0.5?

OK. So that went downhill fast but I think I recovered. I ended up recreating the 5.0.5 flash drive and making sure it booted, had network, etc. After that I copied my config in, checked the drives, and ran permissions. I'm still getting slower speeds than I recall in 4.7 and also way slower than the synology drive on the same cable. I understand it won't ever be as fast but it isn't even close and down from what I remember. Ultimately, I won't be able to readily replace every cable since one is an upstairs/downstairs run. Other ideas?

ethtool said it had a link. I'll check it an post when I get home. Thanks. Sent from my XT1053 using Tapatalk

Any ideas? It was lit up like a Christmas tree so I'm assuming it is doing a parity check. It has a link light, the router is blinking but I still can't ping it. Sent from my XT1053 using Tapatalk

Well that was a terrible idea so far. Super slow copies. ethtool revealed 10 MB link. I am tried swapping cables but now maybe the NIC is toast. No link lights. Edit: Rebooted server. Link lights are on, says link detected but can't get to it on network. Sent from my XT1053 using Tapatalk

I didn't do exactly as you said just because I didn't have time to move either machine. I did what I think is the next best thing. I tested the write speed to my Synology near the windows 7 PC. I then disconnected my Unraid server, moved the Synology to its spot and used the same network cable to plug into the Synology. Write speed in both settings was 50MB/s. Can I downgrade the server to 4.7 to retest? I have a copy of the old flash contents. I haven't made any drive changes.

Dropped packets? syslog-03112014.zip

I'm not sure if this is helpful. I don't really see anything in the log but this Tower avahi-daemon[1334]: Invalid legacy unicast query packet. I started copying a 40gig folder around 10:24 and it is still copying. syslog-03-10-20142.zip

Yes. All green 2TB. Sent from my XT1053 using Tapatalk

I upgraded to 5.0.5 tonight and am noticing slower writes than I was getting on 4.7. Copying from Windows 7 I am used to getting around 30-35MB/s write speeds. It starts there but then falls to about 12 and doesn't come back up. Copying from the server seems to be OK. I'm getting around 75-90MB/s. These numbers are from TeraCopy. syslog03092014.zip

I was just reading in 4.7 I guess it has an extra setting for AF drives. I was just trying to avoid the jumper vs. no jumper stuff. Also I wasn't totally convinced that wdidle wasn't the issue.

On first pass it doesn't look like I have the one from the 17th. I disabled and re-enabled 4 again and it completed with 754 errors according to the web gui. I don't see much in the syslog though? At this point should I upgrade to the latest 4.7? I think if I run another parity check 4 will fail again. Replace 4 rebuild then upgrade?

I may try 300. I just set them all back to 8 last night to see if issues remain.

OK...will do. disk 4 is probably shot. Over 2 million on LLC count. I imagine this is because where I store pictures. When my sagetv server goes into standby it cycles through pictures on disk 4. I am thinking it displays a few pics then parks the head every 8 seconds? syslogweb.txt smart.txt

I haven't run smart yet. It just seemed too coincidental that issues cropped up after disabling it so I thought I would see what other users experienced. On a side note, I ran a parity check for the hell of it last night and disk 4 failed again.

I don't frequent these forums but came the other day to look into adding some more disks to an Antec 1200. I noticed the threads on wdidle and the ears drives. So I went to work disabling the parking feature on all of them. The machine booted and everything looked good. Let's call that Day 0. Day 1. Web gui will not respond. Found several commands in the forum for restarting that I tried via telnet to get it working but no dice. After a few reboots and then a complete powerdown things got back to normal. Day 3. Disk 4 reports itself as bad. I unnassign it, recheck all cabling, assign it and it starts the rebuild with 1 error. Day 5. Disk 3 has reported 93 errors sometime around 7pm last night. I know it could be a freak thing but it seems my tower is now seeing unstability and disk errors that weren't commonplace before I disabled intellipark. Should I re-enable? Should I re-enable at the lower frequency instead of totally disabling? Here are some of the errors from last night. I can post a syslog but I thought this was more of a general question. Jun 17 18:51:58 Tower kernel: end_request: I/O error, dev sdj, sector 3874079887 Jun 17 18:51:58 Tower kernel: ata9: EH complete Jun 17 18:51:58 Tower kernel: md: disk3 read error Jun 17 18:51:58 Tower kernel: handle_stripe read error: 3874079824/3, count: 1 Jun 17 18:51:58 Tower kernel: md: disk3 read error Jun 17 18:51:58 Tower kernel: handle_stripe read error: 3874079832/3, count: 1 Jun 17 18:51:58 Tower kernel: md: disk3 read error Thanks.

Yea it all went pretty smooth. It took a little longer than I expected when I unassigned the parity but that was the only issue. Parity check afterwards had no errors. I guess I will check out the syslog in my spare time. Thanks.

I went ahead and picked up a combo deal on an ASUS board and sempron. Any tips on switching out mobo? Quick research just says to print my configuration and hook it back up then make sure everything looks good, maybe reassign the drives? Anything else?