GFRoSTY

I may have found a reason why we are all having issues with the not being able to see the system temps anymore. SYSTEM INFO: unraid: v6.8.3 M/B: ASUSTeK COMPUTER INC. Z10PA-U8 Series Version Rev 1.xx BIOS: American Megatrends Inc. Version 3801. Dated: 05/23/2019 CPU: Intel® Xeon® CPU E5-2620 v4 @ 2.10GHz First I ran pwmconfig: Found the following devices: hwmon0/device is power_meter hwmon1 is nct7904 hwmon2 is coretemp hwmon3 is nct6779 Found the following PWM controls: hwmon1/pwm1 current value: 255 hwmon1/pwm2 current value: 76 hwmon1/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) n hwmon1/pwm3 current value: 76 hwmon1/pwm3 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) n hwmon1/pwm4 current value: 5 hwmon3/pwm1 current value: 10 hwmon3/pwm2 current value: 0 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon1/fan1_input current speed: 1412 RPM hwmon1/fan2_input current speed: 0 ... skipping! hwmon1/fan3_input current speed: 872 RPM hwmon1/fan4_input current speed: 852 RPM hwmon1/fan5_input current speed: 0 ... skipping! hwmon1/fan6_input current speed: 0 ... skipping! hwmon1/fan7_input current speed: 954 RPM hwmon1/fan8_input current speed: 0 ... skipping! hwmon3/fan1_input current speed: 0 ... skipping! hwmon3/fan2_input current speed: 0 ... skipping! So I can see that the system can see what sensors and fans I have. I then ran: 'dmesg | grep NCT6779' # dmesg | grep NCT6779 [ 49.798332] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290 [85626.400888] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290 [85646.600274] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290 [86575.679176] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290 [87679.600329] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290 I next ran the command 'sensors' and it gave me a load of errors against the 'bus name' ~# sensors Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 16: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 18: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 20: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 26: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 28: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 30: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 32: Undeclared bus id referenced sensors_init: Can't parse bus name On opening up the 'sensors.conf' file and looking at the referenced error lines I can see a reference to '0-2d' # sensors chip "nct6779-isa-0290" ignore "temp7" chip "nct6779-isa-0290" ignore "temp8" chip "nct6779-isa-0290" ignore "temp9" chip "nct6779-isa-0290" ignore "temp10" chip "nct6779-isa-0290" ignore "fan1" chip "nct6779-isa-0290" ignore "fan2" chip "nct7904-i2c-0-2d" ignore "fan2" chip "nct7904-i2c-0-2d" ignore "fan5" chip "nct7904-i2c-0-2d" ignore "fan6" chip "nct7904-i2c-0-2d" ignore "fan8" chip "coretemp-isa-0000" label "temp1" "CPU Temp" chip "nct6779-isa-0290" label "temp1" "MB Temp" chip "nct7904-i2c-0-2d" label "fan1" "Array Fan" chip "nct7904-i2c-0-2d" label "fan3" "Array Fan" chip "nct7904-i2c-0-2d" label "fan4" "Array Fan" chip "nct7904-i2c-0-2d" label "fan7" "Array Fan" so I make changes from '0-2d' to '02d', thereby removing the minus char. I go back into settings>system temp and it now shows me all the settings!!!!! I choose all the fans, HOWEVER... when I click on APPLY. The page reloads and the temperature settings have reset and NOTHING shows and the sensors file is reset to show references to '0-2d' - argh! BUT.... If I do all the above and NOT click on APPY', the cpu and motherboard temps NOW show up in UNRAID. and one last update , if you REBOOT then it stops working again and I had to do the above again. SO, clearly further investigation around this whole situation is required from both Limetech and Bonienl

hmm ok, I 'll have a look at the network bits and see if I can get any further in diags and fix.

So, my cache drive failed and at present I don't have a replacement. I started to re add the containers and added Google Music Manager. It setups up ok using the default "net-host", I VNC'd in and logged in with my google email address, password and authorised 'is this me' from my phone but then after that gives me a Couldn't connect to Google Play: I've rechecked my email login details and they are correct. I do have an internet connection so no sure why I am getting this now. Prior to my cache issue all was fine, what else can I check any ideas of a fix?

