petsheep

Thank you. I just worry about their latest versions and don't need the latest features. I believe 6.5.55 is stable and has the Java patch so I should be set if I ever upgrade a device.

So for both to confirm, going from 5.14.23 to 6.5.54 is a good route? No need to take any earlier 6.* version to start with and then upgrade to 6.5.54? I'm really just looking for a stable version of 6 so I can eventually get upgrade to 7. Thanks!

I am having the exact same issue. Have just started after upgrading to 6.6.3. What does "Fix Common Problems, Troubleshooting Mode" refer to?

Nice clean look with great specs! I'm very surprised you're able to idle at 18 watts with that CPU. Everything working out with onboard NIC's? No driver issues?

Thanks for the detailed reply, but this issue is in Linux, not Windows.

Thanks. I'll take a look at they setting. Would love to upgrade, but I would have to build a new system since my hardware is > 10 years old.

I recently updated from version 4.x.x to 5.0.6. I've noticed that my monitor that is connected to my server never sleeps anymore. With the previous version, my monitor would sleep (video signal off) within about 5 mins. Is there a setting somewhere that I can change to turn off the video signal? Thanks! Dan

I hate to hijack a thread, but I'm seeing sort of the same issue with an SSD drive outside of the array. I've have recently installed the SAS2LP in an PICe x16 v1 slot (2.5Gbps). The only drive I've added is an SATA II SSD which "theoretically" top out at 6.0 Gbps (but not in this case due to PCIe v1). All my array drives are hooked up to the motherboard with previous pre-clear results between 80-120 Mbps. Parity checks are also in the 100's once my weakest drive drops of. For some reason, any file I copy to the SSD, from array, from network, from ssd -> ssd, i'm topping out at 41 MB/s (using rsync --progress, obviously not rsync over network). I had much higher speeds (well over 80) for any of the aforementioned file transfers before moving the drive from the motherboard to controller card. I don't see any strange log entries or errors. SSD drive properly mounts with snap.sh. I plan on adding new > 2TB drives and I'm concerned that i'll have performance reductions due to this card. Any ideas? Thanks, Dan

Yes aware about the parity drive. Just want to make sure the SAS controller was compatible before I spend the money. Thanks for the response.

Yeah so ignore this, I made a stupid mistake and I can't delete this thread.

I upgraded to 5.0.6 from 4.7 last night. I thought everything was working until I tried to access my shares. I get "Access is denied" for all my drives. I use SMB shares and mount them in Windows 7. Not sure what to do since they unRAID was working flawlessly since 2007. Not a single folder on my 5 drives is accessible... any suggestions? BTW, nothing reported in the log when I try to access my shares. Thanks

Great, thanks for the info.

So... I've been using unRAID since about 2007 (yes, the famous ASUS P5N-VM DO MB) and haven't upgraded any of the hardware :'(... only hard drives. I'm to the point where I would like to add some > 2TB drives. I originally thought I needed a new MB, CPU, RAM, and controller card. After reading the following thread: http://lime-technology.com/forum/index.php?topic=10671 , I might not have to. Yes, this is referring to SAS, not SAS2, but I'm hoping the same should apply. Can I just add the SAS2LP in the "graphics" slot, disable PEG/PCI, and start adding new drives/re-configuring existing drives? I'm really not in the situation to rebuild my box, but I'm willing at at this point to put a BAND-AID® on to break the 2TB barrier. Thoughts? Any comments are welcome, thanks! Dan

I don't believe UnRAID supports wireless cards. I'm using the Z87E-ITX board as well and it's been very solid. I tossed the wireless card into an old laptop and use the mini PCIe for a dual sata card. Great idea with adding a SATA card to the mini PCIe slot! Was that just plug and play? No extra settings or issues to get the additional drives up and running?

I've precleared many many disks and this is the first time I'm noticing something about the Post-Read. All my array disks are spun up and they are being read from. What's going on? Have I never noticed that before? No writes are being done, just reads. Should I be concerned? putty window tells me this: ( 1,748,694,528,000 of 2,000,398,934,016 bytes read ) 109 MB/s Disk Temperature: 32C, Elapsed Time: 20:57:25 unMENU tells me this: Post-Read (1 of 3). 87% @ 41 MB/s (20:57:25) Thanks

Thanks for the feedback. My guess is not the memory or motherboard since the errors are only occurring on one drive. I can swap out the SATA cable and switch the power connector to a free one. Power supply is pretty new too.

