neztach

if I remove them both, array greys out "start array", unless I commit to them being out ....makes me nervous. Would it be better to wait for my replacement cache drive to arrive? or if I do unassign them, can I then put them back in case something goes wrong?

says can't because disk is mounted, but can't get to the rest of the pool if its unmounted

it appeared to have gotten further, and I believe I now have both cache drives in SATA slots, diagnostics included to confirm. Nothing I can do to possibly limp it along to get a copy of the contents? Some of it? all of it? like I said, all I really want is my VMs ...specifically one of them. after that, I don't mind decomissioning the bad SSD and formatting the remaining one as cache. I already have a new 2TB en route. eden-diagnostics-20211118-0919.zip

I think the device dropping issue is probably symptomatic of the drive dying, in which case, what could I really do about it? Having said that, I'll shuffle the drives around again, and send another diagnostics. In the mean-time, If-after I shuffle the cache drives to both be on SATA the device still drops, is there something I can do after that to attempt to copy data off?

To reiterate, I would love for there to be some kind of method to just change the pool back to using a single drive (the 1 of 2 drives in the cache pool still good). Of I would be willing to buy a new 2TB SSD to replace both drives in the pool. At this point, I would just like some way (ANY. way.) - that would allow me to at least copy off whatever files are essential - especially my VMs. Is there anything I can do here?

well based on your original response, I rearranged my cache drives to what I thought was the LSI. Can you confirm? and I feel like I'm coming across as dense, but which are my intel ports? eden-diagnostics-20211117-1340.zip

you're absolutely right, and I'm perfectly willing to try. I'm just wondering which log you got that from, so I can look at the previous diagnotics and see if either cache drive was previously in an LSI to narrow down what ports I could try, then self-verify so I can follow your advice and get both of them on an LSI controller.

I guess I don't understand how one SSD appears to be connected differently than another SSD. It's a single backplane, and both are connected to the same backplane. Perhaps in my previous diagnostic, one of the drives was hooked up to an LSI controller then as well? If I knew which was was on the LSI controller both then and now I can perhaps shift them around so they are both in a slot previously recognized as LSI. If-not, which part of the diagnostics would I look at to see LSI vs SASLP?

also, I have a HUGE PlexMediaServer folder on cache that I wouldn't be upset about if I trashed all together. Would it help - or make it worse - or change nothing?

I keep rebooting and scrubbing ....sometimes it gets father, sometimes not. Shall I continue, or is there a better approach?

I have a backplane, so I can't really plug directly into the board, but I switched the slots for both cache drives, and the corrective btrfs scrub started fine, then aborted. eden-diagnostics-20211117-0845.zip

wow I'm such a rookie! Apologies, see attached. eden-diagnostics-20211116-1542.zip

https://drive.google.com/drive/folders/1P4ck5oJ1ko4VGZyHPu7m6qGHRF6IMsc7?usp=sharing hopefully that link works.

