frooop

Transition Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About frooop

  • Rank
    Newbie
  1. i tried to use them with the script it doesn't create a single "333..." WellBlock file Since it doesn't find a single well block... ash-4.3# btrfs-find-root /dev/vg1/volume_2 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 Ignoring transid failure parent transid verify failed on 6095751888896 wanted 15520595 found 155
  2. i'm already as root/sudo on the machine, but tried it too with sudo before... ash-4.3# mount -o recovery,ro /dev/vg1/volume_2 /volume2 mount: wrong fs type, bad option, bad superblock on /dev/vg1/volume_2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ash-4.3# sudo mount -o recovery,ro /dev/vg1/volume_2 /volume2 mount: wrong fs type, bad option, bad superblock on /dev/vg1/volume_2, missing codepage or helper program, or other error In some cases useful info is found in sy
  3. i did... got after every command the "wrong fs type" error ash-4.3# mount -o ro /dev/vg1/volume_2 /volume2 mount: wrong fs type, bad option, bad superblock on /dev/vg1/volume_2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ash-4.3# dmesg | tail [ 707.211487] parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 [ 707.216825] parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 [ 707.216828] BTRFS error (device dm-1): BTRFS: dm-1 f
  4. Output below... ash-4.3# btrfs rescue super /dev/vg1/volume_2 All supers are valid, no need to recover ash-4.3# btrfs-find-root /dev/vg1/volume_2 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 parent transid verify failed on 6095662284800 wanted 15520571 found 15507911 Ignoring transid failure parent transid verify failed on 6095751888896 wanted 15520595 found 15507981 parent transid verify failed on
  5. Some more, i case needed ash-4.3# btrfs inspect-internal dump-super -f /dev/vg1/volume_2 superblock: bytenr=65536, device=/dev/vg1/volume_2 --------------------------------------------------------- csum 0xccc63a47 [match] bytenr 65536 flags 0x1 ( WRITTEN ) magic _BHRfS_M [match] fsid dfeb27ca-82a4-4861-a849-4ffe88ea67be label 2017.04.27-14:46:20 v15047 generation 15520602 root 29360128 sys_array_size 129 chunk_r
  6. i tried and got the following lines back ash-4.3# mount /dev/vg1/volume_2 /volume2 mount: wrong fs type, bad option, bad superblock on /dev/vg1/volume_2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ash-4.3# mount -o clear_cache /dev/vg1/volume_2 /volume2 mount: wrong fs type, bad option, bad superblock on /dev/vg1/volume_2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ash-4.3# mount -o
  7. Hi together i got a problem with a crashed volume and my knowledge is now on a point where I need some help I already did a few lines to identify a failure (attached because the forum doesn't like it) I found in the above response these two error lines, but couldn't find anything else about it Found dropping subvolume ID:10011501971644612608 dropping progress: key (259824214343680 UNKNOWN.0 697453126021545984) level: 0 Errors found in extent allocation tree or chunk allocation commands.txt
  8. frooop

    DSM 6.2 Loader

    Good to know I will look to find the older 9300 series card and swap them out... Thanks flyride and IG-88 for the quick help
  9. frooop

    DSM 6.2 Loader

    Tried that with migration to the DS3615xs image and its not showing the drives... Seems like i have to create RDMs or change the HBA to a different one...
  10. frooop

    DSM 6.2 Loader

    Got a problem with a newly created Xpenology VM i passed through a Broadcom HBA 9400-8i with 2x WD Red Pro 8TB connected (in POST and VMware ESXi they get detected) But they dont get recognized in the DS3617xs with the 1.03b Loader (also tried the DS3615xs and the DS918+) Currently its running on DSM 6.2-23739 Already got a DS3615xs VM with an LSI2008, also 1.03b Loader, running without a problem but this thing gives me headaches Somebody got an idea? Could it be a driver problem that would be "fixed" with the driver extension from IG-88? Driver Ext
  11. frooop

    DSM 6.2 Loader

    i tried to install it completely new as VM on an HP MicroServer Gen8 with an E3-1230 V2 with ESXi 6.5 Update 2 i have an Xpenology Machine DS3615xs running with the 1.02b Loader just fine, but with the new 1.03b and DS3615xs bootloader it starts like the other one and stops on [...] Happy Hacking It then should get an IP from DHCP but nothing happens... tried several restarts and also switching between UEFI and BIOS Mode even before starting the vm for the first time it ran for over 10 Minutes between switching to ensure that it doesnt take some time to start all services etc