aitf311

All 8 of mine are set to default as well.

trurl, I ran the command last night, and had 1 thing listed, an images folder in an installation folder for some mac software I downloaded at least a year ago and haven't touched since. I deleted the entire parent folder. I checked the tower first thing this morning and all of my drives were still spinning but the command didn't show anything being accessed.

Well it turns out I got a little excited too soon. I left for an hour with just no pcs connected to the tower, and yet all my drives are still spinning. My spin down time is set to 30 minutes.

Frank, background polling is set to 'no'.

OK so I boot into safe mode and then spun down all the disks using the spindown button. They all spun down for about 10 seconds and then gradually started to spinup again, even without any interaction with the tower. I have three pcs in my house, all Windows 8.1, and all three map my user shares as network drives (movies, music, documents). I shut down two of the pcs and removed the shares on this PC and have been going for about 10-15 minutes without the drives spinning up. That's the longest I've seen the drives stay spun down. Is this expected behavior from mapped network drives? Any way around this?

my go file has not been modified and is identical to the go-safe file. I assume this means I'm essentially always running the equivalent of safe mode, is this correct? Anyone have any ideas what this can be? These disks just keep spinning all day long.

I am having trouble getting any of my disks to spin down. On their own, they will never spin down, but I can click the disk on the main page to spin them down. When they do manage to show the spun down icon, the drive is back up and spinning within a matter of minutes...even with no use. My Setup: • Unraid 5.0.5 Pro • Motherboard: BIOSTAR Hi-Fi A85W • CPU: AMD A10-5800K • Ram: 8GB Addons: Dynamic with the following plugins • WebGui • Active Streams • Cache Dirs • Disk Health • System Info • Plugin Control PhAzE Plugins • CouchPotato • Plex Media Server • SABnzbd • Sick-Beard Disk Setup: • Unraid Flash Drive: 16GB / 15.6GB free • Parity: 4TB • Disk 1: 4TB / 1.58TB free • Disk 2: 2 TB / 118GB free • Disk 3: 3TB / 625GB free • Disk 4: 2TB / 121GB free • Disk 5: 2TB / 70.1GB free • Disk 6: 4TB / 1.03TB free • Disk 7: 2TB / 147GB free • Disk 8: 1TB / 72.4GB free • Cache Drive: 120GB SSD Shares: SMB Security Settings: Export: Yes, Security: Public • Applications o Allocation: High-water o Minimum free space: 0kb o Split level: not set o Included disks: All o Excluded disks: none o Use cache disk: Yes • Documents o Allocation: High-water o Minimum free space: 0kb o Split level: not set o Included disks: All o Excluded disks: none o Use cache disk: Yes • Media o Allocation: High-water o Minimum free space: 0kb o Split level: not set o Included disks: All o Excluded disks: none o Use cache disk: Yes • Apps (on cache drive – used with PhAzE plugins) o Allocation: High-water o Minimum free space: 0kb o Split level: not set o Included disks: All o Excluded disks: none o Use cache disk: no Users: root Disk Settings: • Enable auto start: Yes • Default spin down delay: 30 minutes • Force NCQ disabled: Yes • Enable spinup groups: No • Default partition format: MBR: 4K-aligned • Md_num_stripes: 1280 • Md_write_limit: 768 • Md_sync_window: 384 Network Settings: • Enable bonding: no • Bonding mode: active-backup (1) • Obtain IP address automatically: yes • Obtain DNS server address automatically: yes Share Settings: • Enable user shares: Yes • Included disks: All • Excluded disks: none • Use cache disk: Yes • Min free space: 2000000 • Mover schedule: Daily • Time of day: 03:40 • Mover logging: Disabled SMB Settings: • Enable SMB: Yes (Workgroup) • Workgroup: WORKGROUP • Local Master: no Folder Caching: • Folder caching function: enabled • Wait until array is online: Yes • Force disks busy: no • Suspend during ‘Mover’ process: yes • Scan user shares: Yes syslog.txt

Ahh man, I just remoted home to check on the model. It looks like Amazon did indeed send me a 2TB! I ordered it earlier this year after a sale and only put it in the server a month ago. That's what I get for not being on the ball I guess. Thank you fro the help.

I've upgraded disks many times before and have never had a problem with the drive showing the correct capacity. I recently replaced a 1TB with a 3TB, unraid saw it offered to proceed with the data-rebuild. I went through and and now I'm running low on space again. I just noticed the 3TB is showing as 2TB on the Main Unraid tab. I'm running version 5.0-rc16b. My parity is a 3TB as well. Does anyone know why this would have happened and what I can do to fix it?

Rob, I went ahead and downloaded the latest RC, and reformatted my flash drive for it. Then dropped back on my shares and key and it's back up. Thank you for your help, if you notice anything else off in the log please let me know.

Rob, I should have specified, I tried both URL's and I tried both of them again and receive a 404 for both. I appreciate the AHCI tip, that should work well.

Rob, I switched to AHCI and tried again but got the same result with http://gtower/main and \\gtower in Windows Explorer. I grabbed a new syslog, it's attached. syslog.txt

I was having some trouble getting one of my plugins to start so I restarted my tower today for the first time in a month or so. I tried going to the ip and web address http://gtower and it would not respond. So I then plugged a monitor in and rebooted and did not see anything alarming, it still went to the login and started up sickbeard/sabnzbd/couchpotato. I removed the flash drive, renamed extra to extraOLD, and config/plugins to config/pluginsOLD, and made sure the go file only had the 3 defailt lines in it. Still booted just fine, but I cannot access it. I'm attaching the syslog in hopes someone can help me out? Thank you syslog.txt

Joe, I saw another thread you were helping on where it turned out to be memory. I have stopped all custom scripts outside of vanilla unraid and default unmenu from booting in the go script. I then restarted and ran the samba start command.

OK, I'm not sure where there is a 'Start Samba' button on the official interface though.