jbartlett

Settings > Disk Settings > Enable auto start. That said, mine doesn't seem to be sticking on Yes.

I had no issues just now with downloading the most recent beta or 4.7.

I've noticed a couple times now that viewing the UNRAID website after many hours of inactivity can cause several drives to spin up - tonight six out of the seven data drives spun up but no mention of it in the syslog. Last entry was 15 hours ago when it was spinning down the drives after the mover ran. When I tried viewing the website, it was slow to respond and I could hear the drives spinning up one at a time. When it did reply, it still indicated that all drives were spun down. Refreshing the page showed 6 out of 7 data drives had spun up.

My SATA4 port on my main PC is starting to flake out. Windows will suddenly hang and if I press the reset key, the BIOS detection on the SATA4 port will hang too. Powering down and up corrects. Mental note: I need to move the SATA4 port cable.

I wouldn't expect to see any ETA on a stable release until things settle down enough to allow for an RC release. Many of the recent betas have been to troubleshoot issues with drivers and the kernel, an RC isn't going to happen until those work themselves out.

Just a general FYI From my understanding of things behind the scenes, multiple files by the same name are only visible once, the file served is the first drive in the array that contains that file. However, UNRAID (at least with v5) does seem to know the files are duplicate and reports it in the syslog. Things seemed to get tricky when removing a copy of the file from one drive and not others when the file removed was the first drive in the array to contain that file.

I used to do PC tech support in the late 90's and one thing I hated most was when a lightning strike machine came in. They seemed to defy logic. I had one PC that would not boot (blank screen, like you're experiencing) until I left it on for no less than 10 minutes and then pressed CTRL-ALT-Del. So, good luck!

My problem is that any hard drive that exists in a certain distance from me (typically as far as I can reach) has it's lifespan cut dramatically. I built a stack of drives that failed less than one year from manufacture before I started to realize this proximity thing. Drives that exist in a different location than I frequent tend to last several years. Naturally, my UNRAID server is in a location I don't frequent. Unfortunately, I recently had a drive fail in my UNRAID server but since it's one of those EARS drives, I'm blaming the drive. Not limited to hard drives either, I've had enough motherboards fail in my work laptop to earn me a reputation at work. Currently experimenting with SDD drives.

Post your syslog.

I'm getting higher throughput on my Realtek gigabit NIC with b12a than I did with b12. With b12, Windows taskmon reported I was peaking around 60% utilization and the file transfer said it was getting around 51MB/sec. With b12a, it's getting up to 80% utilization (though not as steady as b12, network activity is "sawtoothed") and file transfer speed is 62MB/sec.

I've done nothing to correct this but now it's working.

I wasn't aware that there was talk of one? Hence the "final" label on it. It has been mentioned but I can't recall where. I believe it's in one of the 5.0 beta threads.

I recall people posting in previous beta threads that their cache drive doesn't spin down on it's own, that it's handled differently from the data drives. That said, clicking on the "Spin Down" button in the GUI does spin the cache drive down along with any active data drives. The Disk settings has one selection: "Default spin down delay", with no differentiation between data & cache drives. If things are behaving the way they are supposed to behave, then the GUI should be updated to be more clear or you'll get a never-ending question asking why the Cache drive isn't spinning down.

My understanding is the setting tells UNRAID to use the cache drive (or not) when writing new content.

Upgraded from 4.7 to b12, everything seems to be working fine with the exception that I can not access the disk2 smb share. The others are fine. I ran the fix permission process & rebooted (twice), no change. I can browse once logged in as root and I can browse via the web gui. The permissions look fine. I could access the disk2 smb share under 4.7. I can see the files on disk2 in the user shares. Syslog attached. syslog.zip