September 30, 200817 yr Sorry, I thought I quoted Ropo when I replied. By "that" I meant Ropo's commands (specifically the second line) in his go file. I do thing anyhow as thinking Joe.L in code below: nohup sh -c "while true; do awk -W re-interval -f /boot/unmenu.awk; done" >/dev/null 2>&1 &
October 1, 200817 yr Looks like 4.4b2 broke the temperature readings in unmenu. Probably due to the Smartmontools update from 5.36 to 5.38 Edit... smartctl doesn't work at all.... the c++ library needs to be updated.
October 1, 200817 yr Looks like 4.4b2 broke the temperature readings in unmenu. Probably due to the Smartmontools update from 5.36 to 5.38 Edit... smartctl doesn't work at all.... the c++ library needs to be updated. Sounds like there will be a 4.4b3 with the proper libraries. Joe L.
October 1, 200817 yr Author Here's a link to 12.0 CXX Libs http://packages.slackware.it/package.php?q=12.0/cxxlibs-6.0.8-i486-4 Download to your flash, telnet in and run installpkg cxxlibs-6.0.8-i486-4.tgz
October 1, 200817 yr Can anyone save me a ton of time and put up a sensors.conf for lm-sensors on the Abit AB9pro
October 1, 200817 yr Won't help you w/o hardware monitoring in the kernel.... or at least the proper modules properly compilled.
October 1, 200817 yr BubbaRaid is what you want Version 0.0.3 has hardware monitoring enabled, and a host of sensor chip modules.... along with perl so you can run "sensors-detect" and detect the sensors. It also has phpSysInfo, so you can view hardware temps, voltages, and other info via the browser.
October 1, 200817 yr Just a tease to show a Package Manager plug-in to unmenu.awk that bubbaQ and I have been working on. It uses easy to define package configuration files to display, download, and install extra software packages on your unraid server. It is not yet finished, but a great part of the user-interface is in place. The data shown on the unmenu web-server "Package Manager" screen is read from small text files that describe and define a package. Packages can be in "installpkg" format, ".zip" format, in fact, just about any format we have the ability to work with on the unRAID server. The actual installation commands are part of the configuration file. It will probably be next week before I have a public version available, but here is a screenshot of the work in progress. Joe L.
October 5, 200817 yr I am in the process of setting up a test unraid server to try out bubbaraid and experiment with some things. For now, it has no parity. When I bring up the main page, a row is present forthe non-existent parity drive with the following values: Status: DISK_DSBL_NP (in RED) Disk:-parity Mounted:(blank) Device: /dev/ Model/Serial: _ Temp: * Reads/Writes/Errors: 0 Size/Used/%Used/Free: (blank) The only thing that looks kind of bad is the lengthy status.
October 5, 200817 yr I am in the process of setting up a test unraid server to try out bubbaraid and experiment with some things. For now, it has no parity. When I bring up the main page, a row is present forthe non-existent parity drive with the following values: Status: DISK_DSBL_NP (in RED) Disk:-parity Mounted:(blank) Device: /dev/ Model/Serial: _ Temp: * Reads/Writes/Errors: 0 Size/Used/%Used/Free: (blank) The only thing that looks kind of bad is the lengthy status. Well, it is the internal STATUS... I suppose we can alias it to something shorter... Any suggestions on how to handle this? I can actually use the whole line to say it is not present, but figured you might have a suggestion for the affiliated description. Since it is not present, I'm not sure if it should be in "red." Your thoughts on the color? Joe L.
October 5, 200817 yr Just my suggestion, show in black: Status: not present (DISK_DSBL_NP) By the way, absolutely awesome demo of the Package Manager! Will there be a 'Base' package, that includes a few basic libs and necessities, plus sets up the initial recommended folder tree and go script additions? I wonder if it would be possible if it could also indicate very roughly someone's estimate of the memory hit, if a particular package was installed. It would be nice to know if the hit was closer to 10K, 100K, 1MB, 10MB, etc. Or perhaps roughly categorized as Negligible (less than 10K), Light (10K to 500K), Moderate (500K to 10MB), Heavy (greater than 10MB).
October 5, 200817 yr Just my suggestion, show in black: Status: not present (DISK_DSBL_NP) That is as good as any... By the way, absolutely awesome demo of the Package Manager! Will there be a 'Base' package, that includes a few basic libs and necessities, plus sets up the initial recommended folder tree and go script additions? That was my plan. A few basic packages, especially those used in the "System Info" plug-in. "lsof," "lspci", etc will be in the initial release of my plug-in. The "poweroff" script is another strong possibility. It is designed so it is easy to create a package.conf file. You do not need to edit the original supplied file, but can add your own, or download a supplied one. The files do not need to be in "installpackage" format, but they do need to be downloadable from a URL. I'll probably make a subsequent install plug-in package.conf file for the APC UPS Daemon. It is less likely to be useful to all, but the APC brand UPS supplies are pretty common, so I might be wrong about how many would be interested in invoking powerdown via the "apcupsd" command automatically in extended power outages. Do you have any suggestions at to what else might be useful in the initial package? Perhaps the "mail-notify" script that has been enhanced recently to be able to use a SSL connection? I wonder if it would be possible if it could also indicate very roughly someone's estimate of the memory hit, if a particular package was installed. It would be nice to know if the hit was closer to 10K, 100K, 1MB, 10MB, etc. Or perhaps roughly categorized as Negligible (less than 10K), Light (10K to 500K), Moderate (500K to 10MB), Heavy (greater than 10MB). Excellent Idea. I'll add a section for it to encourage its use. Certainly, you could put it in the description, but it is better as its own field. Would "Memory Usage:" be a good label for the section? Would an equivalent "CPU Usage:" label and section be a good idea as well? Joe L.
October 5, 200817 yr If you start the script with line like this in the "go" script, there is no telnet session involved, and none stay open. nohup sh -c "while true; do awk -W re-interval -f /boot/unmenu.awk; done" >/dev/null 2>&1 & I added this to my GO script and now I don't have to telnet in to start my unMENU - NICE. However, all the user scripts disappeared. Has anyone else experienced this?
October 6, 200817 yr I am in the process of setting up a test unraid server to try out bubbaraid and experiment with some things. For now, it has no parity. When I bring up the main page, a row is present forthe non-existent parity drive with the following values: Status: DISK_DSBL_NP (in RED) Disk:-parity Mounted:(blank) Device: /dev/ Model/Serial: _ Temp: * Reads/Writes/Errors: 0 Size/Used/%Used/Free: (blank) The only thing that looks kind of bad is the lengthy status. Well, it is the internal STATUS... I suppose we can alias it to something shorter... Any suggestions on how to handle this? I can actually use the whole line to say it is not present, but figured you might have a suggestion for the affiliated description. Since it is not present, I'm not sure if it should be in "red." Your thoughts on the color? Joe L. I think I'd just go with something simple like "NONE" in black, and set serial, device, and temp to blank.
October 6, 200817 yr Do you have any suggestions at to what else might be useful in the initial package? Perhaps the "mail-notify" script that has been enhanced recently to be able to use a SSL connection? My inclination is to have a base or intro package that is as light as possible, and then perhaps another more full package, with the items you listed. There will be some users who will be leery of this, of making any changes to their unRAID setup, and would only try it if it feels completely safe and simple, with as little impact and as few changes as possible to their working unRAID system. Then after getting their feet wet, they will be more likely to try additional stuff. Others are going to be leery of adding anything that might risk the stability of their system. They want unRAID just to concentrate on rock solid parity-protected file serving. But there may be one key feature that they want to add, the APC UPS package for instance, that would interest them here. As nice as some of the other little features may be, some users will only want the minimum, for maximum stability and performance. Call one the Lean and Mean package, and the other the Deluxe package with the extras (just my thoughts). Would an equivalent "CPU Usage:" label and section be a good idea as well? This one would be harder to define, partly because slow single cores will suffer much more than fast quad-cores, but also because of the different types of CPU usage. There are 2 kinds of CPU hits, one from a consistent range of CPU use (1% to 10%, average 2%), and the other from mostly minimal CPU use, but occasional very heavy spikes of 100% use. Some apps are not affected by the first, but are affected unacceptably by the second. For example, video playback has no difficulties with fairly high background CPU use, so long as it gets its CPU share, but may have unacceptable visual and audible stutter during and immediately after a 100% spike of CPU use. The other kind is easier to control. With numerous programs running in the background, it's always nice to know who is mostly to blame, and dragging the system down. The 'Memory Usage' can be a number, or range of numbers, or a descriptive label. 'CPU Usage' is probably more of a note field, for any special comments on bad CPU effects of a package. Perhaps others will have better ideas on ways to quantify it.
October 6, 200817 yr If you start the script with line like this in the "go" script, there is no telnet session involved, and none stay open. nohup sh -c "while true; do awk -W re-interval -f /boot/unmenu.awk; done" >/dev/null 2>&1 & I added this to my GO script and now I don't have to telnet in to start my unMENU - NICE. However, all the user scripts disappeared. Has anyone else experienced this? add a line above it in the "go" script to "cd" to /boot. It should look like this: cd /boot nohup sh -c "while true; do awk -W re-interval -f /boot/unmenu.awk; done" >/dev/null 2>&1 & It is looking in the directory where you start it for the scripts. (If you put the scripts elsewhere, change the "cd" command accordingly.) Joe L.
October 6, 200817 yr If you start the script with line like this in the "go" script, there is no telnet session involved, and none stay open. nohup sh -c "while true; do awk -W re-interval -f /boot/unmenu.awk; done" >/dev/null 2>&1 & I added this to my GO script and now I don't have to telnet in to start my unMENU - NICE. However, all the user scripts disappeared. Has anyone else experienced this? You know what I was going to post about the same problem. I did the same thing. If I start it via telnet I get everything but using the command for the Go script I don't have any of the scripts. Any ideas??
October 6, 200817 yr Dude....how did I miss that Thanks. Edit.... AHHHH I didn't see the next page was added...sorry
October 8, 200817 yr Quick question: Are Drives on unprotected array always spinning? cuz mine seems to be acting that way all drives that are in the array are spun down after an hour but I have 2 drives (NTFS) inside my case but not spun down. Is it normal or should I invistigate more? Thanks!
October 8, 200817 yr Quick question: Are Drives on unprotected array always spinning? cuz mine seems to be acting that way all drives that are in the array are spun down after an hour but I have 2 drives (NTFS) inside my case but not spun down. Is it normal or should I invistigate more? Thanks! It is normal, no command to spin them down has ever been issued. Tell me more how you are using those NTFS drives... are you migrating data to the protected drives?, or simply keeping the NTFS drives unprotected, but available on your LAN as a shared drive? Joe L.
October 8, 200817 yr It is normal, no command to spin them down has ever been issued. Tell me more how you are using those NTFS drives... are you migrating data to the protected drives?, or simply keeping the NTFS drives unprotected, but available on your LAN as a shared drive? Joe L. Correct I am using it as a shared drive on LAN. One drive actually a system drive (XP on it) and the other is just bunch shared of files. I am planning to use those if I build a new PC as I dont have desktop anymore.
October 8, 200817 yr It is normal, no command to spin them down has ever been issued. Tell me more how you are using those NTFS drives... are you migrating data to the protected drives?, or simply keeping the NTFS drives unprotected, but available on your LAN as a shared drive? Joe L. Correct I am using it as a shared drive on LAN. One drive actually a system drive (XP on it) and the other is just bunch shared of files. I am planning to use those if I build a new PC as I dont have desktop anymore. It sounds like you are using unmenu.awk to mount and share them. Glad it is helping by making the task easier. I'll add a line in the unmenu.awk script to set the spin-down time and a pair of buttons to spin-up and spin-down. That may help you. I didn't do it as I don't think my USB attached external drive supported spin-down/up, but yours are apparently internal. Did you install the ntfs-3g package? Any issues I should be aware of? Joe L.
October 9, 200817 yr It is normal, no command to spin them down has ever been issued. Tell me more how you are using those NTFS drives... are you migrating data to the protected drives?, or simply keeping the NTFS drives unprotected, but available on your LAN as a shared drive? Joe L. Correct I am using it as a shared drive on LAN. One drive actually a system drive (XP on it) and the other is just bunch shared of files. I am planning to use those if I build a new PC as I dont have desktop anymore. It sounds like you are using unmenu.awk to mount and share them. Glad it is helping by making the task easier. I'll add a line in the unmenu.awk script to set the spin-down time and a pair of buttons to spin-up and spin-down. That may help you. I didn't do it as I don't think my USB attached external drive supported spin-down/up, but yours are apparently internal. Did you install the ntfs-3g package? Any issues I should be aware of? Joe L. @ Joe L. That would be a nice addition to your unmenu, maybe not all will benifit from it but I'm sure I will. ;D Unmenu is really a handy and very very usefull tool for unRAID users (mounting and unmounting unprotected drive/s is just a single click) . Thanks. I am using ntfs-3g-1.2412-i486-1McD.tgz package, so far I haven't had any issue or problem that I am aware of. I transfered over a terabytes of files using NTFS-3G package; using both USB and internal connection.
Archived
This topic is now archived and is closed to further replies.