November 6, 20169 yr Not sure if it's a bug but thought I'd report it. I just updated from 6.2.2 to 6.2.3. I only have one user created for user shares and that's gone. Not a biggie, I only have that one user to set up again. After creating the user, checking the user shares show the user attached with the right permissions so I didn't have to set up permissions again.
November 6, 20169 yr This is probably an issue with your USB flash device. Suggest you plug into a PC, make a backup, and run file system check.
November 6, 20169 yr Author I shut it down, plugged the USB (Sandisk Ultra Fit 16GB) into my Mac, run Disk Utility. It fixed an error, I turned on the NAS with the flash drive. And I lost all my array device assignment. Consequently I'm not seeing any dockers. My user is also gone. From the log: Nov 6 15:12:15 Tower emhttp: shcmd (80): udevadm settle Nov 6 15:12:15 Tower emhttp: SanDisk_Ultra_Fit_4C531146380502112423-0:0 (sda) 15015592 Nov 6 15:12:15 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E7JTAZPZ (sdb) 3907018532 Nov 6 15:12:15 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E5SA596V (sdc) 3907018532 Nov 6 15:12:15 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E7JTADCR (sdd) 3907018532 Nov 6 15:12:15 Tower emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E7JTA9KT (sde) 3907018532 Nov 6 15:12:15 Tower emhttp: Samsung_SSD_850_EVO_500GB_S2RANX0H416137Y (sdf) 488386552 Nov 6 15:12:15 Tower kernel: mdcmd (1): import 0 Nov 6 15:12:15 Tower kernel: mdcmd (2): import 1 Nov 6 15:12:15 Tower kernel: mdcmd (3): import 2 Nov 6 15:12:15 Tower kernel: mdcmd (4): import 3 Nov 6 15:12:15 Tower kernel: mdcmd (5): import 4 Nov 6 15:12:15 Tower kernel: mdcmd (6): import 5 Nov 6 15:12:15 Tower kernel: mdcmd (7): import 6 Nov 6 15:12:15 Tower kernel: mdcmd (: import 7 Nov 6 15:12:15 Tower kernel: mdcmd (9): import 8 Nov 6 15:12:15 Tower kernel: mdcmd (10): import 9 Nov 6 15:12:15 Tower kernel: mdcmd (11): import 10 Nov 6 15:12:15 Tower kernel: mdcmd (12): import 11 Nov 6 15:12:15 Tower kernel: mdcmd (13): import 12 Nov 6 15:12:15 Tower kernel: mdcmd (14): import 13 Nov 6 15:12:15 Tower kernel: mdcmd (15): import 14 Nov 6 15:12:15 Tower kernel: mdcmd (16): import 15 Nov 6 15:12:15 Tower kernel: mdcmd (17): import 16 Nov 6 15:12:15 Tower kernel: mdcmd (18): import 17 Nov 6 15:12:15 Tower kernel: mdcmd (19): import 18 Nov 6 15:12:15 Tower kernel: mdcmd (20): import 19 Nov 6 15:12:15 Tower kernel: mdcmd (21): import 20 Nov 6 15:12:15 Tower kernel: mdcmd (22): import 21 Nov 6 15:12:15 Tower kernel: mdcmd (23): import 22 Nov 6 15:12:15 Tower kernel: mdcmd (24): import 23 Nov 6 15:12:15 Tower kernel: mdcmd (25): import 24 Nov 6 15:12:15 Tower kernel: mdcmd (26): import 25 Nov 6 15:12:15 Tower kernel: mdcmd (27): import 26 Nov 6 15:12:15 Tower kernel: mdcmd (28): import 27 Nov 6 15:12:15 Tower kernel: mdcmd (29): import 28 Nov 6 15:12:15 Tower kernel: mdcmd (30): import 29 Nov 6 15:12:15 Tower emhttp: import 30 cache device: no device Nov 6 15:12:15 Tower emhttp: import flash device: sda I see files in the USB drive but nothing that looks like a log file from booting up. What can I do next to troubleshoot and fix this?
November 6, 20169 yr On your flash drive, what do you see in your /config folder? There should be stuff in cfg files that you can look into to see the info.
November 6, 20169 yr Author This is what I have: Inside docker.cfg: DOCKER_ENABLED="yes" DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker.img" DOCKER_IMAGE_SIZE="20" DOCKER_APP_CONFIG_PATH="/mnt/user/appdata/" DOCKER_APP_UNRAID_PATH="" Inside domain.cfg: SERVICE="enable" IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img" IMAGE_SIZE="1" DEBUG="no" DOMAINDIR="/mnt/user/domains/" MEDIADIR="/mnt/user/isos/" VIRTIOISO="" BRNAME="br0" VMSTORAGEMODE="auto" Inside the /shares folder I see .cfg files for my shares.
November 6, 20169 yr Author Just tried to SSH into the NAS and got this: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is SHA256:OgG6hor5AfJpucQfUKUJokygD03TukuMQ1SSSllUctw. Please contact your system administrator. Add correct host key in /Users/Vurtopia/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /Users/Vurtopia/.ssh/known_hosts:4 ECDSA host key for 192.168.1.252 has changed and you have requested strict checking. Host key verification failed. I had the nginx-letsencrypt docker running before, could that be why this is happening?
November 7, 20169 yr Likely, some of the ssh host key files in your /boot/config/ssh folder got corrupted/erased and thus unraid regenerated those files, hence the error about the changed host key. Just clean up the file (line 4, and maintain the line endings) /Users/Vurtopia/.ssh/known_hosts on you Mac.
November 7, 20169 yr Author Just clean up the file (line 4, and maintain the line endings) /Users/Vurtopia/.ssh/known_hosts on you Mac. This is what I'm seeing with lines 4 and 5: 192.168.1.252 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= tower.local ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= How do I clean it up? Make it like: 192.168.1.252 ecdsa-sha2-nistp256 = tower.local ecdsa-sha2-nistp256 = ? Assuming = is the line ending you're referring to?
November 7, 20169 yr Just delete the whole lines. 192.168.1.252 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= tower.local ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= Sorry, there are no issues with line endings as you are using a Mac. (that's a corss Windows/Linux issue)
November 7, 20169 yr Author Just delete the whole lines. 192.168.1.252 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= tower.local ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNaagRAOo0jvQBgraRps6D1BVjrsdhbqA3yh/FmtMAShVqKdoibxgq7sawaSGJYdoyvQ8kFc8qSDO7pbdC6c1bA= Sorry, there are no issues with line endings as you are using a Mac. (that's a corss Windows/Linux issue) Thank you, that worked! Now to figure out the rest which is more perplexing.
November 7, 20169 yr Author I'm getting these random errors at different times: I would reboot and cannot access the web gui at tower.local. I see input/output error when I connect the NAS to a monitor. The OS appears are unregistered. There was an Disabling IRQ #6 or 16 (Don't remember right now). What am I suppose to do? Would a flash drive problem be causing all this? How have I had it running for 2 weeks until this update/reboot??
November 7, 20169 yr The fixed error on your USB flash drive might have caused a bunch of config files to become lost, which would explain the ssh and drive assignment issues. You might need to set it up from scratch and copy in the missing key file from your email.
November 7, 20169 yr Author I'm seeing the .cfg files for my shares in the /shares folder on the USB.
November 7, 20169 yr Author This might be too late because I've rebooted several times, but I'm attaching a zip of the logs. tower-diagnostics-20161107-0459.zip
November 8, 20169 yr Author This is extremely frustrating. I thought maybe it's a flash drive problem and would try a different drive except of course the key is locked to the first flash drive. So how am I suppose to troubleshoot? I don't understand how people are using unRAID for business if troubleshooting a flash drive or getting support is so difficult.
November 8, 20169 yr Actually, your current diagnostics show that its in Trial mode. Hence my initial reply: The fixed error on your USB flash drive might have caused a bunch of config files to become lost, which would explain the ssh and drive assignment issues. You might need to set it up from scratch and copy in the missing key file from your email. Since the cfg file for the shares are present, your shares should be available right away, once the OS is registered (either as a Trial or with your original key) and array is started. So locate your original key (Plus.key or Pro.key file) and copy it into the config directory of the flash drive.
November 8, 20169 yr Author It's in trial mode because I've had it for 2 weeks. When I first had unRAID running I had issues installing the trial key, error-1. I remember going into my BIOS and changing the boot option for the SANDISK to "Forced FDD" and disabled "UEFI". I also manually copied the trial key onto the flash drive. That seemed to work. I set up my shares, installed the dockers had unRAID running for 2 weeks until I updated to 6.2.3. The reboot after the update is when all these problems began. But the situation is the same when the system appears registered and unregistered: My shares are gone, user is gone, dockers are gone. But my Community Application plug-in exists. So something is persisting from before all this happened.
November 8, 20169 yr Community Expert Backup your config folder, do a fresh install, and restore your config folder.
November 8, 20169 yr Author Fresh install meaning: Download the 6.2.4 files, go through the prep for the USB flash drive, and then do I 1) boot up with that first, shut down, copy the old config to the flash drive and boot up again, or 2) copy the old config to the newly prepared USB flash drive and boot up with it?
November 8, 20169 yr Community Expert 2) copy the old config to the newly prepared USB flash drive and boot up with it? Your diagnostic looks like it is missing some config files, so I am trying to get them back.
November 8, 20169 yr Author I did what you said. Can't log into the web gui, tower.local does not resolve. Can't access with the IP too. From the Mac terminal, pinging tower.local returns nothing. But pinging the IP address works. I can also SSH using the IP, logging in as "root@Tower". I ran the "diagnostics" command and got this: root@Tower:~# diagnostics Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/tower-diagnostics-20161107-2232.zip' created. No ZIP file on the flash drive. Does this mean the flash drive is no good? Or I can try the remaining USB ports, I've been using the same USB port since the first install.
November 8, 20169 yr looks like your flash drive is either full or still has some issues. Try using a different flash drive. If tower.local does not resolve. access the web ui using IP address.
Archived
This topic is now archived and is closed to further replies.