Hey guys... after 4 years of service, I started seeing this in my log. Is my drive going bad? Anyone have ideas? Thanks! Snippet below, full log attached. Jan 27 23:06:28 flock kernel: Descriptor sense data with sense descriptors (in hex): Jan 27 23:06:28 flock kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 27 23:06:28 flock kernel: 00 68 42 10 Jan 27 23:06:28 flock kernel: sd 5:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 (Drive related) Jan 27 23:06:28 flock kernel: sd 5:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 68 41 a8 00 00 80 00 (Drive related) Jan 27 23:06:28 flock kernel: end_request: I/O error, dev sdd, sector 6832656 (Errors) Jan 27 23:06:28 flock kernel: ata4: EH complete (Drive related) Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors) Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832592/3, count: 1 (Errors) Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors) Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832600/3, count: 1 (Errors) Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors) Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832608/3, count: 1 (Errors) Jan 27 23:07:22 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Jan 27 23:07:22 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related) Jan 27 23:07:22 flock kernel: ata4.00: failed command: READ DMA (Minor Issues) Jan 27 23:07:22 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related) Jan 27 23:07:22 flock kernel: res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Jan 27 23:07:22 flock kernel: ata4.00: status: { DRDY ERR } (Drive related) Jan 27 23:07:22 flock kernel: ata4.00: error: { UNC } (Errors) Jan 27 23:07:22 flock kernel: ata4.00: configured for UDMA/133 (Drive related) Jan 27 23:07:22 flock kernel: ata4: EH complete (Drive related) Jan 27 23:07:25 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Jan 27 23:07:25 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related) Jan 27 23:07:25 flock kernel: ata4.00: failed command: READ DMA (Minor Issues) Jan 27 23:07:25 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related) Jan 27 23:07:25 flock kernel: res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) Jan 27 23:07:25 flock kernel: ata4.00: status: { DRDY ERR } (Drive related) Jan 27 23:07:25 flock kernel: ata4.00: error: { UNC } (Errors) Jan 27 23:07:25 flock kernel: ata4.00: configured for UDMA/133 (Drive related) Jan 27 23:07:25 flock kernel: ata4: EH complete (Drive related) Jan 27 23:07:27 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Jan 27 23:07:27 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related) Jan 27 23:07:27 flock kernel: ata4.00: failed command: READ DMA (Minor Issues) Jan 27 23:07:27 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related) Jan 27 23:07:27 flock kernel: res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors) syslog.txt

Unless there were open files when the system shut down I can't understand why it got corrupted. Honestly, I have hard drives and flash drives that are always plugged in and have not experienced that. It it formatted fat32? I actually experienced this again last night. I restarted and the drive was 100% full. Seems to be when I restart with out shutting down Couch Potato (as the DIR size is ~4GB on restart), the drive gets corrupted (my fault for not shutting down). What I haven't tested is when all my apps (all 3) on my snapped drive are disabled and then I restart without unsnapping. I'll save that test for another weekend . I'm pretty sure you're right, if nothing was running when I restart, I'm 99.99% sure nothing would get corrupted.

Very happy with the add-on. Thank you. I didn't read the whole thread, but I don't think this question has been answered. What happens on powerdown when I have drives snapped? Do I need to first unsnap the drives? I ask because I restarted my server this weekend and my one and only snapped drive was corrupted on reboot. It's a 256MB flash that was about 11% full. When i started up, it was 100% full and a bunch of my application files were corrupted. Luckily, I had a cronjob running nightly backing up the flash so I didn't loose any data. Either way, I would like to know if I need to add anything to the powerdown script (and how if necessary) to unmount drives. Thanks!

Question about SABnzbd I/O - how much writing is done with this package? If your temp download and complete download are in your array, what's really being written to the flash? Once the package loads on boot, what is needed from the flash? Also, having SABnzbd's log file going to /var/log/* removes that writing. What am I missing here? I'm asking because I have SABnzbd installed on my flash, but I'm not too sure how to detect the I/O. Thanks!

I wasn't specific on what was missing because in this thread you wrote "you must have the latest unMENU" which I don't have. So i added things like python, cheetah, sqlite, ect. No need for a change on your end. I just didn't want to do two updates at once... unMENU and install SAB. That's just me being me . Just wanted to give a quick update... so far so good. Haven't had any hiccups with having SAB installed to my flash drive. I know permissions were mentioned as a possible issue, but I haven't run into any. Best part is that all my drives will stay idle until I start a download... and I have RSS feeds setup to check every 30 mins. I guess my only concern is the I/O on the flash. From what I understand, majority of the I/O for this package is in memory. Not really sure when the flash I/O comes into play. Overall, very very happy. Wish I did this a long time ago. I just hate having machines sitting on and idle with only one function... now it's got two functions. Thanks again.

I wasn't specific on what was missing because in this thread you wrote "you must have the latest unMENU" which I don't have. So i added things like python, cheetah, sqlite, ect. No need for a change on your end. I just didn't want to do two updates at once... unMENU and install SAB. That's just me being me .

Ok... so installed your script. Since I didn't have the latest unMENU, I had to add missing dependencies to the .conf. You are right as the version I was using before was outdated... I didn't even realize that when I installed (i was very tired). Against your recommendation, I did install onto the flash. I'll do some testing to see how it works. I am now able to choose any /mnt/* to download to. Phew. I was actually worried about that for some reason. Other than that, so far so good. After a few days of testing, I'll modify the .conf again to get the latest version of SAB (0.6.9). Thanks for the help!

Ok, I will install yours tonight when I get home. Just one question before I install... I should be able to install to my flash and have my temp/complete dirs in any /mnt/*, correct? I just want to clear that up before I move forward. Thanks!

Which sabnzb package did you use? Mine, the 5.0b11+ one, mrmachine's original... I saw your question yesterday in the other thread but I need to know which one you are using to help at all. The information you have given above is also not enough to go on. where are you trying to change this download_dir from, I need more information and the steps you are taking to try and reproduce the problem. I used the .conf from "New unMENU packages for SABnzbd, Sick Beard and Couch Potato" thread (mrmachine). Just SABnzbd on version 4.7. I installed everything to the flash drive and have it loading on boot through unMENU. I am trying to change the temp download and completed download to /mnt/disk3/ through SABnzbd UI under config. When I click save change, i get a white screen that says "Cannot create download_dir folder /mnt/disk3/_nzbTemp". That's the only error i receive. Seems like SAB doesn't see any of my /mnt/* drives. I obviously can update the folders to /boot/* without a problem. I don't have a cache drive, and really don't want to put one in just for this application. Thanks for the help.