ToXIc

ok will preclear it and hold as spare

plz see attached WDC_WD40EFRX-68N32N0_WD-WCC7K6TSYCEL-20220905-1317.txt

thank for you help btw, wished i posted here to begin with

i am took a bit to figure out how to get it to show up.. should i preclear the old drive and trust it?

recreated the log and i see some data not everything but some

i click on the check mark in UD and i get FS: xfs Executing file system check: /sbin/xfs_repair -n /dev/sdx1 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 895215175, counted 902030091 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. File system corruption detected!

got the drive added to the system it shows up in UD but i dont see a "Check Filesystem Status" section in the Disk settings window for the drive the drive is xfs

ok

i have a usb doc that loads drives to UD but it runs 1/3 or the speed. or use sata?

i still have the old disk.. it did say "unmountable" ill review the link

yea i rebooted hoping it would of shown the contents of drive 18, it asked to format 18 when i added 9 to the system and i did, i guess that killed the data? i also have this new section since all this occurred

oh my b i looked at the persistent diagnostic service uploaded logs here and 1st post fatjoe-diagnostics-20220905-1015.zi

unfortunately the service wasnt running

i just uploaded the logs from http://tower/log/syslog should i gather via the method you posted?

Hi everyone, been using unraid since v4 and have replaced many drives since then. recently however was my 1st time 2 drives went bad at the same time. I'm currently on version 6.9.2 and using two parity drives. Before i did anything i noticed that one of the emulated drives showed nothing, my data in some folders were missing. Not thinking too much about it hoping it was a bug or something i proceeded with my replacement process and got my drives preclearing. I swapped them one by one leaving the badly emulated drive last. When i did switch to the 2nd drive the rebuild took over 12hrs and did almost 4tb of write to the drive but unfiortualtely my data still wasnt there.. am i still seeing the emulation or is my data really gone. syslog fatjoe-diagnostics-20220905-1015.zip

oh wow.. didnt see that. i wonder when i did the Unraid Nvidia plugin and did the OS upgrade then OS swap to the Nvidia Plugin one if it reinstalled it? this is what i see now under network settings before virbr0 wasnt there.. see above screenshot. now i need to change it to 192.168.1.0/24 because its not getting any traffic still. edit: nope all good. it had the static setting in there from trouble shooting. changed to DHCP and its working we have web again!! thx

here you go sirs fatjoe-diagnostics-20200504-0825.zip

i did that sir and still no luck.

been messing with it all day today.. still zero success. any recommendations?

no error in the VM logs it just dont want to connect, even with a static IP

so here is my current network.cfg # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DNS_SERVER2="8.8.4.4" DHCP6_KEEPRESOLV="no" BONDNAME[0]="bond0" BONDNICS[0]="eth0 eth1 eth2 eth3" BONDING_MODE[0]="6" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRNICS[0]="bond0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.69" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" USE_DHCP6[0]="yes" IFNAME[1]="br4" BRNAME[1]="br4" BRSTP[1]="no" BRFD[1]="0" BRNICS[1]="eth4" PROTOCOL[1]="ipv4" USE_DHCP[1]="yes" SYSNICS="2" i looked at my old in but dont see any mention of virbr0

is there a way to manually rebuid the virbr0 interface?

so apparently i lost my virbr0 interface when i reconfigured the nics?

Hey guys not sure why but ive changed the bridge method for eth0 to the following (see pic below) but since doing so it has broken the network on the VMs. previously the VMs were set to virbr0 but the VMs cannot find the network anymore, i've change it to br0 but still nogo, I dont have any other network options in the VM config.

Ummm hello?! It’s in the name. “unRaid” I love having JDOB with parity. im not soo sure what else you can add. The flexibility ver6 gave to the platform and with the community’s additions it’s a dream. I don’t even see unraid as a storage server anymore it’s “My Hypervisor” I guess the best thing you can do with unraid is keep its development and support for the latest hardware going. Please never let this great product die. a second thing would be to probably partner spaceinvader one. He has helped soo many of us with tutorials which have expanded the use of our servers soo much.