a12vman

Members
  • Posts

    137
  • Joined

  • Last visited

Posts posted by a12vman

  1. I have a share(Download) that exists on an unassigned HGST 4TB Drive.  I use it for all of my sabnzbd downloads.

     

    This has been working fne for over a year but now I can't access any of the files on the share after i mount.  The share is not available on any of my windows clients.  Sabnzbd can't find this share anymore.

    I can see the share in Krusader but it shows empty.  

    I can browser this share from the Unraid Main Page and see folders and files.

     

    Am I missing something here?  Checked Syslogs but I don't see anything eventful.

     

  2. My parity re-build completed this morning. 

    I formatted the 18TB Drive as XFS and started the Pre-Clear with Pre and Post Read.

     

    This process is going to take a long time.  I shrunk my array from 4 to 3 drives last year.

     

    It took forever to empty a 6TB Drive using UnBalance.  Cant wait to see how long it will take this time.

  3. Thank you  I will re-build.

     

    Long-term I need to get these drives away from Reiser.

     

    I was reading the LimeTech document about how to migrate away from Reiser.  

     

    Why can't I just replace my drives 1 at a time with a new XFS formatted & Pre-Cleared Drive, then Re-Build from Parity?

     

    Does the data migration have to involve Rsync or the Unbalance Plugin?

     

  4. I stopped the Array, went to tools --> New Config. Choose "All" for Preserve Current Assignments.

    Clicked the "Yes i want to do this" checkbox and then clicked "Apply".

    Went back to the Main Tab and changed Disk 1 to the original 10TB Drive.

    I Started the array. The array came up but started a Parity Sync. I cancelled it immediately.

    I browsed my shares and it looks like I have everything except a couple movies/shows that I added in the last couple days.

    Now my array is online and everything is running. My Parity Drive says that Parity is Invalid.

    There is no "check parity" button.  The only option I see is a "Sync" button which says "Sync will start Parity-Sync and/or Data-Rebuild. "

    I just want to be sure that clicking the "Sync" button will re-build the Parity Drive but not write anything to my data drives.

    I don't want to lose any data.

  5. Oh wow that is a big undertaking.  I am so screwed.  I picked up a new 18TB drive and rebuild from parity. See the screenshot below where Disk 1 is showing invalid size.  

    I take it "EB" is short for Exobytes?

     

    My default FS in Disk settings is XFS but this drive was formatted as Reiser.  

     

    On top of all of this my parity build just completed.  My Movies share is empty even though it still shows as 4.7TB computed space.

     

    I have never done the New Config Option before, can someone walk me through it?  

     

     

    image.thumb.png.e09bebf3d008f2d9bffbc042be1f6782.png

  6. Here is log info for Disk 1:

     

    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] 4096-byte physical blocks
    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] Write Protect is off
    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] Mode Sense: 7f 00 10 08
    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Feb 13 11:21:25 MediaTower kernel: sdd: sdd1
    Feb 13 11:21:25 MediaTower kernel: sd 7:0:2:0: [sdd] Attached SCSI disk
    Feb 13 11:21:49 MediaTower emhttpd: WDC_WD180EDGZ-11BLDS0_8LG1Z0DF (sdd) 512 35156656128
    Feb 13 11:21:49 MediaTower kernel: mdcmd (2): import 1 sdd 64 17578328012 0 WDC_WD180EDGZ-11BLDS0_8LG1Z0DF
    Feb 13 11:21:49 MediaTower kernel: md: import disk1: (sdd) WDC_WD180EDGZ-11BLDS0_8LG1Z0DF size: 17578328012
    Feb 13 11:21:49 MediaTower emhttpd: read SMART /dev/sdd
    Feb 13 11:21:53 MediaTower root: /usr/sbin/wsdd
    Feb 13 11:22:03 MediaTower root: /usr/sbin/wsdd
    Feb 13 11:22:12 MediaTower wsdd[9419]: udp_send: Failed to send udp packet with Invalid argument
    Feb 13 11:22:12 MediaTower wsdd[9419]: udp_send: Failed to send udp packet with Invalid argument
    Feb 13 11:22:12 MediaTower wsdd[9419]: Failed to send hello with Invalid argument
    Feb 13 12:00:25 MediaTower emhttpd: read SMART /dev/sdd
    Feb 13 12:00:51 MediaTower root: /usr/sbin/wsdd
    Feb 13 12:03:37 MediaTower kernel: sd 7:0:2:0: [sdd] Synchronizing SCSI cache
    Feb 13 12:03:37 MediaTower kernel: sd 7:0:2:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] 4096-byte physical blocks
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] Write Protect is off
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] Mode Sense: 7f 00 10 08
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Feb 13 12:04:55 MediaTower kernel: sdd: sdd1
    Feb 13 12:04:55 MediaTower kernel: sd 7:0:6:0: [sdd] Attached SCSI disk
    Feb 13 12:04:56 MediaTower unassigned.devices: Disk with ID 'WDC_WD180EDGZ-11BLDS0_8LG1Z0DF (sdd)' is not set to auto mount.
    Feb 13 12:04:56 MediaTower emhttpd: WDC_WD180EDGZ-11BLDS0_8LG1Z0DF (sdd) 512 35156656128
    Feb 13 12:04:56 MediaTower kernel: mdcmd (2): import 1 sdd 64 17578328012 0 WDC_WD180EDGZ-11BLDS0_8LG1Z0DF
    Feb 13 12:04:56 MediaTower kernel: md: import disk1: (sdd) WDC_WD180EDGZ-11BLDS0_8LG1Z0DF size: 17578328012
    Feb 13 12:04:56 MediaTower emhttpd: read SMART /dev/sdd
    Feb 13 12:06:08 MediaTower root: /usr/sbin/wsdd
    Feb 13 12:06:21 MediaTower wsdd[4178]: udp_send: Failed to send udp packet with Invalid argument
    Feb 13 12:06:21 MediaTower wsdd[4178]: Failed to send hello with Invalid argument

  7. Long-time Unraid user here first time I've ever had an issue with a drive.

     

    My server spent the last 5 days preclearing and building a brand new 18TB WD Drive from parity to replace a 10TB Drive.

     

    Preclear and Parity build completed yesterday with no errors.  

     

    I got up this morning and see that the same 18TB Drive is now unmountable.

     

       Where do I go from here?  I have the original 10TB Drive, it's still in the server but unmounted.

    image.thumb.png.3c03c8579fb9c59b80ac26719ce6b09c.png

     

    In looking thru SysLog I see this:

    Feb 13 11:21:56 MediaTower kernel: REISERFS warning (device md1): journal-1207 journal_read_transaction: REPLAY FAILURE fsck required! Block to replay is outside of filesystem

    Feb 13 11:21:56 MediaTower kernel: REISERFS warning (device md1): reiserfs-2006 journal_init: Replay Failure, unable to mount

    Feb 13 11:21:56 MediaTower root: mount: /mnt/disk1: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.

    Feb 13 11:21:56 MediaTower kernel: REISERFS warning (device md1): sh-2022 reiserfs_fill_super: unable to initialize journal space

    Feb 13 11:21:56 MediaTower emhttpd: shcmd (30): exit status: 32

    Feb 13 11:21:56 MediaTower emhttpd: /mnt/disk1 mount error: not mounted

     

     

    mediatower-diagnostics-20230213-1132.zip

    image.png

  8. I just completed a Parity Rebuild, replaced a 10TB drive with an 18TB drive for additional storage.

     

    Process completed with no errors.  

     

    I have a share(Tunes) that holds my music collection.  I tried to add an album to this share from a windows client and got the error below.  

     

    I also tried it from Krusader and got a "could not create folder" error.  Everything else(VMs, Dockers, etc) seem to be working otherwise.

     

    image.png.093069b8ff027f8ddafed7f478d8b132.png

    image.png.6bfa6e4fbb67a82849f6f09761ae26e7.png

    mediatower-diagnostics-20230213-0657.zip

  9. This Windows 10 VM was working fine before the OS Upgrade 20 6.10.1 but now VM never shows up  on the network after I start it.  Works fine if I turn off PassThru and use VNC instead.  I am using a 750TI.  Any ideas? Here is VM Log.

     

    -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
    -blockdev '{"driver":"file","filename":"/mnt/user/Backup/Software/Windows10RS4/Windows 10 RS4 Pro SupremeOS Edition (x64) 2018-P2P.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
    -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
    -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \
    -blockdev '{"driver":"file","filename":"/mnt/user/Backup/Software/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
    -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
    -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
    -netdev tap,fd=37,id=hostnet0 \
    -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:5f:dc:a4,bus=pci.0,addr=0x4 \
    -chardev pty,id=charserial0 \
    -device isa-serial,chardev=charserial0,id=serial0,index=0 \
    -chardev socket,id=charchannel0,fd=35,server=on,wait=off \
    -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
    -device usb-tablet,id=input0,bus=usb.0,port=1 \
    -audiodev '{"id":"audio1","driver":"none"}' \
    -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \
    -k en-us \
    -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 \
    -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \
    -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
    -msg timestamp=on
    char device redirected to /dev/pts/0 (label charserial0)
    qxl_send_events: spice-server bug: guest stopped, ignoring
    2022-05-23T17:46:21.564375Z qemu-system-x86_64: terminating on signal 15 from pid 11070 (/usr/sbin/libvirtd)
    2022-05-23 17:46:21.795+0000: shutting down, reason=shutdown
    2022-05-23 17:47:04.868+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.40-Unraid, hostname: MediaTower
    LC_ALL=C \
    PATH=/bin:/sbin:/usr/bin:/usr/sbin \
    HOME=/var/lib/libvirt/qemu/domain-3-W10 \
    XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-W10/.local/share \
    XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-W10/.cache \
    XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-W10/.config \
    /usr/local/sbin/qemu \
    -name guest=W10,debug-threads=on \
    -S \
    -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-W10/master-key.aes"}' \
    -machine pc-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram \
    -accel kvm \
    -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \
    -m 4096 \
    -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296}' \
    -overcommit mem-lock=off \
    -smp 4,sockets=1,dies=1,cores=2,threads=2 \
    -uuid d07abd87-eb87-d4df-0f35-11c60bebc1c8 \
    -display none \
    -no-user-config \
    -nodefaults \
    -chardev socket,id=charmonitor,fd=36,server=on,wait=off \
    -mon chardev=charmonitor,id=monitor,mode=control \
    -rtc base=localtime \
    -no-hpet \
    -no-shutdown \
    -boot strict=on \
    -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
    -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
    -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
    -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
    -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
    -blockdev '{"driver":"file","filename":"/mnt/user/domains/W10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
    -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
    -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
    -blockdev '{"driver":"file","filename":"/mnt/user/Backup/Software/Windows10RS4/Windows 10 RS4 Pro SupremeOS Edition (x64) 2018-P2P.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
    -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
    -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \
    -blockdev '{"driver":"file","filename":"/mnt/user/Backup/Software/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
    -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
    -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
    -netdev tap,fd=37,id=hostnet0 \
    -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:5f:dc:a4,bus=pci.0,addr=0x2 \
    -chardev pty,id=charserial0 \
    -device isa-serial,chardev=charserial0,id=serial0,index=0 \
    -chardev socket,id=charchannel0,fd=35,server=on,wait=off \
    -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
    -device usb-tablet,id=input0,bus=usb.0,port=1 \
    -audiodev '{"id":"audio1","driver":"none"}' \
    -device vfio-pci,host=0000:06:00.0,id=hostdev0,bus=pci.0,addr=0x5 \
    -device vfio-pci,host=0000:06:00.1,id=hostdev1,bus=pci.0,addr=0x6 \
    -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
    -msg timestamp=on
    char device redirected to /dev/pts/0 (label charserial0)
     

  10. I ran the upgrade this morning thru the webui Update OS - big mistake.

     

    Flash Drive update completed and prompted for a reboot.  Did the reboot but server not available.

     

    It's not that I can't login to the WebUI, it is not even on the network.  What do I do now?

     

    I haven't touched anything on my server it has been fine for months, finding it hard to believe that there is some sort of hardware failure after the reboot.

  11. I don't know what I did wrong, but I completely lost my Sonarr Library and my Plex Library.

     

    I could have restored, I had 7 days of CA Backups.

     

    Instead I changed the AppData Config Path to explicitly use /Cache_NVME/Appdata/Sonarr and the same for Plex.

     

    I rebuilt both libraries and all is well.

     

    It's a housekeeping task I have been wanting to do for some time.  The only downside is I lost all of my viewing history.

     

     

  12. I did follow SI-1's process of migrating cache data using the cache settings.

     

    Moved appdata from Old Cache to Array

    Moved appdata from Array to New Cache

     

    I think where I went wrong.  I didn't update the AppData Config path from /mnt/user/appdata/sonarr to /Cache_SSD/Appdata/sonarr

     

    I repointed my containers.  Everything seems to be working now.

     

    Thanks for your help, not sure how I missed that step!

  13. I added a 2nd Cache Drive several months ago following SI-1's cookbook. My original cache drive is Cache_SSD and my new one is Cache_NVME.

    I modified my share settings so all folders that I want to cache point to Cache_SSD.  Docker, VM, and Appdata are set to Cache_NVME.

    Everything checked out when I was done all Dockers and VM's were functioning.

    Just looking around on Krusader and noticed that Cache_SSD still has an AppData folder with a folder for each Docker.

     

    I changed the folder Name of Sonarr at this location to Sonarr1.  My Sonarr library is now empty(says no series found) even after I renamed it  back to Sonarr and restarted the app.

    The container path for all of my dockers is still set to \Mnt\User\AppData\<Docker Name>, do I need to update these paths?

    Is there any way to get back my Sonarr Library?  I do CA Appdata Backups Daily.

     

    Sizes of Appdata:

    Cache_SSD: 758MB

    CACHE_NVME: 42GB

     

    Thanks,

    a12vman

     

     

  14. Thanks I never thought  of checking unofficial driver support.

     

    My bigger issue is that I can't even get the VM to boot up when I change the Graphics to the 750ti and start the VM.

    The VM is running, the logs look normal but it never appears on the network so I can connect via RDP.

    I ping the Machine Name from a windows client but it's not available.

    The VM Log looks normal and I don't see anything in the System Log.

     

    I have created Windows 7/10/11 Vm's using this card for GPU Passthru and had no issues.

  15. I was able to stand up a Windows XP Pro VM thanks to advice on this forum.

     

    I have it working with VNC but want to do GPU Passthru.  I have a GTX750ti card.  The oldest OS drivers 

    available from Nvidia are for Windows 7 64.  

     

    I can start the VM with GPU Passthru but it never boots up.  Is this too much of an ask(assigning a video card

    to an OS that predates the graphics card?  I have some XP-era games that I would like to play that won't run on 

    Windows 7.

     

    Thanks in Advance,

    a12vman