unMENU 1.6 - now available (A major upgrade in appearance)


Recommended Posts

  • 2 weeks later...

I wanted to start a parity check off the unMenu UI, but the button is disabled: "Parity check not possible with missing or disabled disks."

 

I don't have a failed disk, but I did "skip" a slot number...I wanted to try keep a drive as almost a warm spare... it's pre-cleared, but not part of the array. The reason I skipped that slot is so that my assignments line up with my physical drive locations on the case.

 

It was really coincidental, I wasn't planning on using the last slot, ever (thought I couldn't physically fit another drive in the case).. but when I saw the room, I stuck in a smaller 1TB drive, that would've otherwise just been wasted.

 

Is there a safe workaround to this? Or should I just bite the bullet and assign that 6th disk?

Link to comment

I wanted to start a parity check off the unMenu UI, but the button is disabled: "Parity check not possible with missing or disabled disks."

 

I don't have a failed disk, but I did "skip" a slot number...I wanted to try keep a drive as almost a warm spare... it's pre-cleared, but not part of the array. The reason I skipped that slot is so that my assignments line up with my physical drive locations on the case.

 

It was really coincidental, I wasn't planning on using the last slot, ever (thought I couldn't physically fit another drive in the case).. but when I saw the room, I stuck in a smaller 1TB drive, that would've otherwise just been wasted.

 

Is there a safe workaround to this? Or should I just bite the bullet and assign that 6th disk?

let me take a quick look.

 

Joe L.

Link to comment

I wanted to start a parity check off the unMenu UI, but the button is disabled: "Parity check not possible with missing or disabled disks."

 

I don't have a failed disk, but I did "skip" a slot number...I wanted to try keep a drive as almost a warm spare... it's pre-cleared, but not part of the array. The reason I skipped that slot is so that my assignments line up with my physical drive locations on the case.

 

It was really coincidental, I wasn't planning on using the last slot, ever (thought I couldn't physically fit another drive in the case).. but when I saw the room, I stuck in a smaller 1TB drive, that would've otherwise just been wasted.

 

Is there a safe workaround to this? Or should I just bite the bullet and assign that 6th disk?

let me take a quick look.

 

Joe L.

You should now be able to check for/install updates (on the user-scripts page) and have that button work as expected.
Link to comment

You should now be able to check for/install updates (on the user-scripts page) and have that button work as expected.

 

 

Whoa nice! Button is re-enabled. I started a restore from Crashplan...  as soon as that is done, will fire off a parity check. Thanks for the quick update Joe!

Link to comment

You should now be able to check for/install updates (on the user-scripts page) and have that button work as expected.

 

 

Whoa nice! Button is re-enabled. I started a restore from Crashplan...  as soon as that is done, will fire off a parity check. Thanks for the quick update Joe!

You were the first to report the issue.  (most people do not leave open slots)  Fix was easy.
Link to comment

You were the first to report the issue.  (most people do not leave open slots)  Fix was easy.

 

OT:

woot! first at something, for a change. Only open until i reach Max storage or experience a failure. Last month, I moved my drive cables from on-board to an LSI card... upon rebooting, I had a short on my PSU that caused a bright, visible short. Taught me a valuable lesson: a reboot can sometimes CAUSE issues. So it's good to keep a warm spare handy. When i'm at max capacity, time to put server #2 together!

 

 

Link to comment

I know this has been somewhat covered before but I have a M1015 and can't seem find where to edit in the unmenu files to get my disk temps on the "Main" page.

 

I removed "-d ata" from everywhere in 09-unmenu-disk_mgmt.awk so that fixes running smart on the "Disk Management" tab.

 

"smartopt -A" in the drive info page fixes everything for "myMain."

 

Only thing I can't figure out is the temps on "Main." I get them for the drives connected to the mobo but not the m1015.

 

grep -r "\-d ata" /boot/unmenu/ didn't show anything that appeared to be it.

 

Link to comment

You were the first to report the issue.  (most people do not leave open slots)  Fix was easy.

 

I do,  My cages are in a tower and I count slots from left to right, bottom to top (telco style ;D).  So my parity drive is the bottom left and the cache is the most top/right position.  I then skipped every other slot as I added drives.  The helped keep the parasitic heat down, i.e the heat from a spinning drive affecting the adjacent drive.  This was only an issue when all drives are spinning in a parity check.

 

This makes disk 1 the second slot in the bottom cage. Disk 5 is the left most disk in the second cage etc.  This makes it very easy to locate/ associate a physical disk with its logical assignment in Unraid.

Link to comment

Just updated unmenu with the recent changes and it's showing temps on Main now. I noticed unmenu.awk was updated. Was something fixed there?

 

 

I know this has been somewhat covered before but I have a M1015 and can't seem find where to edit in the unmenu files to get my disk temps on the "Main" page.

 

I removed "-d ata" from everywhere in 09-unmenu-disk_mgmt.awk so that fixes running smart on the "Disk Management" tab.

 

"smartopt -A" in the drive info page fixes everything for "myMain."

 

Only thing I can't figure out is the temps on "Main." I get them for the drives connected to the mobo but not the m1015.

 

