July 25, 20196 yr So today I come home and notice my home automation (running in a VM) was not working. I tried to restart the VM but nothing happened. Did a force shutdown, but when I try to start it again I just get an error, ofcourse did not write it down. So I figure something has crashed on Unraid. Although no error messages. So what does one usually do at this point, reboot server... (obviously coming here reading now, this was a big mistake). Because when I boot up again I notice that one disk is missing, that's ok because it was an old disk listed as a spare and not in use. But my VM did not autostart, so I check the VM tab and it says "No Virtual Machines installed" then I check my docker tab and it says "No Docker containers installed". Then I take a look back at my array and everything seems to be fine. I do however wonder if an old setup is in place and maybe the wrong disk are in my array. I'm not 100% sure about this. (I had 3 spares connected and powered down) This is the point where I come here, desperate for help before I make more mistakes.
July 25, 20196 yr Author fdisk -l seems strange to me Disk /dev/loop0: 8.5 MiB, 8949760 bytes, 17480 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/loop1: 5.9 MiB, 6135808 bytes, 11984 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/loop2: 20 GiB, 21474836480 bytes, 41943040 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/sda: 3.8 GiB, 4009754624 bytes, 7831552 sectors Disk model: Voyager Mini 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/sda1 * 2048 7831551 7829504 3.8G c W95 FAT32 (LBA) Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: WDC WD20EARX-00P 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/sdb1 64 3907029167 3907029104 1.8T 83 Linux Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: WDC WD30EFRX-68E 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: 916C9430-DEF3-4B7F-B98E-E4E696965BB9 Device Start End Sectors Size Type /dev/sdd1 64 5860533134 5860533071 2.7T Linux filesystem Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: WDC WD30EFRX-68E 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: 94A7DD12-CDD1-4371-BF19-E62F6C401AFA Device Start End Sectors Size Type /dev/sdc1 64 5860533134 5860533071 2.7T Linux filesystem Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: WDC WD30EFRX-68E 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: 435098AE-8757-4530-9855-06E9E2390957 Device Start End Sectors Size Type /dev/sde1 40 1060289 1060250 517.7M Microsoft basic data /dev/sde2 1060296 2120579 1060284 517.7M Microsoft basic data /dev/sde3 2120584 5842744109 5840623526 2.7T Microsoft basic data /dev/sde4 5842744112 5843804399 1060288 517.7M Microsoft basic data /dev/sde5 5843804408 5860511999 16707592 8G Microsoft basic data Disk /dev/sdf: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000VN000-1H41 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: 07D55308-4243-45D8-9B9A-720689AE49FF Device Start End Sectors Size Type /dev/sdf1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdg: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: SAMSUNG HD103SJ 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/sdg1 64 1953525167 1953525104 931.5G 83 Linux Disk /dev/sdh: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10EADS-00M 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 1953525167 1953525104 931.5G 83 Linux Disk /dev/md1: 2.7 TiB, 3000592928768 bytes, 5860533064 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/md2: 931.5 GiB, 1000204853248 bytes, 1953525104 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/md3: 931.5 GiB, 1000204853248 bytes, 1953525104 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
July 25, 20196 yr Author My logic here tells me the missing disk messed up the sda,sdb,sdc.... order and now the wrong disks are in the array. Problem is I'm not 100% sure what disks I had in my array.
July 25, 20196 yr Author ok, so I notice my cache disk is also missing. I guess it's time to power off the damn thing.
July 25, 20196 yr Author ok, I'm up and running again. Got my Cache disk back and everything is working. Guess it's the heatwave taking it's toll. But I notice appdata, system and domains have a warning that some or all files are unprotected. I assume this is files that are on the cache disk and are not backed up to the array ? Why is this ? It's a bit critical if cache disk fails and you loose your settings.
July 25, 20196 yr 54 minutes ago, yrune said: when I boot up again I notice that one disk is missing, that's ok because it was an old disk listed as a spare and not in use. That's not OK. Because of how parity protection works, even empty disks must be 100% readable without errors to keep parity protection. It's not a good idea to leave unused unneeded disks in the array, because if one of them fails, and you have another disk fail with data that you care about, you will lose data. 45 minutes ago, yrune said: My logic here tells me the missing disk messed up the sda,sdb,sdc.... order and now the wrong disks are in the array. Problem is I'm not 100% sure what disks I had in my array. Unraid tracks disks by serial number, the sdX designations are not tracked because they can change. It's a good idea to keep a current screenshot of your Main GUI page as well as a diagnostics zip file. 16 minutes ago, yrune said: But I notice appdata, system and domains have a warning that some or all files are unprotected. I assume this is files that are on the cache disk and are not backed up to the array ? Why is this ? It's a bit critical if cache disk fails and you loose your settings. If you don't have a BTRFS cache pool with 2 devices set for RAID1, then the cache files will be unprotected from device failure. This is not a big deal if you use the appdata backup plugin and keep your VM's backed up.
July 25, 20196 yr Author @jonathanm Thank you for your input. Are you sure disk that are not part of the array are used for the parity ? That seems strange. Also I have setup up appdata backup plugin now, thanks for suggestion. Do you also have suggestion for something to automate VM backup ? Edited July 25, 20196 yr by yrune
July 25, 20196 yr 25 minutes ago, yrune said: Are you sure disk that are not part of the array are used for the parity ? That seems strange. If it's not part of the array, it's not included in parity. I must have missed where you said it wasn't part of the array. I just saw where you said... 1 hour ago, yrune said: it was an old disk listed as a spare and not in use. Since unraid doesn't have "spare" as an official label in the list of disks, I assumed that was your designation of what its purpose was and it was still part of the array.
July 25, 20196 yr 30 minutes ago, yrune said: Do you also have suggestion for something to automate VM backup ? There are scripts on the forum that deal with backup of the vdisk files, personally I just treat my VM's just like any physical machine on the network and use whatever backup software is applicable to that OS and run it inside the VM. For some of them I'm using duplicati pointing to a webdav target on my nextcloud instance.
July 25, 20196 yr Author @jonathanm yeah, bad wording on my part. I guess the term is "Unassigned Devices" what I called spare, and I have 3 of those. But again, do you have suggestion for VM backups, I checked and notice they only reside on the cache disk. I did find an old script here on the forum, but it's over 3 years old and run from shell, not as a plugin.
July 25, 20196 yr Author 1 minute ago, jonathanm said: There are scripts on the forum that deal with backup of the vdisk files, personally I just treat my VM's just like any physical machine on the network and use whatever backup software is applicable to that OS and run it inside the VM. For some of them I'm using duplicati pointing to a webdav target on my nextcloud instance. Can I use duplicati on a running VM to copy from cache to array ?
July 25, 20196 yr 1 minute ago, yrune said: Can I use duplicati on a running VM to copy from cache to array ? I suppose you could, in my case I wanted the backup to be at another physical location, and I have a server set up with nextcloud specifically for that purpose. There are a million different ways to accomplish backups, and a VM is just another computer in that regard. Some people have scripted the backup of the vdisk files, but unless you shut down the VM during the backup, that method is either complicated or has issues. There are plenty of backup programs that work fine with the computer or VM still running, I just happen to use duplicati.
July 25, 20196 yr Also, to be clear, I am NOT running the duplicati docker on unraid. I could do that as well I suppose, but that wouldn't allow me to back up the VM's conveniently. I'm running duplicati as an application inside the VM or computer I wish to back up.
July 25, 20196 yr Author @jonathanm Thanks for your input, I already have duplicati setup as a docker running on unraid. For me the most practical is to just backup the whole VM image because on the complex nature of the VM. I will try to run it and see if it works while the VM is running.
Archived
This topic is now archived and is closed to further replies.