bmacklin

So I want to say I'm probably screwed and need to do a btrfs recover to a volume that is big enough. Problem is my volume is nearly 64TB (and is completely filled) and I don't have anything now or soon to be able to dump the btrfs volume to. Even more concerning is that I am getting kernel panics running btrfs commands. I am running 6.2.3 update-2. What happened: I was adding more drives to my NAS and might have bumped the sas to 4 sata cable in my machine. When I booted up, a few drives showed up as disconnected, needing to be initialized, bad system partition, etc, I shutdown, wiggled a few cables and rebooted, still having issues but with a different set of drives. I shutdown once again and booted again. This time, one drive shows up as disconnected and needing to be added to the volume, while the other three say they have bad system partition. I started the repair process in DSM and added the disconnected drive back to the volume, which started a consistency check. Still checking parity consistency. I also repaired the system partition which completed and all 8 drives are showing healthy. The pool says 64TB used / 64TB total, the volume says 0 bytes used / 1 byte total. This is the part that has me worried. Usually checking consistency is a background process. At this point the volume should be usable. I started googling and found my way back to the xpenology forums. I followed the advice here: https://xpenology.com/forum/topic/14337-volume-crash-after-4-months-of-stability I tried mount -o recovery,ro /dev/vg1/volume_1 /volume1 , got these errors from dmesg: [34649.993061] BTRFS error (device dm-1): parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.003239] BTRFS error (device dm-1): parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013465] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013490] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013521] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013541] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013563] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013584] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013602] BTRFS error (device dm-1): failed to read block groups: -5 [34650.039212] BTRFS: open_ctree failed I also ran btrfs check --check-data-csum /dev/vg1/volume_1 but I got a kernel panic... [34650.003239] BTRFS error (device dm-1): parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013465] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013490] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013521] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013541] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013563] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013584] parent transid verify failed on 10053299585024 wanted 154500 found 154497 [34650.013602] BTRFS error (device dm-1): failed to read block groups: -5 [34650.039212] BTRFS: open_ctree failed [34976.628348] btrfs[5977]: segfault at f9f80e81 ip 000000000042edff sp 00007ffc1ee25880 error 4 in btrfs[400000+9d000] yikes some of the other commands that were suggested had that error where synology's btrfs tools mismatched the open source version. btrfs check --init-extent-tree /dev/vg1/volume_1 couldn't open RDWR because of unsupported option features (3). Couldn't open file system So yeah, so I'm thinking I'm kind of screwed. I'm hoping the partition checks will finish and magically everything will be back, but I kind of doubt it. I'm thinking maybe I should boot from a live USB drive and try to mount the partition, see what data is actually recoverable before I decide if I should spend money to build an array that large just so I can recover a bunch of corrupted data. If I go the liveUSB route, which distro and version would you recommend? Anything else I can try?

Update - My problem is now my ovs-vsctl and network settings are not persisted across reboots. I have added mac3 and mac4 and changed the number of ports in the grub.cfg file When I enable open vswitch, and reboot, I see ovs_eth[0-4] but only eth[01]. I have to ssh into the box to do: ip link set ovs_eth2 down # eth2 is the 10gb port ovs-vsctl add-port ovs_eth2 eth2 ip link set ovs_eth2 up ip link set eth2 up These settings are not persistent across boot. I have to run these commands each time. How do I get synology to persist these changes? Alternatively, I'd be fine if I can execute these commands after boot as root user. Thanks!

I have a motherboard with two onboard 1gb ethernet and that was recognized and working no problem. I added a mellanox cx312a 10gb two port sfp+ card and the loaded extra.lzma and extra2.lzma and the card was recognized and works... until I enabled virtual manager which enabled vSwitch. Upon reboot I still see the 4 ports, but the two 10gb ports are inactive and disconnected (but it is directly connected to another machine, was working and transferring at the expected speed before the reboot). So after hours of troubleshooting, I ssh'd in and used ifconfig to look at the interfaces. I got eth0 and eth1 and 4 ov?_eth[0-3]. Looked up what those ov interfaces were and lead to vSwitch. So then disabled vSwitch and viola, eth1 and eth2 came back again and works again. But that means virtual machine manager is uninstalled so I can't run virtual machines. I added all the mac addresses to grub.cfg and also changed the number of ports to 4. It would really be good to be able to enable both virtual machine manager and still use 10gb!