So I have a cache pool /dev/sdj and /dev/sdk and /sdj is throwing errors, so probably going bad. For a minute, restart I was able to get it to be recognized and come online, and I stupidly missed my window to copy my windows VM from within. At this point, if I spin up the array normally, the cache pool will say "no file system" seemingly no matter what. Whatever section of /sdj1 that's bad is right in the section where mover needs to move, so I can't move anything. I also can't run dockers, as they were built dependent on cache, so no krusader. I found a link here which allows me to make the cache pool read only, which lets me look at things via console. btrfs rescue zero-log /dev/sdj1 I've attempted multiple variations of rsync to copy the vdisk.img to a location on the array, all of which fail. The latest being rsync -avh --progress --sparse /mnt/user/domains/Windows\ 10/vdisk1.img /mnt/user/Archives/VMBackup/Win10/ which results in the following (bear in mind only 200G is allocated to that VM): 214.75G 100% 63.13MB/s 0:54:04 (xfr#1, to-chk=0/1) rsync: [sender] read errors mapping "/mnt/user/domains/Windows 10/vdisk1.img": Input/output error (5) WARNING: vdisk.img failed verification -- update discarded (will try again). 214.75G 100% 51.68MB/s 1:06:02 (xfr#2, to-chk=0/1) rsync: [sender] read errors mapping "/mnt/user/domains/Windows 10/vdisk1.img": Input/output error (5) ERROR: vdisk1.img failed verification -- update discarded. I also tried cp -av --sparse=always <source> <destination> '/mnt/user/domain/Windows 10/vdisk1.img' -> '/mnt/user/Archives/VMBackup/Win10/vdisk1.img' cp: error reading '/mnt/user/domain/Windows 10/vdisk1.img': Input/output error I'm at a loss. Any advice? Honestly, if I could remove the pool, and put all of cache on /dev/sdk1 then I'm sure all would be well.

bump?

I was havig trouble with my Win7 VM not trimming and after a post here this lovely community guided me in the right direction and I ended up spinning up a Windows 10 VM so I could attempt to avoid the trimming issue in the future. I followed the post that was linked in that thread, and after some troubleshooting, ended up having to use SeaBIOS to create my VM. I gave it meager hardware stats as it was part experimenting and part if-this-works-this-is-what-i'll-use. Now that it's up and running, I'd like to give it more cores and more RAM, but whenever I shut down the VM and go edit the settings, no matter what I change, it says I have more than one SCSI channel indexed as 0. Can anyone give me some directionon how I can alter this VM and give it more processors and RAM? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='12'> <name>Windows 10</name> <uuid>68751b5d-6ad9-1ca6-03f1-25f77271d3b3</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/Microsoft Windows 10 Pro x64BiT.iso'/> <backingStore/> <target dev='hda' bus='scsi'/> <readonly/> <boot order='2'/> <alias name='scsi0-0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.160-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:97:25:32'/> <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-12-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

well that sure enough worked! thank you to everyone for the help! Will this be a reoccurring problem though? It took most of the day to copy off the img file then copy it back due to it being ~500G. Which leads me to an off-topic question, if I decided to change my cache from RAID1 to RAID0, will I need to empty off the cache drive first?

crap. So did I mess things up with my copy command? If-not, I should adjust steps 2 and 3 to be /mnt/user/vDisks rather than /mnt/cache? Do my steps and syntax look correct (other than /mnt/cache)?

ok I made a share called vmbaktemp, and since this copy is going to take a while, I just want to make sure I have my order of operations down so I'm not leaving anything out. cp /mnt/cache/vDisks/win7/vdisk1.img /mnt/user/vmbaktemp/vdisk1.img rm /mnt/cache/vDisks/win7/vdisk1.img cp --sparse=always /mnt/user/vmbaktemp/vdisk1.img /mnt/cache/vDisks/win7/vdisk1.img ...and I don't need to run any other trim commands or anything else, yes? Sorry, not trying to be a nuisance, just trying to make sure I understand the instructions properly.

Please excuse my ignorance, I'm guessing the cp = copy meaning I'm copying the vdisk1.img? In that case, I don't have enough free space to make a duplicate copy of it, or am I misunderstanding?

It appears the instructions layed out there are specifically with Windows 8/10 in mind. In my case, my VM is Windows 7, do the same instructions apply, or would I be better served just renaming like the post mentions?

The size of the vm is what I expect it to be, I don't see how I'm missing those 300G. The single windows vm size on disk is 550G which is what I set it to.

I don't think I'm understanding how the cache works or something. I have 2 1T drives in a cache pool, and the server registers that as 980G total, which is fine. My problem is my cache keeps filling up now and I appear to be missing more than 300G of storage from the cache drive. Please forgive my formatting. I don't know how to format it to be more readable, so I did the best I could. At this point, I'm thinking I may attempt to convert it to raid0, but even then I'm not sure if I'd have to empty the cache drive of its contents (which I'd like to avoid if-possible). At this point I'm looking to understand how more than 300G goes "missing" and how to get it back. Essentially am I not understanding some kind of math here, or how the cache operates or something? du -sh /mnt/cache = 600G /mnt/cache so where am I being mistaken? It seems to me that 980-600=380 and I would even allow for some overhead, but 300G?? Can someone point me in the right direction here? fdisk -l Disk /dev/sdj: 894.3 GiB, 960197124096 bytes, 1875385008 sectors Disk model: SanDisk Ultra II 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/sdj1 64 1875385007 1875384944 894.3G 83 Linux Disk /dev/sdk: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: SanDisk SDSSDH31 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/sdk1 64 1953525167 1953525104 931.5G 83 Linux btrfs fi df -H /mnt/cache Data, RAID1: total=960.20GB, used=952.02GB System, single: total=33.55MB, used=163.84kB Metadata, single: total=3.22GB, used=1.24GB GlobalReserve, single: total=245.89MB, used=0.00B btrfs fi show /mnt/cache Label: none uuid: 7a020af7-db4e-4f8f-99d8-af2616135849 Total devices 2 FS bytes used 887.79GiB devid 1 size 894.25GiB used 894.25GiB path /dev/sdj1 devid 2 size 931.51GiB used 897.28GiB path /dev/sdk1 btrfs fi usage /mnt/cache Overall: Device size: 1.78TiB Device allocated: 1.75TiB Device unallocated: 34.23GiB Device missing: 0.00B Used: 1.73TiB Free (estimated): 24.73GiB (min: 24.73GiB) Data ratio: 2.00 Metadata ratio: 1.00 Global reserve: 234.48MiB (used: 0.00B) Data,RAID1: Size:894.25GiB, Used:886.64GiB /dev/sdj1 894.25GiB /dev/sdk1 894.25GiB Metadata,single: Size:3.00GiB, Used:1.16GiB /dev/sdk1 3.00GiB System,single: Size:32.00MiB, Used:160.00KiB /dev/sdk1 32.00MiB Unallocated: /dev/sdj1 1.05MiB /dev/sdk1 34.23GiB