September 7, 201411 yr hi Joe server r2d2 root@R2D2:/# /root/mdcmd status | strings | grep loo root@R2D2:/# server p8h67 root@P8H67:/# /root/mdcmd status | strings | grep loo root@P8H67:/# r2d2 without the grep root@R2D2:/# /root/mdcmd status | strings sbName=/boot/config/super.dat sbVersion=2.2.0 sbCreated=1406786502 sbUpdated=1409912139 sbEvents=24 sbState=0 sbNumDisks=14 sbSynced=0 sbSyncErrs=0 mdVersion=2.3.0 mdState=STARTED mdNumProtected=14 mdNumDisabled=1 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=0 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=0 mdResyncCorr=0 mdResyncPos=0 mdResyncDt=0 mdResyncDb=0 diskNumber.0=0 diskName.0= diskSize.0=0 diskState.0=4 diskId.0= rdevNumber.0=0 rdevStatus.0=DISK_DSBL_NP rdevName.0= rdevSize.0=0 rdevId.0= rdevNumErrors.0=0 rdevLastIO.0=0 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=1953514552 diskState.1=7 diskId.1=SAMSUNG_HD204UI_S2H7J9JB614304 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sdn rdevSize.1=1953514552 rdevId.1=SAMSUNG_HD204UI_S2H7J9JB614304 rdevNumErrors.1=0 rdevLastIO.1=0 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=1953514552 diskState.2=7 diskId.2=WDC_WD20EARX-00PASB0_WD-WMAZA8611843 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdm rdevSize.2=1953514552 rdevId.2=WDC_WD20EARX-00PASB0_WD-WMAZA8611843 rdevNumErrors.2=0 rdevLastIO.2=0 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=976762552 diskState.3=7 diskId.3=Hitachi_HDT721010SLA360_STF607MH3N350K rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdc rdevSize.3=976762552 rdevId.3=Hitachi_HDT721010SLA360_STF607MH3N350K rdevNumErrors.3=0 rdevLastIO.3=1410097247 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=1953514552 diskState.4=7 diskId.4=WDC_WD20EARX-00PASB0_WD-WCAZAC672415 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdg rdevSize.4=1953514552 rdevId.4=WDC_WD20EARX-00PASB0_WD-WCAZAC672415 rdevNumErrors.4=0 rdevLastIO.4=0 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=976762552 diskState.5=7 diskId.5=WDC_WD10EARS-00Y5B1_WD-WCAV5M103508 rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sdd rdevSize.5=976762552 rdevId.5=WDC_WD10EARS-00Y5B1_WD-WCAV5M103508 rdevNumErrors.5=0 rdevLastIO.5=1410097657 rdevSpinupGroup.5=0 diskNumber.6=6 diskName.6=md6 diskSize.6=1953514552 diskState.6=7 diskId.6=ST2000DM001-1CH164_Z1E4BSSC rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdh rdevSize.6=1953514552 rdevId.6=ST2000DM001-1CH164_Z1E4BSSC rdevNumErrors.6=0 rdevLastIO.6=1410097534 rdevSpinupGroup.6=0 diskNumber.7=7 diskName.7=md7 diskSize.7=976762552 diskState.7=7 diskId.7=WDC_WD10EACS-00D6B0_WD-WCAU45503540 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=sdi rdevSize.7=976762552 rdevId.7=WDC_WD10EACS-00D6B0_WD-WCAU45503540 rdevNumErrors.7=0 rdevLastIO.7=1410096902 rdevSpinupGroup.7=0 diskNumber.8=8 diskName.8=md8 diskSize.8=976762552 diskState.8=7 diskId.8=WDC_WD10EARS-00MVWB0_WD-WCAZA0747326 rdevNumber.8=8 rdevStatus.8=DISK_OK rdevName.8=sdj rdevSize.8=976762552 rdevId.8=WDC_WD10EARS-00MVWB0_WD-WCAZA0747326 rdevNumErrors.8=0 rdevLastIO.8=1410097247 rdevSpinupGroup.8=0 diskNumber.9=9 diskName.9=md9 diskSize.9=976762552 diskState.9=7 diskId.9=WDC_WD10EADS-00L5B1_WD-WCAU4D176083 rdevNumber.9=9 rdevStatus.9=DISK_OK rdevName.9=sdk rdevSize.9=976762552 rdevId.9=WDC_WD10EADS-00L5B1_WD-WCAU4D176083 rdevNumErrors.9=0 rdevLastIO.9=0 rdevSpinupGroup.9=0 diskNumber.10=10 diskName.10=md10 diskSize.10=976762552 diskState.10=7 diskId.10=WDC_WD10EADS-11M2B2_WD-WCAV5A500947 rdevNumber.10=10 rdevStatus.10=DISK_OK rdevName.10=sdb rdevSize.10=976762552 rdevId.10=WDC_WD10EADS-11M2B2_WD-WCAV5A500947 rdevNumErrors.10=0 rdevLastIO.10=0 rdevSpinupGroup.10=0 diskNumber.11=11 diskName.11=md11 diskSize.11=1953514552 diskState.11=7 diskId.11=TOSHIBA_DT01ACA200_83PZV9LKS rdevNumber.11=11 rdevStatus.11=DISK_OK rdevName.11=sdf rdevSize.11=1953514552 rdevId.11=TOSHIBA_DT01ACA200_83PZV9LKS rdevNumErrors.11=0 rdevLastIO.11=1410096900 rdevSpinupGroup.11=0 diskNumber.12=12 diskName.12=md12 diskSize.12=976762552 diskState.12=7 diskId.12=WDC_WD10EARS-00Y5B1_WD-WCAV5W578010 rdevNumber.12=12 rdevStatus.12=DISK_OK rdevName.12=sde rdevSize.12=976762552 rdevId.12=WDC_WD10EARS-00Y5B1_WD-WCAV5W578010 rdevNumErrors.12=0 rdevLastIO.12=0 rdevSpinupGroup.12=0 diskNumber.13=13 diskName.13=md13 diskSize.13=1953514552 diskState.13=7 diskId.13=WDC_WD20EARX-00PASB0_WD-WMAZA8131647 rdevNumber.13=13 rdevStatus.13=DISK_OK rdevName.13=sdl rdevSize.13=1953514552 rdevId.13=WDC_WD20EARX-00PASB0_WD-WMAZA8131647 rdevNumErrors.13=0 rdevLastIO.13=1410097689 rdevSpinupGroup.13=0 diskNumber.14=14 diskName.14= diskSize.14=0 diskState.14=0 diskId.14= rdevNumber.14=14 rdevStatus.14=DISK_NP rdevName.14= rdevSize.14=0 rdevId.14= rdevNumErrors.14=0 rdevLastIO.14=0 rdevSpinupGroup.14=0 diskNumber.15=15 diskName.15= diskSize.15=0 diskState.15=0 diskId.15= rdevNumber.15=15 rdevStatus.15=DISK_NP rdevName.15= rdevSize.15=0 rdevId.15= rdevNumErrors.15=0 rdevLastIO.15=0 rdevSpinupGroup.15=0 diskNumber.16=16 diskName.16= diskSize.16=0 diskState.16=0 diskId.16= rdevNumber.16=16 rdevStatus.16=DISK_NP rdevName.16= rdevSize.16=0 rdevId.16= rdevNumErrors.16=0 rdevLastIO.16=0 rdevSpinupGroup.16=0 diskNumber.17=17 diskName.17= diskSize.17=0 diskState.17=0 diskId.17= rdevNumber.17=17 rdevStatus.17=DISK_NP rdevName.17= rdevSize.17=0 rdevId.17= rdevNumErrors.17=0 rdevLastIO.17=0 rdevSpinupGroup.17=0 diskNumber.18=18 diskName.18= diskSize.18=0 diskState.18=0 diskId.18= rdevNumber.18=18 rdevStatus.18=DISK_NP rdevName.18= rdevSize.18=0 rdevId.18= rdevNumErrors.18=0 rdevLastIO.18=0 rdevSpinupGroup.18=0 diskNumber.19=19 diskName.19= diskSize.19=0 diskState.19=0 diskId.19= rdevNumber.19=19 rdevStatus.19=DISK_NP rdevName.19= rdevSize.19=0 rdevId.19= rdevNumErrors.19=0 rdevLastIO.19=0 rdevSpinupGroup.19=0 diskNumber.20=20 diskName.20= diskSize.20=0 diskState.20=0 diskId.20= rdevNumber.20=20 rdevStatus.20=DISK_NP rdevName.20= rdevSize.20=0 rdevId.20= rdevNumErrors.20=0 rdevLastIO.20=0 rdevSpinupGroup.20=0 diskNumber.21=21 diskName.21= diskSize.21=0 diskState.21=0 diskId.21= rdevNumber.21=21 rdevStatus.21=DISK_NP rdevName.21= rdevSize.21=0 rdevId.21= rdevNumErrors.21=0 rdevLastIO.21=0 rdevSpinupGroup.21=0 diskNumber.22=22 diskName.22= diskSize.22=0 diskState.22=0 diskId.22= rdevNumber.22=22 rdevStatus.22=DISK_NP rdevName.22= rdevSize.22=0 rdevId.22= rdevNumErrors.22=0 rdevLastIO.22=0 rdevSpinupGroup.22=0 diskNumber.23=23 diskName.23= diskSize.23=0 diskState.23=0 diskId.23= rdevNumber.23=23 rdevStatus.23=DISK_NP rdevName.23= rdevSize.23=0 rdevId.23= rdevNumErrors.23=0 rdevLastIO.23=0 rdevSpinupGroup.23=0 root@R2D2:/# no parity running on that one for the moment (need to get salary to buy one.. just bought a house and other costs get priority
September 7, 201411 yr Are you seeing those same error messages in your syslog as the person who reported the issue with unMENU?? (are you running loop-back devices?? with docker images??)
September 7, 201411 yr Safe to use? Is what safe to use? If you simply mean beta 8 then it is certainly as safe to use if you are using base unRAID features. Assuming by base features you do not mean disk replacement expansion. It does not support replacing a smaller disk with a larger disk. Yes, it does. It won't expand the hard drive, tho. This feature, I suspect, was removed temporarily due to lack of proper testing of expansion with the newly offered file systems. Yes there is code added that changed the way expansion was done but for XFS code not added yet, so I thought, "Hey, instead of delaying the release a couple more days, let's just leave this out the for a beta release or two. How many people using a beta will want to replace smaller disk with larger one, I bet I can get away with this and no one will notice." Obviously someone noticed I won't make that mistake again. Nope. Just note it clearly and include the appropriate statement, " We are testing and developing new features and sometimes that means other features have to be disabled. if this is a problem for you, do not use betas!" This is all very confusing. Could someone post a single summary in objective language to the 'faults' forum where people considering problems with the beta might see it? D
September 7, 201411 yr I have been rebuilding a server that I had issues with, and was trying to create the docker.img file, but it was failing to expand when I used /mnt/user/appdata/docker.img. I tried changing it to /mnt/cache/appdata/docker.img and it worked fine. Here is the syslog events: Sep 7 14:39:00 Tower kernel: Btrfs loaded Sep 7 14:39:22 Tower php: /etc/rc.d/rc.docker start Sep 7 14:39:22 Tower php: Maybe expand image file Sep 7 14:39:22 Tower php: Not starting Docker: mount error Sep 7 14:39:22 Tower php: Sep 7 14:41:38 Tower php: /etc/rc.d/rc.docker start Sep 7 14:41:38 Tower php: Creating new image file for Docker: /mnt/user/appdata/docker.img size: 10G Sep 7 14:41:38 Tower php: SMALL VOLUME: forcing mixed metadata/data groups WARNING! - Btrfs v3.14.2 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using Sep 7 14:41:38 Tower php: Not starting Docker: failed to create btrfs file system Sep 7 14:41:38 Tower php: Sep 7 14:42:03 Tower php: /etc/rc.d/rc.docker start Sep 7 14:42:03 Tower php: Maybe expand image file Sep 7 14:42:03 Tower php: Not starting Docker: mount error Sep 7 14:42:03 Tower php: Sep 7 14:42:06 Tower php: /etc/rc.d/rc.docker start Sep 7 14:42:06 Tower php: Maybe expand image file Sep 7 14:42:06 Tower php: Not starting Docker: mount error Sep 7 14:42:06 Tower php: Sep 7 14:43:40 Tower php: /etc/rc.d/rc.docker start Sep 7 14:43:40 Tower php: Creating new image file for Docker: /mnt/cache/appdata/docker.img size: 10G Sep 7 14:43:41 Tower php: WARNING! - Btrfs v3.14.2 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 fs created label (null) on /mnt/cache/appdata/docker.img ^Inodesize 16384 leafsize 16384 sectorsize 4096 size 10.00GiB Btrfs v3.14.2 Sep 7 14:43:41 Tower php: Not starting Docker: mount error Sep 7 14:43:41 Tower php: Sep 7 14:43:58 Tower php: /etc/rc.d/rc.docker start Sep 7 14:43:58 Tower php: Maybe expand image file Sep 7 14:43:58 Tower kernel: BTRFS: device fsid 90be9fb8-2fdd-405d-8624-3700c4c5953f devid 1 transid 4 /dev/loop8 Sep 7 14:43:58 Tower kernel: BTRFS info (device loop8): disk space caching is enabled Sep 7 14:43:58 Tower kernel: BTRFS: flagging fs with big metadata feature Sep 7 14:43:58 Tower kernel: BTRFS: creating UUID tree Sep 7 14:43:58 Tower php: Resize '/var/lib/docker' of 'max' Sep 7 14:43:58 Tower php: starting docker ... Sep 7 14:43:58 Tower kernel: BTRFS: new size for /dev/loop8 is 10737418240 Sep 7 14:43:58 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Sep 7 14:43:58 Tower avahi-daemon[1895]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1. Sep 7 14:43:58 Tower avahi-daemon[1895]: New relevant interface docker0.IPv4 for mDNS. Sep 7 14:43:58 Tower avahi-daemon[1895]: Registering new address record for 172.17.42.1 on docker0.IPv4. Sep 7 14:43:59 Tower ntpd[1284]: Listen normally on 3 docker0 172.17.42.1 UDP 123 Sep 7 14:43:59 Tower ntpd[1284]: peers refreshed Sep 7 14:43:59 Tower ntpd[1284]: new interface(s) found: waking up resolver Sep 7 14:43:59 Tower php: Any idea why /mnt/cache would work, but /mnt/user would not?
September 7, 201411 yr I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. I use IE 11 for all my browsing because it is the most compatible with financial websites I visit. What I have found is happening with the webgui is, when it hangs I go to the Windows Task Manager and see several instances of iexplorer.exe running even after I have closed Internet Explorer. When I terminate iexplore.exe in the Task Manager, I am then able to get back into the webgui. I don't know if other browsers are having the same problem. I sometimes use Safari on my iPad, and it seems to have a lot less issues with the hangs.
September 7, 201411 yr I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. I use IE 11 for all my browsing because it is the most compatible with financial websites I visit. What I have found is happening with the webgui is, when it hangs I go to the Windows Task Manager and see several instances of iexplorer.exe running even after I have closed Internet Explorer. When I terminate iexplore.exe in the Task Manager, I am then able to get back into the webgui. I don't know if other browsers are having the same problem. I sometimes use Safari on my iPad, and it seems to have a lot less issues with the hangs. Even though I use IE 11 for just about everything under the sun, I have started using Google Chrome for managing UnRAID as the GUI behaves better and pop-up windows display correctly (i.e. under IE the template settings for Docker containers in Docker Manager don't tend to fill in correctly). I am not sure why, but IE and UnRAID do not seem to play really nicely together.
September 7, 201411 yr Not that I want to encourage IE shenanigans but it might be time for you to do some cross browser testing (shrug)
September 7, 201411 yr Not that I want to encourage IE shenanigans but it might be time for you to do some cross browser testing (shrug) Given it's prevalence, one might think so. Though I am surprised how popular Chrome is, IE is still the default many use.
September 7, 201411 yr You guys use IE?? It hurts my brain! It's hard to teach an old dog a new trick. What is it that unRAID is doing that is so incompatible with IE? Doesn't seem to me that the webgui is doing anything extra ordinary. Oh well, Microsoft has their own way of doing things.
September 7, 201411 yr Not that I want to encourage IE shenanigans but it might be time for you to do some cross browser testing (shrug) Given it's prevalence, one might think so. Though I am surprised how popular Chrome is, IE is still the default many use. We don't have much choice in some cases. My bank, payroll service, financial services, etc all insist on IE.
September 7, 201411 yr We don't have much choice in some cases. My bank, payroll service, financial services, etc all insist on IE. I don't have any problems with my financial sites using Firefox. I haven't used IE in probably 10 years
September 7, 201411 yr We don't have much choice in some cases. My bank, payroll service, financial services, etc all insist on IE. I don't have any problems with my financial sites using Firefox. I haven't used IE in probably 10 years We're getting off topic, but what I hear is that IE is an issue with the unRAID webgui and the recommendation is to use another browser.
September 7, 201411 yr Author I have been rebuilding a server that I had issues with, and was trying to create the docker.img file, but it was failing to expand when I used /mnt/user/appdata/docker.img. I tried changing it to /mnt/cache/appdata/docker.img and it worked fine. This is a known bug, fixed in next release: http://lime-technology.com/forum/index.php?topic=35020.0 Guys, PLEASE, no longer use Announcement board to post bugs. There's a whole new board for that.
September 7, 201411 yr Author I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. This may or may to apply, but realize this: unRaid users are an impatient lot in general. Some operations will make the webGui appear to hang, when in fact it's working. Pounding on Refresh does not help. I know everyone likes to pound on Refresh and everyone likes to have instant feedback, that's how you use the internet after all right? But the webGui is a user interface that happens to use HTTP/HTML and browsers for display. We are doing our best to make the thing "instantanenous" but this will take some time.
September 7, 201411 yr I have been rebuilding a server that I had issues with, and was trying to create the docker.img file, but it was failing to expand when I used /mnt/user/appdata/docker.img. I tried changing it to /mnt/cache/appdata/docker.img and it worked fine. This is a known bug, fixed in next release: http://lime-technology.com/forum/index.php?topic=35020.0 Guys, PLEASE, no longer use Announcement board to post bugs. There's a whole new board for that. Sorry, ingrained bad habit.
September 7, 201411 yr I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. This may or may to apply, but realize this: unRaid users are an impatient lot in general. Some operations will make the webGui appear to hang, when in fact it's working. Pounding on Refresh does not help. I know everyone likes to pound on Refresh and everyone likes to have instant feedback, that's how you use the internet after all right? But the webGui is a user interface that happens to use HTTP/HTML and browsers for display. We are doing our best to make the thing "instantanenous" but this will take some time. unRAID users impatient? Say it isn't so! Honestly, I don't think you own this problem. If you can help, that's great, but you are dealing with compatibilities/weaknesses in IE.
September 7, 201411 yr I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. This may or may to apply, but realize this: unRaid users are an impatient lot in general. Some operations will make the webGui appear to hang, when in fact it's working. Pounding on Refresh does not help. I know everyone likes to pound on Refresh and everyone likes to have instant feedback, that's how you use the internet after all right? But the webGui is a user interface that happens to use HTTP/HTML and browsers for display. We are doing our best to make the thing "instantanenous" but this will take some time. unRAID users impatient? Say it isn't so! Honestly, I don't think you own this problem. If you can help, that's great, but you are dealing with compatibilities/weaknesses in IE. There are problems that hang the webgui, no matter what browser is being used. Some problems appear to be browser centric whereas others seem to make the webgui hang. Ideally the webgui will remain responsive in the future. When it isn't, users unfamiliar with the console are stuck wondering what's going on.
September 8, 201411 yr Are you seeing those same error messages in your syslog as the person who reported the issue with unMENU?? (are you running loop-back devices?? with docker images??) I am the one who first reported it see also this -> http://lime-technology.com/forum/index.php?topic=27051.msg326217#msg326217 so yeah i am running beta 8 with the loopback loop 8 for the dockerimage
September 8, 201411 yr I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again. I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up. I have some information that may explain and/or help get out of this situation. This may or may not be anything that LT can resolve. This may or may to apply, but realize this: unRaid users are an impatient lot in general. Some operations will make the webGui appear to hang, when in fact it's working. Pounding on Refresh does not help. I know everyone likes to pound on Refresh and everyone likes to have instant feedback, that's how you use the internet after all right? But the webGui is a user interface that happens to use HTTP/HTML and browsers for display. We are doing our best to make the thing "instantanenous" but this will take some time. I learned to telnet in and run a tail against the syslog to see if it's really hung or just busy. The WebGUI tends to take a long time to display after resetting for example. Checks are being done on all the drives.
September 8, 201411 yr Are you seeing those same error messages in your syslog as the person who reported the issue with unMENU?? (are you running loop-back devices?? with docker images??) I just noticed this additional error message positioned near the top banner I highlighted in yellow
September 8, 201411 yr Are you seeing those same error messages in your syslog as the person who reported the issue with unMENU?? (are you running loop-back devices?? with docker images??) I just noticed this additional error message positioned near the top banner I highlighted in yellow Clearly there is some logic change needed in unmenu and myMain to ignore the loopback file system. For now just ignore this message. It is doing no harm.
September 8, 201411 yr Issues with Unmenu should be posted in it's dedicated thread. http://lime-technology.com/forum/index.php?topic=27051.0
September 8, 201411 yr Hello, i added a new disk, I click the Clear option to continue the process, but it stops after a few percent. Why? I am attaching the log. It seems that after 10 percent (not always) it just restarts (no server restart, only option). Syslog.txt
Archived
This topic is now archived and is closed to further replies.