I don't want to hijack this thread too much but the problem was enabling the virtual machine manage which enabled vSwitch. It "masked" the physical eth ports.

Upon reboot, the network card with its two ports are detected but plugging the cable in the port doesn't show up as active. This worked before I rebooted though and I was using a DAC cable between two computers. I added the extra mac addresses to the grub.cfg file as mac3 and mac4 but no change. What do I have to do to fix this for the 918+ again? I read about the two port limitation but I thought adding the extra mac addresses would just work?

I'm an idiot. Plugged my usb drive in and the fat32 partition was mounted by windows. Renamed the original extra and extra2.lmza files and copied the files from the 0.8 syno package and it booted and the mellanox network card showed up!

I have a haswell system with 1.04b and DSM 6.2.2. I have a mellanox connectx-3 (cx312a) card that is not detected. The instructions are still not clear - what exactly do I need to do to get the drivers (0.8) on the usb drive that I have? I'm already on the latest DSM so I don't think I can modify a newer pat file and then upgrade my system. I have downloaded the extra918plus_v0.8 zip file and there are two lzma files. Do I extract both to the second partition on my USB and that's it?

This is amazing news and an awesome workaround! Please let us know if you figure out a way to directly boot windows!

Yeah, it was a long shot. By all accounts it should have been pretty easy and straightforward to have that VMM working but for some reason it just doesn't work for me. I have reinstalled DSM twice now. I also have two ethernet ports. Both are on the same subnet. I dedicated one for cluster-to-cluster communication and tried assigning my VMs to the other one, but no luck.

Anyone else using the virtual machine manager with their DSMs?

Why did they disable SHR? I thought it was more flexible and probably better than raid.

Running DSM 6.1.2-15132 baremetal. Everything working great except two issues: 1. Virtual Machine Manager doesn't allow me to noVNC connect to my instances. I can connect the first time during a VM installation, but once windows reboots the noVNC doesn't reconnect and will never connect to it again. I have been able to load the storage drivers during installation... noVNC is unable to reconnect or ever connect again after the first reboot. I tried loading a VMDK of another virtual machine created elsewhere and it won't connect either. 2. SHR is missing as an option during storage creation. I tried this a few times and same results each time. SHR is simply not available as an option. Anyone else experience these issues?

I'm not sure that works - the installation installs the PAT on all disks, including the boot right? Anyway, that's not the biggest issue. The biggest is why I can't get this to work in VirtualBox???

I'm creating a xpenology in a virtual box machine to test it out before putting it in a server. However, I cannot get past the error during DSM assistant installation "error formatting disk". I am following instructions here: http://idmedia.no/projects/xpenology/in ... -or-later/ I have injected a new SN and mac1 address in my syslinux.cfg and it looks like this below. The pat file I'm using is : DSM 5.2-5644 (28.10.15) And the bootloader is XPEnoboot DS3615xs 5.2-5644.1 The installation process formats the boot drive with the bootloader, so each time that it fails I need to recreate the vmdsk file and that's annoying. I get the same error (code 32) if I do the installation from the web page. Thanks in advance! UI menu.c32 PROMPT 0 TIMEOUT 50 DEFAULT xpenology MENU TITLE XPEnoboot 5.2-5644.1 LABEL xpenology MENU LABEL XPEnology DSM 5.2-5644 KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B4LWN04264 mac1=0011327084AC rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 LABEL debug MENU LABEL XPEnology DSM 5.2-5644 Debug KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B4LWN04264 mac1=0011327084AC rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 debug=1 LABEL install MENU LABEL XPEnology DSM 5.2-5644 Install/Upgrade KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B4LWN04264 mac1=0011327084AC rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.2-5644