jimbobulator

I have a similar issue with Plex on ArchVM: I have seen the Plex DNLA server intermittently showing up on clients, but I don't really use the DLNA portion so I haven't looked into it much.

You only included a v5.0.5 syslog, so cannot tell anything about how well v6.0-beta4 booted. There appears to be a good shutdown from v5.0.5, so there should not have been any problems on the subsequent boot. There is however a small oddity in this v5 syslog, with the 2 following lines (probably not important, but worth mentioning): There are no clues as to what write was attempted, and no clue as to where. I suppose it's possible this was a write to the super.dat file on the flash drive, which could potentially cause a parity check, but no proof here at all, and seems very unlikely. Good point on the start up log, I should have known better. Of course, I do not have it because I didn't think to save it and haven't gotten powerdown up and running yet on 6b4, so that's not good... Best I could do is revert to my 5.05 backup and test to see if I can make the same behaviour occur again. Might try it later this week if I have time as I'm on the road till Wednesday at least. Thanks for the help!

Thank You. Instructions updated. With force user = root, I was not able to access the share over the network. Windows prompted me for a username/password (root password didn't work) when I tried to access the share. I removed this line from the file, and I can access and read/write the disk via SMB just fine. Note I'm using 6.0-beta4.

Just reporting a possibly strange behavior - a parity check initiated after upgrade to 6.0-beta4: I upgraded an Unraid basic install from 5.05 to 6.0-beta4. - Stopped the array and shutdown from the web interface (syslog attached). - Formatted a new key with 6.0-beta4 stock install - Copied over config from 5.05 key backup. - Booted into non-xen mode, and a parity check had started. Not sure why it's checking parity - did I do something wrong? I was running the powerdown script that was released before all the recent updates and it always worked fine. I had a few plugins and extras in 5.05 but nothing crazy, v6 was stock/barebones. Thanks! edit: entirely possible this is nothing to do with the beta. If you think so let me know and I'll take the discussion elsewhere... syslog-20140412-173334.zip

Nicinabox, like what your doing here. Great to see professional development practices applied to a community project like this. I too had the certificate errors above when I first installed boiler to try it out. I didn't know what I was doing and haven't had time to troubleshoot. I took the brute force approach and reran the installer and then everything worked for some reason. Now I get the error again (several reboots later). I clearly don't understand what's causing this but perhaps this info might help you address a potential problem (or explain what I did wrong ). Cheers and best of luck. Sent from my Nexus 4 using Tapatalk

Good points, SBD. I think my concern is not stability, its the risk of the monthly updates doing something drastic that causes difficulty for casual users. From what I've observed Arch has a history of dropping support for things quickly after adopting a new standard (this is arguably what makes it awesome too; it doesn't get hung up supporting old ways of doing things and can stay nimble). Agreed that Arch has some of the best documentation. You are right though, Centos probably isn't a great option for applications you describe. Sent from my Nexus 4 using Tapatalk

Ironic, this is great and I'm looking forward to trying it out when I have some time. I have been planning on building something similar for myself as a learning exercise (still will probably), but this is a nice way to get my feet wet in v6 and Arch. One question though: Is Arch a good long term option for an appliance VM? Maybe I'm way off here, but I would think a stable server-oriented operating system would be better suited to this type of application (Centos minimal, or similar). Far less likely to break when updating, guaranteed long support life. Would that be better suited to the average unraid user looking to offload extended functionality into a VM? Perhaps it is trivial for the maintainer of the VM appliance to update the image monthly, but I don't think it would be practical for each user to start from scratch and reconfigure or migrate settings into a new image. Maybe I'm missing something simple, it's possible; I'm learning. The beauty here is that there's nothing stopping someone from creating another image. Arch may be a nice starting point for those technically inclined people that prefer the customization, control and cleanliness it brings, but a system with better long term support, simpler/safer upgrades for non-technical users could prove useful long term. Keep up the awesome work. Thanks!

Thanks, I'll try that out tonight and let you know how it goes. Good advice on reformatting the flash. /boot/plugins has some non-dynamics plugins in it as well; safe to assume I can leave those alone?

First off, I quite like Dynamix; it's a great UI. Troubleshooting a problem here, believe it's to do with Dynamix or one of its plugins. I had a unexpected hard shut down the other day (and immediately moved my power bar to a less foot-accessible location...). There was no drive access going on at the time, and I think I had the dynamix (2.1.1) web-gui running at the time. After rebooting and a clean parity check, I'm seeing segfaults in my log every minute or so, example from log: Feb 2 15:02:01 jimbo kernel: crond[29978]: segfault at 4001e51c ip 4001e51c sp bfb7f2d8 error 15 in ld-2.11.1.so (deleted)[4001e000+1000] (Errors) This seems to be where the failure is happening: excerpt from crontab -l # System data collection - poll every minute */1 * * * * /usr/lib/sa/sa1 1 1 & 1>/dev/null 2>&1 This seems to be added for the system-stats plugin in Dynamix. Installing or un-installing any dynamix plugins from the web-gui causing the browser (chrome/W7) to freeze. I didn't do this before. The problem goes away booting into safe mode. I don't have much else installed (unmenu + some packages, boiler). Could the dynamix files on the flash have been corrupted during when the server shut down? If so, what's the best way to go about manually removing and re-installing? I'm still getting my head around which files go where and what to add/remove for a plugin / package to install on boot. I suppose I could copy my configs into a clean installation but I'd like to try fixing it for the learning opportunity. Thanks!