ironicbadger

Community Developer
  • Posts

    1396
  • Joined

  • Last visited

Everything posted by ironicbadger

  1. Just trying out upstatsboard with a completely stock config but I get an error others have had: root@epsilon:/mnt/user/appdata/upstats/config# cat config.js var config = module.exports = { // What mode do you want to run? // - normal: // Nothing is outputted to the console. // Logs are stored in logs/debug.log // NO debugging code is logged. // - debug: // Logs are displayed in the console as well as logged to file logs/debug.log // Debug logs are store and displayed as well. "runningMode": "debug", // Server Settings. "host": "0.0.0.0", "port": 8024, //"webRoot": "", // Allow UpsBoard check for new updates on startup and every 12 hours. "checkForUpdates": true, // Optional, If you want to stop the page requesting updates. "debugStopUpdating": false, // Optional, If you want to log the http requests. "logHttpRequests": true, // Required, Pick a username and password, On first run the password will get encrypted. "username": "admin", "userPassword": "[$2a$10$TXQLkx5aGtuUHusl050BM.jcwXGuDR0kr9gMT8.is7Y.WmIILdpTe]", // Optional, Either url, path, or email address(Gravatar) for user avatar. //"userAvatar": "", // Optional, If you want to include Google Analytics //"googleAnalyticsId": "", //"googleAnalyticsUrl": "", "drives": { "Label":{ "remote": false, "location": "/", // Optional, If your drive is on a machine running something other than linux. // Support Operating Systems: // mac & linux "os": "linux", // Required, if this is a remote drive. "host": "", "port": 22, "username": "", // One of the following are required. // "password": "", //// ssh-agent for linux // "sshAgent": true, //// Public/Private Key // "privateKey": "", // Absolute location of key. // "passphrase": "", // If public key, then leave empty. // Optional, Allow you to specify a total drive space. // Format: // (Size)(Unit) // Size: Any whole number. // Unit: Can be any of the following: // B, KB, MB, GB, TB, PB, EB // Example: // total: "5TB", total: "", // Optional, If you want to give the drive a different icon. icon: "" } }, "memory": { "Label": { // This allows you to display on bottom bar, when you have multiple memory monitors. "default": true, // Optional, If your getting the memory of a machine running something other than linux. // Support Operating Systems: // linux "os": "linux", // Required, if this is a remote server. "host": "", "port": 22, "username": "", // One of the following are required. // "password": "", //// ssh-agent for linux // "sshAgent": true, //// Public/Private Key // "privateKey": "", // Absolute location of key. // "passphrase": "", // If public key, then leave empty. } }, "bandwidthServers": { "Label": { // This allows you to display on bottom bar, when you have multiple bandwidth monitors. "default": true, // [Download, Upload] "maxSpeed": [100, 100], "remote": false, // Optional, Allow you specify if you have a bandwidth cap/limit. // Format: Download,Upload:10TB = If you bandwidth includes both upload and download, 10 terabytes is the cap. // Example: Upload:20TB = Only have a cap on your upload of 20 terabytes. // Download:20TB = Only have a cap on your download of 20 terabytes. // Download,Upload:250GB = Your whole connection is capped at 250 gigabytes. "cap": "", // Optional, Select the interface to to watch "interface": "eth0", // Optional, Select the path of vnStat, if not at the default location. "vnstatPath": "/path/to/vnstat", // Optional, Allows you specify the directory of the vnstat, if it is not at the default location. "vnstatDBDirectory": "/path/to/database/directory", // Required, if this is a remote server. "host": "", "port": 22, "username": "", // One of the following are required. // "password": "", //// ssh-agent for linux // "sshAgent": true, //// Public/Private Key // "privateKey": "", // Absolute location of key. // "passphrase": "", // If public key, then leave empty. } }, "services": { "Service Name": { "host": "", "port": 80, // Optional, This allows you to put a link on the button. "url": "", // Optional, Require the user to be logged in before they can see the link "loginRequired": false } }, "sabnzbd": { // Set to True if you want to disable sabnzbd from upsboard. "disable": false, // Optional, Allow user to logged out and use sabnzbd "anyoneCanUse": false, "protocol": "http://", "host": "", "port": 8080, "webRoot": "", "apiKey": "" }, "sickbeard": { // Set to True if you want to disable sickbeard from upsboard. "disable": false, "protocol": "http://", "host": "", "port": 8081, "webRoot": "", "apiKey": "" }, "plex": { "protocol": "http://", "host": "", "port": 32400, "username": "", "password": "", "recentTVSection": 2, "recentMovieSection": 1 }, // Optional, Forecast.io Api "weather": { "apiKey": "", "lat": "", "long": "", "useFahrenheit": true } }; config.version = 2; config.salt = "$2a$10$TXQLkx5aGtuUHusl050BM.";
  2. No problem. One of these days I'll get to fan control. Are the sensors in yellow above or below non critical value? See pic. I had to modify the colours so that the yellow was readable! Red = yellow btw.
  3. I bought one from x-case UK and was issued with a full refund (and got to keep it) because of it's SHOCKING build quality. The fans at the back don't even take standard 80mm fans when a motherboard is installed, just one example. Look in your pictures and you can see the fan hanging into the motherboard backing plate area by a few mm, just awful. The iStar drive caddies were OK but one of the two was faulty that I received. Sharp edges everywhere, thin flimsy panels and everything is riveted in place meaning you will have a 'fun' installation time with this case. I got half way through my build and gave up. I've never done that and been building systems for 15+ years! It was such a disappointment because if executed correctly it would have been a superb case. Score out of 10... probably a 2 because the design is soooo good but executed so poorly. === In other news: anyone want to buy this case off me ?
  4. Yes, I did read that and it is still hard to tell which and what cases will accept hard drive cages. Recently I ordered a large tower case and it had internal brackets inside for hard drives which couldn't be removed. In that case hard drive cages would not work. I do not want to limit myself with a cage I cannot install drive cages. And several on that list in that post looked like they had some internal brackets that may not be removed, hence no drive cage compatibility. I either wait and just keep my current box and deal with it and wait for more 8TB drives to come out, then I won't need cages at all or try and find a fully bare "inside" case. Several of the cases listed do as you say have brackets inside which cannot be removed, have you heard of a Dremel? I took one to my Antec 900 and it now houses 3x 5x 3.25" caddies.
  5. Thank you for this plugin. Just installed it with my new Asrock C2750D4I and can confirm it works out the box with no configuration required. Some of my sensors are showing as yellow (the voltages mainly) though. Nice work!
  6. This would be very useful. Integration with IFTTT and many other uses can occur when a decent API is opened up. Here's my +1.
  7. Perhaps via an advanced settings toggle somewhere I would find it incredibly useful sometimes to be able to modify Docker configurations when the array is stopped. Example: Disable autostart of a container before I start the array. Example: Modify a config/appdata directory if I've replaced the cache drive with a different one and moved files to different paths before the array starts and autostarts container. I understand why you might not want this as default behaviour, but it would be very to me to at least be able to modify these configs under the circumstances mentioned. An advanced / expert mode like XBMC has perhaps?
  8. Sadly not. The Plex release focuses on music, not audiobooks. I suspect it would be trivial for them to add the killer missing feature, position persistence. The whole point of an audiobook player is that it remembers where you are for you. Audible is fantastic at this. If only Plex (or any other service for that matter) would implement such a feature it would save me a ££ every month! I have a huge collection of audiobooks I legally own but don't listen too as I don't want to have to jockey for position everytime I stop listening. Any devs out there? Do this!
  9. I did 7x 3TB the last week and some took 30 but others took 48!
  10. reviving a realllllly old thread, i'd LOVE to find a good way to do this.
  11. Error: internal error: process exited while connecting to monitor: 2015-05-19T05:22:02.795843Z qemu-system-x86_64: -drive file=/mnt/user/VMs/Windows 8.1/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=none,aio=native: Could not find working O_DIRECT alignment. Try cache.direct=off. Thought I'd give KVM a go in unRAID but this was the result!
  12. Firstly, apologies if this has been covered elsewhere before but I couldn't find much with search. I'm keen to have a large cache drive present in my new system and wondered if I'd be able to utilise pooling? Ideally it would look something 256gb SSD cache drive with a 2tb failover backup if that fills up (a rare occurrence, but possible).
  13. Given that my RAID controller card just failed and caused me all sorts of headaches I'll chalk it down to that. Also, I've fully precleared and extended smart checked the drive since this log was generated and the drive appears healthy.
  14. ATA Error Count: 1818 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1818 occurred at disk power-on lifetime: 14554 hours (606 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 08 08:50:59.517 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:59.496 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 08:50:52.963 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 08:50:52.944 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:52.923 IDENTIFY DEVICE Error 1817 occurred at disk power-on lifetime: 14554 hours (606 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 08 08:50:52.944 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:52.923 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 08:50:46.389 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 08:50:46.370 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:46.349 IDENTIFY DEVICE Error 1816 occurred at disk power-on lifetime: 14554 hours (606 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 45 00 00 00 a0 08 08:50:46.370 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:46.349 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 08:50:44.741 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 08:50:44.722 SET FEATURES [set transfer mode] Error 1815 occurred at disk power-on lifetime: 14554 hours (606 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 08:50:44.722 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:44.701 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 08:50:44.671 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 08:50:44.652 SET FEATURES [set transfer mode] Error 1814 occurred at disk power-on lifetime: 14554 hours (606 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 08:50:44.652 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 08:50:44.631 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 08:50:44.601 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 08:50:44.582 SET FEATURES [set transfer mode]
  15. Wow that is some spectacularly bad design from syncthing.
  16. RDP is a valid category IMHO. Providing an entire desktop experience, or teamviewer or whatever is appropriate in my view for this category.
  17. As you all said, I needed the array to be running in order for this to work. I cancelled the clearing on one of my older drives that I know is fine and added it to the array and the unassigned drives showed up, including preclear progress. Bit annoying but I suspect probably an edge case problem.
  18. I haven't got anything in my array, at all as I nuked the config with my partition tables got trashed. Perhaps a weird idiosyncrasy (bug) I've found?
  19. Do you have any unassigned devices? If not, that's why it doesn't show up. I have 6...
  20. [me=ironicbadger]goes to check the dynamix plugins[/me]
  21. Yes but unRAID trashed my partition tables for me, so I have no array. I can't imagine I'd be alone in wanting this to show up even when the array isn't running? Think of a new user for example... They'd have no data either and be in a similar position to me.
  22. The preclear progress indicator is still in. Dynamix (SF) looks for the file /tmp/preclear_stat_<device> and if existing it will print its contents (this is the progress information supplied by the preclear script). To make the progress information visible, the drive must be listed under the "Unassigned Devices" though. Where exactly? Another observation is that the dashboard CPU utilisation doesnt seem to match what I get in htop, at all.