grep -r "\-d ata" /boot/unmenu/ didn't show anything that appeared to be it.

Link to comment

Just updated unmenu with the recent changes and it's showing temps on Main now. I noticed unmenu.awk was updated. Was something fixed there?

 

 

I know this has been somewhat covered before but I have a M1015 and can't seem find where to edit in the unmenu files to get my disk temps on the "Main" page.

 

I removed "-d ata" from everywhere in 09-unmenu-disk_mgmt.awk so that fixes running smart on the "Disk Management" tab.

 

"smartopt -A" in the drive info page fixes everything for "myMain."

 

Only thing I can't figure out is the temps on "Main." I get them for the drives connected to the mobo but not the m1015.

 

grep -r "\-d ata" /boot/unmenu/ didn't show anything that appeared to be it.

yes, I made it a bit smarter.  ;D

It first tries to get the temps without "-d ata", and if no luck, tries with "-d ata"

 

Joe L.

Link to comment

I'm using unraid 5.0-rc11, and I just updated unmenu to 1.6 rev. 270 using the built-in user script - no problems there. After restarting unmenu, I checked again for updates, and this show up as available:

 

Available files on current release list:

unmenu.base.lib_2.awk :Revision: 262  Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013)

 

But it does not get installed:

 

Downloading unmenu.base.lib_2.awk

rev $Revision: 262 $ $Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013) $

1332288fd58dfdf0daa210d0fa88fff1 != d41d8cd98f00b204e9800998ecf8427e or d41d8cd98f00b204e9800998ecf8427e,  /tmp/unmenu_tmp/unmenu.base.lib_2.awk not installed

 

Any idea?  :)

Link to comment

On my esxi build I get these in the event log,  have seen one instance where they were constant most times there are only a few of them. 

 

Jun 15 12:58:30 VMTower unmenu[1526]: ERROR: Can't get value of subfeature temp1_input: Can't read (Errors)

Jun 15 12:58:30 VMTower unmenu[1526]: ERROR: Can't get value of subfeature temp2_input: Can't read (Errors)

Jun 15 12:58:30 VMTower unmenu[1526]: ERROR: Can't get value of subfeature temp1_input: Can't read (Errors)

Jun 15 12:58:30 VMTower unmenu[1526]: ERROR: Can't get value of subfeature temp2_input: Can't read (Errors)

Link to comment

I'm using unraid 5.0-rc11, and I just updated unmenu to 1.6 rev. 270 using the built-in user script - no problems there. After restarting unmenu, I checked again for updates, and this show up as available:

 

Available files on current release list:

unmenu.base.lib_2.awk :Revision: 262  Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013)

 

But it does not get installed:

 

Downloading unmenu.base.lib_2.awk

rev $Revision: 262 $ $Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013) $

1332288fd58dfdf0daa210d0fa88fff1 != d41d8cd98f00b204e9800998ecf8427e or d41d8cd98f00b204e9800998ecf8427e,  /tmp/unmenu_tmp/unmenu.base.lib_2.awk not installed

 

Any idea?  :)

 

I'm getting the same

 

the file unmenu.base.lib_2.awk in the /tmp/unmenu_tmp directory is zero bytes

 

Is google starting early?  http://lime-technology.com/forum/index.php?topic=27941.msg247553#msg247553

Link to comment

I get a similar issue -- all the updates installed except these 2 ... and I just keep getting the same "available" list, and the same failure to install with them.

 

After the Check for Updates:

 

Available files on current release list:

myMain_local.conf :Revision: 182  Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)

unmenu.base.lib_2.awk :Revision: 262  Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013)

 

 

After the Install Updates:

 

Downloading myMain_local.conf

rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$

5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442,  /tmp/unmenu_tmp/myMain_local.conf not installed

Downloading unmenu.base.lib_2.awk

rev $Revision: 262 $ $Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013) $

1332288fd58dfdf0daa210d0fa88fff1 != d41d8cd98f00b204e9800998ecf8427e or d41d8cd98f00b204e9800998ecf8427e,  /tmp/unmenu_tmp/unmenu.base.lib_2.awk not installed

Link to comment

Joe, just got around to upgrading to rc15 and was looking though my syslog I noticed a few red lines. I've seen this before so its nothing new for rc15 but just was curious if you knew what these were for / safe to ignore (i would assume so but just wanted to double check).

 

Noticed that this is only being reported to the drives directly connected to the motherboard, the drives that run through the sas controllers do not show anything.

 

WDC WD30EZRX-00DC0B0 is my parity drive. its directly connected to the mobo.

WDC WD30EZRX-00MMMB0 is disk5 also directly connected to the mobo.

 