Changed Status to Solved

Thank you guys for a quick response and your comments. I raised this originally as an 'Urgent' due to the fact that I believed something must have changed the USB drive's status during the upgrade process. I did some more reading of other posts and I decided to run the 'make_bootable' app on the USB via my desktop PC. That worked, and the BIOS booted the USB as it should. It ran through first but then got stuck and locked up the server, so I rebooted and then ran GUI with safemode/no plugins. It booted fine with no apparent issues. One more reboot, and I let it bootup normally and everything started as intended, checked logs and all was good.

Hi Constructor... I've deleted the docker.img file from the cache/system folder and the system recreated it but not sure where it put it as it is no longer in 'system'. I looked at previous apps and selected the ones I wanted and HEY PRESTO back to normal working operation with the DOCKER. Great stuff, so thanks for all the DOCKER related info/tips NOW, that moves me onto why ALL my VM's have disappeared any ideas how to get them back?

docker and libvirt files are in the "system" folder which resides on the cache and nowhere else. settings - docker says location : /mnt/user/system/docker/docker.img

Thanks for the replies so far... I tried to connect to SABNZB which in on 8080 - can't be reached... and I also can't connect to any others that I had set up I was running 6.6.5 and upgraded to 6.6.6 when I noticed no dockers, vm's so thought something must have gone wrong with the upgrade so I restored to my previous 6.6.5 which then showed me no dockers., vms I tried the GUI SAFE mode option and after starting the array no dockers or vms. One thing I did see on restarting was the closed down activities and it said stopping docker containers and then it said that libvirt "was not running". What would cause both dockers and vm's to not show up? All shares, disks, plugins, tools all appear to be OK. The app data info is a still there as is appconfig data (well for 2 apps anyway - (musicbrainz& upststaboard) I have backups of my previous unraid root flash files for 6.6.3 / 6.6.2 version, would there be anything in there to help me fix my issue? Anything else I can look at, provide logs, config, settings to assist in the diagnosis and fix?

I've checked the system share and its only on the cache, there are no other system folders on any other drive. I've also gone through the disks and also other shares and cannot see a system folder or the docker.img libvit.img files... I am perplexed why all my dockers' apps have disappeared (dockers appdata is still in the 'AppData' folder) and vm's also not showing but the disks are in the 'domain' folder.

I updated to 6.6.6 and thought everything was good until I noticed that the Dashboard was showing 'No apps available to show' I then checked each of the header sections and DOCKER, is blank ( shouldn't be) also VMs ( I had 3 running) everything else seems fine (drives, shares,plugins are ok) Thinking there was a problem I restored to 6.6.5 and still the same issue, what has gone wrong here? HELP, please. I thought about going back to 6.6.6 but wanted to post in here first for your comments. I've run the Diagnostics Tool and zip attached. goliath-diagnostics-20190109-1208.zip

Hi, I am trying to change from the default naming in the PATH string and it only shows me (title) and wants to delete the existing filename which has "track name - artist". What do I need to add to enable a filename that gives me "trackname-artistname?"

deleted APPdata for Observium, started... It took about 10 mins, then I could log in. Not sure what happened on the first install which then you mentioned I needed to delete appdata and start up that seemed to fix it as I got to the Observium dashboard. Thanks.

installed , tried login with 'observium' name and Pswd, not being recognised. Waited 10 mins still not working. restarted app waited another 5 mins still won't accept login credentials.

Thanks for the replies. After watching a few youtube videos from Gridrunner aka Spaceinvader One (awesome by the way) I've been having a play with Krusader, Duplicity and rclone. So I just need to do some further checking against my use case requirements what I should setup and use.

Hi all, the answer to my question might be buried deep in the forum so if it is please give a link. I want to be able to copy data from my unRAID shares to another NAS that is running on my network. I see that rclone works to cloud services so would that also work going from unRAID -> another NAS on the same network? What options do I have?

Yes please, would make things a lot easier allocating resources

32gb in mine (4 x8gb sticks DDR4) can upgrade MB to 512 but not for a looooooong time

That's true, and what with the WannaCry (Ransomware) issues globally and SMB amongst other things best to stay patched up all the time on all systems Thanks for your comments and assistance today, back to normal operation

Ok... managed to get the server booted with 6.3.5 with my previous config data copied over and updated the reg key with the new guid of the USB drive and registration. Couple of strange things though... The server booted ok , parity, drives, shares however viewing the shares via the browser and its contents are ok I can see the folders, files and open files no issue. But, when trying to connect to the server from windows and login it is not recognising my credentials. I even created a test user and test share adding test user to the share and still cannot log into the server/share with any account. Has something gone screwy with the smb shares somehow... WELL... no, I rebooted my win 10 pc and when logged into windows tried the share, it prompts me for a password and after about 10secs the folder appears and all files accessible. So, I wanted to add this so people are aware that sometimes a windows reboot can reset things. ? I have made multiple backups both cloud and On-perm of my USB drive so should I get another failure I can restore easier. 2nd strange thing was that even after copying all my config data to the new USB the server name and identification went back to the defaults namely being named 'Tower'. Not sure why that is... I just entered the same name and details I used previously and all was fine. Thanks

Hello Frank1940, thanks for the quick reply. I do have the reg key as I made a concerted effort to save that by my mailing that to myself, pitty I didn't do that with config info... learning note to self!!! Funny thing is I have been transferring data to the cloud, just not got to the folder that my unRaid saved files are in.. yes muppet award ? I know what my drive arrays are as I labelled the drives in the server so know what's parity and drives1-6 plus ssd cache drive. So, going to grab a fresh USB and see what happens...

Hi everyone, I really need some help here. 6.3.4 was ruining fine, logged into the browser GUI today and saw a 6.3.5 version available, so clicked on update and after it did its patching as I have done several times before I rebooted... and now my issue which I don't believe is down to the upgrade but... I left it a few minutes and then refreshed the webpage to unRaid and still a blank screen not connecting, pinged the IP of the server and no response.. hmm I thought. I then plugged in a VGA Cable and connected it a monitor... the bios was sat trying to enable network boot at which point I thought that's not right it should have booted the USB drive. Rebooted again and when into the bios, all drives show including the boot drive a Kingston Datatraveler 3.0 so forced a boot of the USB drive when the screen went blank for a couple of seconds and then the network boot kicked I bypassing the USB boot. That's not good I thought... So I took the USB drive out of the server and connected it to my win 10 desktop when it presented me with a "drive unrecognised do you want to format it" error, at that point I thought crap its corrupted. unplugged and re plugged in each time saying the same error, looks like it has failed. I am now trying to create an image of the usb drive using R-Studio and it is giving me so lots of read disk errors and so going to take another 6hrs o I can see what data is on here. I searched for a backup of the USB disk and I know I have one on the array... but so far haven't found another.. ? How can I boot my server and mount the array, I don't want to just go ahead and try a default install on a different USB stick as not sure that would affect the array negativity. Please help, what can I do?

Hi, Ive noticed inconsistent transfer speeds as of late and I am not entirely sure why that is. Using 6.2.4 Looking at the Network settings within unRAID I see that eth0 has dropped to 100MB/s from 1000Mb/s and don't know why that is. My whole network is 1gig and no 100Mb devices on it. If I restart the UnRAID box it shows me 1000Mb/s for a while and then goes back to show me 100Mb/s I don't recall seeing this in earlier releases... What can I check that might be the cause of this drop? Thanks.

2 suggestions I can add are: 1. put your unraid box and any clients in the same workgroup in your network. 2. Make the unraid server the 'current local master browser' - you may find that another device on your network is the local master and this will cause issues with smb shares

well, I tried to recreate the issue I had to no avail. my current setup that seems to be working now is my win10 pc is in the same workgroup as the smb settings in unraid. Also and I think this was the reason, my unraid server is the current local master browser whereas before it wasnt, the win 10 pc was.