July 29, 20187 yr hi, i have a weird situation with my unraid server. when i go to the gui it seems to have reverted to default or something. the color sceme has changed and for example my docker menu is missing (in the settings docker is not enabled) when i had it running for a year or so. also the containers i had running are still running as you can see: root@Tower:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3542990118ee linuxserver/mariadb "/init" 4 weeks ago Up 4 weeks 0.0.0.0:3306->3306/tcp mariadb 6b3a344b6c78 linuxserver/headphones "/init" 4 weeks ago Up 4 weeks 0.0.0.0:8182->8181/tcp headphones f7127ebfac5c linuxserver/ombi "/init" 4 weeks ago Up 4 weeks 0.0.0.0:3579->3579/tcp ombi b90f42fdbf9f linuxserver/tautulli "/init" 4 weeks ago Up 4 weeks 0.0.0.0:8181->8181/tcp tautulli 2bef8f174dc1 linuxserver/radarr "/init" 4 weeks ago Up 4 weeks 0.0.0.0:7878->7878/tcp radarr 152bdf8bd913 linuxserver/plex "/init" 4 weeks ago Up 4 weeks plex 9f6d4a560691 owncloud "docker-entrypoint.s…" 2 months ago Up 5 weeks 0.0.0.0:8000->80/tcp owncloud in the bottom of the gui it is saying array started starting services...but everything seems to be up and running. this might be going on some time now but i never noticed as everything seems to be running normally, but i wanted to update some containers so i noticed it now. i have a feeling that at some point the connection of the usb stick has been lost or something. i don't see it if i run fdisk (it should be sda): root@Tower:~# fdisk -l Disk /dev/loop2: 50 GiB, 53687091200 bytes, 104857600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 46D71786-C0E0-403B-8389-D47391EBA9B1 Device Start End Sectors Size Type /dev/sdc1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 2281615A-26EA-415F-8293-CFB76199FB3F Device Start End Sectors Size Type /dev/sdd1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 64 488397167 488397104 232.9G 83 Linux Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sde1 1 4294967295 4294967295 2T 0 Empty Partition 1 does not start on physical sector boundary. Disk /dev/sdf: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: BE5FE0D6-652A-4304-B873-1ADFE9659971 Device Start End Sectors Size Type /dev/sdf1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdg: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdg1 1 4294967295 4294967295 2T 0 Empty Partition 1 does not start on physical sector boundary. Disk /dev/sdh: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdh1 64 3907029167 3907029104 1.8T 0 Empty Disk /dev/sdi: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdi1 64 3907029167 3907029104 1.8T 83 Linux Disk /dev/sdj: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 7A605483-0F9B-44BB-B83A-2A27DEEFA3DF Device Start End Sectors Size Type /dev/sdj1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdk: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: D5A21EA0-ED34-4DAB-B983-A257BDC57E4C Device Start End Sectors Size Type /dev/sdk1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdl: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 943B81BA-64F0-4CCD-9765-8E36228F0230 Device Start End Sectors Size Type /dev/sdl1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdm: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 4E0230B9-950C-4796-AB06-586F6E17CA87 Device Start End Sectors Size Type /dev/sdm1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/md3: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md4: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md5: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md6: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md7: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md8: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md9: 1.8 TiB, 2000398901248 bytes, 3907029104 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdn: 14.3 GiB, 15376000000 bytes, 30031250 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x2ddc8508 Device Boot Start End Sectors Size Id Type /dev/sdn1 * 2048 30029823 30027776 14.3G c W95 FAT32 (LBA) but the system seems to think it is still mounted as /boot: root@Tower:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 7.7G 735M 7.0G 10% / tmpfs 32M 488K 32M 2% /run devtmpfs 7.7G 0 7.7G 0% /dev tmpfs 7.7G 0 7.7G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 128M 0 100% /var/log /dev/sda1 15G 629M 14G 5% /boot /dev/loop0 7.5M 7.5M 0 100% /lib/modules /dev/loop1 4.5M 4.5M 0 100% /lib/firmware /dev/md3 3.7T 3.2T 462G 88% /mnt/disk3 /dev/md4 3.7T 2.4T 1.3T 66% /mnt/disk4 /dev/md5 3.7T 2.3T 1.4T 64% /mnt/disk5 /dev/md6 3.7T 3.2T 466G 88% /mnt/disk6 /dev/md7 3.7T 3.2T 484G 88% /mnt/disk7 /dev/md8 3.7T 1.9T 1.9T 51% /mnt/disk8 /dev/md9 1.9T 933G 930G 51% /mnt/disk9 /dev/sdb1 233G 86G 147G 37% /mnt/cache shfs 24T 17T 6.8T 72% /mnt/user0 shfs 24T 18T 6.9T 72% /mnt/user /dev/loop2 50G 3.6G 45G 8% /var/lib/docker /dev/loop3 1.0G 18M 904M 2% /etc/libvirt shm 64M 0 64M 0% /var/lib/docker/containers/9f6d4a560691647679ea028e4fcdc94de4749d0477046780f14093bf17a00dd4/shm shm 64M 8.0K 64M 1% /var/lib/docker/containers/152bdf8bd913b88ddf7b602ee1aee325b0e28df6107854e622edc59497334434/shm shm 64M 4.0K 64M 1% /var/lib/docker/containers/2bef8f174dc1d466984f6317c068b41554da456eeb06f8bc99b50f56d8db54bf/shm shm 64M 0 64M 0% /var/lib/docker/containers/b90f42fdbf9f2d0c3a5d285c98c41b0087a3f70f1894fbfdfa61333537bfa796/shm shm 64M 0 64M 0% /var/lib/docker/containers/f7127ebfac5c1e157758e97f898154556f12eace0b70c80708d1f86141a22804/shm shm 64M 0 64M 0% /var/lib/docker/containers/6b3a344b6c78225d60d4dfe27071317d7e81b33c28328ee52276d0c6d5be5971/shm shm 64M 0 64M 0% /var/lib/docker/containers/3542990118ee8e5b491e4c816a903bd20c76e673dc5eac7a044c266c364e8777/shm the gui also reports the usb stick, but when i browse it it is empty. i took the usb stick and put it in another pc and it seems ok, all the files seem to be there as well. i think there is a chance that if i reboot the server it will find the stick again and boot from it normally but before i try that i wanted to check here if anybody has any ideas. thanks in advance, i hope i included enough info. if not let me know what you need. tower-diagnostics-20180729-1748.zip
July 29, 20187 yr Author yes i have it is still not showing up it is showing when i check the usb devices: root@Tower:~# lsusb Bus 002 Device 003: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub it's the scandisk Edited July 29, 20187 yr by slasse
August 3, 20187 yr Community Expert You will have to shutdown and maybe it would be a good idea to put the flash in your PC and let it checkdisk. Do you have a backup of the flash? For future reference, you can always download a zipped backup of your flash from Main - Boot Device - Flash - Flash backup But of course that won't work if it isn't mounted now. Can you see it in Unassigned Devices?
August 4, 20187 yr Author i do have a backup from some time ago, but if i put the usb in the pc i can access it without problems. so i hope that wil be ok. i do see it in unassigned devices, but i am unable to mount it from there. also a bit weird is that it is listed as the boot device (sda) and under the unassigned devices as sdn i guess i will risk restarting, but first i will take another copy of the content on the usb stick
August 4, 20187 yr When your USB drive is assigned as the boot device (usually sda, but it may differ) then it is not available as an unassigned device. Seeing your USB as unassigned implies there is something wrong.
August 4, 20187 yr Author yeah i think so to i took the usb to my pc, when i tried to copy the files off the usb i get messages that a certain file is not there anymore. also an new explorer window opens as if i inserted the usb stick and sometimes even saying the device is unaccessible when i click try again a couple of times eventually everything gets copied. obviously this doesn't give me much confidence in the usb stick.. at the moment i am running a tool called check flash to see if it can detect any issue's. the stick is just under a year old, i just checked and i replaced it last year august 26. so by the default policy i would have to wait until august 26th to be able to replace it. but i guess if i send a mail to support i could do this sooner
Archived
This topic is now archived and is closed to further replies.