Motherboard bios should is the latest (just double checked per MSI's site), ACPI is enabled...

Jun 15 11:43:31 husky kernel: DMI: MSI MS-7752/Z77A-G45 (MS-7752), BIOS V2.10 02/28/2013

 

Jun 15 11:43:31 husky kernel: ACPI Warning: 0x0000f040-0x0000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) (Minor Issues)
...
Jun 15 11:43:31 husky kernel: ata2.00: ATA-9: WDC WD30EZRX-00DC0B0,      WD-WMC1T1598435, 80.00A80, max UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ata2.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f504dbd0), AE_NOT_FOUND (20130117/psparse-537) (Errors)
Jun 15 11:43:31 husky kernel: ata2.00: configured for UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f504db88), AE_NOT_FOUND (20130117/psparse-537) (Errors)
Jun 15 11:43:31 husky kernel: ata1.00: ATA-8: WDC WD30EZRX-00MMMB0,      WD-WCAWZ2293818, 80.00A80, max UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f504db88), AE_NOT_FOUND (20130117/psparse-537) (Errors)

Link to comment

I'm using unraid 5.0-rc11, and I just updated unmenu to 1.6 rev. 270 using the built-in user script - no problems there. After restarting unmenu, I checked again for updates, and this show up as available:

 

Available files on current release list:

unmenu.base.lib_2.awk :Revision: 262  Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013)

 

But it does not get installed:

 

Downloading unmenu.base.lib_2.awk

rev $Revision: 262 $ $Date: 2013-04-15 22:23:54 -0400 (Mon, 15 Apr 2013) $

1332288fd58dfdf0daa210d0fa88fff1 != d41d8cd98f00b204e9800998ecf8427e or d41d8cd98f00b204e9800998ecf8427e,  /tmp/unmenu_tmp/unmenu.base.lib_2.awk not installed

 

Any idea?  :)

let me investigate.  Clearly, its checksum does not match that expected, but until I look, I won't know why.
Link to comment

unmenu.base.lib_2.awk never really existed as part of the distribution.  It was a copy I had made of unmenu.base.lib.awk.

 

My release list creation script picked it up as a new file to be distributed, but I had never added it to google.code, so it was not available to be downloaded, therefore you ended up with a zero byte file.

 

I've fixed the release list and updated it on google.cde.

 

I'm not sure if the announcement on google.code directly affects how I'm using it to update unMENU, but it appears as if the initial "download" page will be going away at some point for the initial zip file.

 

We'll eventually see for sure next year.  One way or anther, we'll figure it out.

 

for now, you can just delete unmenu.base.lib_2.awk.

 

As far as  myMain_local.conf , you've apparently made some local changes, so any installation of a replacement must be done by merging the change with your local version.

 

I think the most recent changes in it were in the expected sizes for 4TB drives, to keep them from being flagged as possibly having an HPA.

Link to comment

Joe, just got around to upgrading to rc15 and was looking though my syslog I noticed a few red lines. I've seen this before so its nothing new for rc15 but just was curious if you knew what these were for / safe to ignore (i would assume so but just wanted to double check).

 

Noticed that this is only being reported to the drives directly connected to the motherboard, the drives that run through the sas controllers do not show anything.

 

WDC WD30EZRX-00DC0B0 is my parity drive. its directly connected to the mobo.

WDC WD30EZRX-00MMMB0 is disk5 also directly connected to the mobo.

 

Motherboard bios should is the latest (just double checked per MSI's site), ACPI is enabled...

Jun 15 11:43:31 husky kernel: DMI: MSI MS-7752/Z77A-G45 (MS-7752), BIOS V2.10 02/28/2013

 

Jun 15 11:43:31 husky kernel: ACPI Warning: 0x0000f040-0x0000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) (Minor Issues)
...
Jun 15 11:43:31 husky kernel: ata2.00: ATA-9: WDC WD30EZRX-00DC0B0,      WD-WMC1T1598435, 80.00A80, max UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ata2.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f504dbd0), AE_NOT_FOUND (20130117/psparse-537) (Errors)
Jun 15 11:43:31 husky kernel: ata2.00: configured for UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f504db88), AE_NOT_FOUND (20130117/psparse-537) (Errors)
Jun 15 11:43:31 husky kernel: ata1.00: ATA-8: WDC WD30EZRX-00MMMB0,      WD-WCAWZ2293818, 80.00A80, max UDMA/133 (Drive related)
Jun 15 11:43:31 husky kernel: ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)
Jun 15 11:43:31 husky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) (Errors)
Jun 15 11:43:31 husky kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f504db88), AE_NOT_FOUND (20130117/psparse-537) (Errors)

Those lines have the word "Error" within them.    I have no idea how important they are on your system.    ACPI = Advanced Configuration and Power Interface, so something n your server cannot be controlled via it.  It might be harmless, as the device might just not have that capability. 

 

In any case, it is not an unMENU issue, as it highlighted the line with the word "Error" on it.  You can open up a thread in the general support forum if you have further questions...  You might want to do a quick google search first...

http://www.linuxquestions.org/questions/slackware-14/acpi-error-%5Bdssp%5D-namespace-lookup-failure-ae_not_found-on-slackware-14-64-bit-4175448907/

Link to comment

First off - thanks for unMENU Joe.  It's a really useful tool that greatly enhances unRAID.

 

Could you add a button on the Disk Management page that runs hdparm -tT /dev/sda on the chosen drive?  Or is there a reason it's not already included?

I suppose I could, but there is a button on the user-scripts page that does exactly that, but for all the drives.  It is labeled "Disk Speed Test"  Does it not work for you?
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.