Jump to content
XPEnology Community

flyride

Moderator
 View Profile  See their activity

  • Posts

    2,438

  • Joined

  • Last visited

  • Days Won

    127

 Content Type 

Posts posted by flyride

    Voulme [1] was crashed. Unable to mount btrfs partition

    in General Post-Installation Questions/Discussions (non-hardware specific)

    Posted

    Not easy to do.  Synology have "private" tools they use for repairing btrfs... the standard btrfs check tools don't work to update the filesystem.

     

    Review this thread

     

    Also, I recently ran across a temporary posting of a full Syno repair and recovery and saved it off.  It includes downloading some of the Syno private tools and should NOT be blindly followed, as it fixes a random person's btrfs corruption.  But it might give you some more ideas and/or tactics.

     

    Spoiler

    2019-05-22T09:05:41-07:00 <NAS NAME> -sh: HISTORY: PID=4905 UID=1024 sudo -i
    2019-05-22T09:05:48-07:00 <NAS NAME> -ash: HISTORY: PID=4927 UID=0 cat /proc/mdstat
    2019-05-22T13:59:22-07:00 <NAS NAME> -sh: HISTORY: PID=1908 UID=1024 sudo -i
    2019-05-22T13:59:41-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 cat /proc/mdstat
    2019-05-22T14:02:44-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 echo idle > /sys/block/md2/md/sync_action
    2019-05-22T14:02:56-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 ls /etc/space
    2019-05-22T14:03:12-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 cat /space/etc/space_history_20190228_091858.xml
    2019-05-22T14:03:28-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 cat /etc/space/space_history_20190228_091858.xml
    2019-05-22T14:04:09-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 mdadm -S /dev/md2
    2019-05-22T14:06:38-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 mdadm -Sf /dev/md2
    2019-05-22T14:06:49-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 mount
    2019-05-22T14:06:59-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 /umount /volume2
    2019-05-22T14:07:04-07:00 <NAS NAME> -ash: HISTORY: PID=2031 UID=0 umount /volume2
    2019-05-24T15:29:44-07:00 <NAS NAME> -sh: HISTORY: PID=27873 UID=1024 sudo -i
    2019-05-24T15:32:56-07:00 <NAS NAME> -ash: HISTORY: PID=27889 UID=0 syno_poweroff_task -d
    2019-05-24T17:20:27-07:00 <NAS NAME> -sh: HISTORY: PID=1021 UID=1024 sudo -i
    2019-05-24T17:20:52-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 wget -P /tmp https://sacmirror.synology.me/host/scripts/sac_poweroff_task.sh; chmod +x /tmp/sac_poweroff_task.sh
    2019-05-24T17:20:57-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 sh /tmp/sac_poweroff_task.sh -off
    2019-05-24T17:22:17-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 cat /proc/mdstat
    2019-05-24T17:22:28-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 ls /etc/space
    2019-05-24T17:22:38-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 cat /etc/space/space_history_20190521_023217.xml
    2019-05-24T17:22:54-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 mount
    2019-05-24T17:24:00-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 sfdisk -l
    2019-05-24T17:24:25-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 cat /etc/space/space_history_20181010_093903.xml
    2019-05-24T17:25:03-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 lvm lvscan
    2019-05-24T17:25:09-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 mount
    2019-05-24T17:25:58-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 mount /dev/vg1000/lv /volume1
    2019-05-24T17:27:16-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 vgs
    2019-05-24T17:27:19-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 pvs
    2019-05-24T17:27:35-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 synofstool -–get-fs-type /dev/vg1000/lv
    2019-05-24T17:28:23-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 lvm pvscan
    2019-05-24T17:28:35-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 mount
    2019-05-24T17:31:24-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 dmesg | tail
    2019-05-24T17:32:40-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs-show-super /dev/vg1000/lv
    2019-05-24T17:33:23-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs check --clear-space-cache v1 /dev/vg1000/lv
    2019-05-24T17:33:37-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs check --clear-space-cache v2 /dev/vg1000/lv
    2019-05-24T17:33:59-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs rescue zero-log /dev/vg1000l/v
    2019-05-24T17:34:04-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs rescue zero-log /dev/vg1000/lv
    2019-05-24T17:34:23-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 mount /dev/vg1000/lv /volume1
    2019-05-24T17:34:48-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0  dmesg | tail
    2019-05-24T17:35:07-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs-show-super /dev/vg1000/lv
    2019-05-24T17:35:16-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs-show-super -a /dev/vg1000/lv
    2019-05-24T17:36:07-07:00 <NAS NAME> -ash: HISTORY: PID=1086 UID=0 btrfs-show-super -f /dev/vg1000/lv
    2019-05-28T15:57:27-07:00 <NAS NAME> -sh: HISTORY: PID=18359 UID=1024 sudo -i
    2019-05-28T15:57:42-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 cat /proc/mdstat
    2019-05-28T15:57:48-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mount
    2019-05-28T15:57:56-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 ls /etc/space
    2019-05-28T15:58:10-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 cat /etc/space/space_history_20180831_192154.xml
    2019-05-28T15:58:21-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 lvm lvscan
    2019-05-28T15:59:07-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 cat /etc/space/space_history_20190228_091858.xml
    2019-05-28T15:59:42-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 cat /etc/space/space_history_20190519_163250.xml
    2019-05-28T16:00:08-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 vgs
    2019-05-28T16:00:11-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 pvs
    2019-05-28T16:00:32-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 pvdisplay
    2019-05-28T16:02:00-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 vgchange -an /dev/vg1000
    2019-05-28T16:02:23-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mdadm -S /dev/md2
    2019-05-28T16:03:00-07:00 <NAS NAME> -sh: HISTORY: PID=23088 UID=1024 sudo -i
    2019-05-28T16:03:08-07:00 <NAS NAME> -ash: HISTORY: PID=23187 UID=0 tail -f /var/log/messages
    2019-05-28T16:04:10-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mdadm -A /dev/m2 /dev/sdg[abcde]5
    2019-05-28T16:04:15-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mdadm -A /dev/md2 /dev/sdg[abcde]5
    2019-05-28T16:04:34-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 pvs
    2019-05-28T16:04:35-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 vgs
    2019-05-28T16:04:41-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 lvm lvscan
    2019-05-28T16:04:59-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 vgchange -ay /dev/vg1000
    2019-05-28T16:05:09-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 synofstool -–get-fs-type /dev/vg1000/lv
    2019-05-28T16:08:20-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mount -o ro,no_block_group /dev/vg1000/lv /volume3
    2019-05-28T16:08:32-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 dmesg | tail
    2019-05-28T16:09:30-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 btrfs-show-super -a /dev/vg1000/lv
    2019-05-28T16:10:45-07:00 <NAS NAME> -ash: HISTORY: PID=18458 UID=0 mount -o ro,no_block_group,nologreplay /dev/vg1000/lv /volume3
    2019-05-28T22:51:19-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 ls
    2019-05-28T22:51:22-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 cd /
    2019-05-28T22:51:23-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 ls
    2019-05-28T22:51:29-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 cd volume1
    2019-05-28T22:51:30-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 ls
    2019-05-28T22:51:31-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 cd ..
    2019-05-28T22:51:38-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 cd volume3
    2019-05-28T22:51:39-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 ls
    2019-05-28T22:51:52-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 cd ..
    2019-05-28T22:52:33-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 df
    2019-05-28T23:00:01-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 mdadm --detail /dev/md1
    2019-05-28T23:00:05-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 sudo mdadm --detail /dev/md1
    2019-05-28T23:00:23-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 sudo mdadm --detail /dev/md2
    2019-05-28T23:00:28-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 sudo mdadm --detail /dev/md3
    2019-05-28T23:00:32-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 sudo mdadm --detail /dev/md0
    2019-05-28T23:00:51-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 ls /dev/
    2019-05-28T23:01:25-07:00 <NAS NAME> -sh: HISTORY: PID=20204 UID=1026 sudo mdadm --detail /dev/md4
    2019-05-29T11:18:10-07:00 <NAS NAME> -sh: HISTORY: PID=10301 UID=1024 sudo -i
    2019-05-29T11:18:17-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 vim /var/log/messages
    2019-05-29T11:18:49-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 lvm lvscan
    2019-05-29T11:19:03-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 mount
    2019-05-29T11:19:24-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 btrfs-show-super -f /dev/vg1000/lv
    2019-05-29T11:20:58-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 ll
    2019-05-29T11:21:05-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 nohup btrfs check /dev/vg1000/lv
    2019-05-29T11:21:14-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 tail nohup.out
    2019-05-29T11:21:33-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 ps -aux |grep btrfs
    2019-05-29T11:21:46-07:00 <NAS NAME> -ash: HISTORY: PID=10307 UID=0 cat nohup.out
    2019-05-29T21:55:30-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 mdadm --detail /dev/md0
    2019-05-29T21:55:38-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md0
    2019-05-29T21:55:44-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md1
    2019-05-29T21:55:47-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md2
    2019-05-29T21:55:59-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md3
    2019-05-29T21:56:01-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md2
    2019-05-29T21:56:04-07:00 <NAS NAME> -sh: HISTORY: PID=12890 UID=1026 sudo mdadm --detail /dev/md4
    2019-06-19T20:46:11-07:00 <NAS NAME> -sh: HISTORY: PID=28616 UID=1024 sudo -i
    2019-06-19T20:46:13-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 df
    2019-06-19T20:57:25-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cd /etc/space/
    2019-06-19T20:57:25-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 ll
    2019-06-19T20:57:32-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat space_history_20190616_191337.xml
    2019-06-19T20:57:35-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 df -h
    2019-06-19T20:58:29-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 synologoncvert /var/log/synolog/.SYNOSYSDB |grep crash
    2019-06-19T20:58:39-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 synologconvert /var/log/synolog/.SYNOSYSDB |grep crash
    2019-06-19T20:59:55-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 free
    2019-06-19T21:00:00-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 free -h
    2019-06-19T21:02:25-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat /var/log/messages |grep 2019-05-18T00
    2019-06-19T21:08:12-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat /var/log/messages |grep 2019-05-18T04
    2019-06-19T21:20:59-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat /etc/VERSION
    2019-06-19T21:26:06-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cd /root
    2019-06-19T21:26:06-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 ll
    2019-06-19T21:26:10-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat nohup.out
    2019-06-19T21:26:28-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat /var/log/bash_history.log
    2019-06-19T21:28:59-07:00 <NAS NAME> -ash: HISTORY: PID=28654 UID=0 cat /proc/mdstat
    2019-06-20T18:44:26-07:00 <NAS NAME> -sh: HISTORY: PID=7480 UID=1024 sudo -iu
    2019-06-20T18:44:29-07:00 <NAS NAME> -sh: HISTORY: PID=7480 UID=1024 sudo -i
    2019-06-20T18:44:40-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 df
    2019-06-20T18:44:46-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 cd /etc/space/
    2019-06-20T18:44:47-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 ll
    2019-06-20T18:45:03-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 cat space_history_20190616_191337.xml
    2019-06-20T18:45:14-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 sfdisk -l
    2019-06-20T18:47:29-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 cd /root
    2019-06-20T18:47:43-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-show-super /dev/vg1000/lv
    2019-06-20T18:48:14-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-show-super -a /dev/vg1000/lv
    2019-06-20T18:49:14-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-show-super -f /dev/vg1000/lv
    2019-06-20T18:50:39-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 cd /root
    2019-06-20T18:51:41-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-super-hack -g 1714375 -r 814468104192 backup_file /dev/vg1000/lv
    2019-06-20T18:51:52-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-show-super /dev/vg1000/lv
    2019-06-20T18:52:29-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 mount -o ro /dev/vg1000/lv /volume3
    2019-06-20T18:52:46-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 tail /var/log/messages
    2019-06-20T18:53:09-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 tail /var/log/messages -n 50
    2019-06-20T18:53:18-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 date
    2019-06-20T18:55:17-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 btrfs-super-hack -b backup_file /dev/vg1000/lv
    2019-06-20T18:55:31-07:00 <NAS NAME> -ash: HISTORY: PID=7521 UID=0 mount -o ro /dev/vg1000/lv /volume3
    2019-06-20T19:03:17-07:00 <NAS NAME> -sh: HISTORY: PID=15476 UID=1024 sudo -i
    2019-06-20T19:03:18-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 df
    2019-06-20T19:03:23-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 tail /var/log/messages
    2019-06-20T19:03:26-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 date
    2019-06-20T19:03:36-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 top
    2019-06-20T19:03:44-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 ps aux |grep mount
    2019-06-20T19:03:55-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 kill -9 11804
    2019-06-20T19:03:58-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 ps aux |grep mount
    2019-06-20T19:04:04-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 ps aux |grep mount
    2019-06-20T19:05:39-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 cd /root
    2019-06-20T19:05:39-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 ll
    2019-06-20T19:05:41-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 wget ftp.synology.com/support_web/Jason_tools/BTRFS_rescue/check_root.sh
    2019-06-20T19:05:42-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 wget ftp.synology.com/support_web/Jason_tools/BTRFS_rescue/find_restore.sh
    2019-06-20T19:05:43-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 wget ftp.synology.com/support_web/Jason_tools/BTRFS_rescue/restore_btrfs_from_roots.sh
    2019-06-20T19:05:44-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 wget ftp.synology.com/support_web/Jason_tools/BTRFS_rescue/toolbox.sh
    2019-06-20T19:06:07-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 nohup bash find_restore.sh /dev/vg1000/lv &
    2019-06-20T19:06:11-07:00 <NAS NAME> -ash: HISTORY: PID=15509 UID=0 tail -f nohup.out
    2019-06-21T02:39:02-07:00 <NAS NAME> -sh: HISTORY: PID=14356 UID=1024 sudo -i
    2019-06-21T02:39:03-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 df
    2019-06-21T02:39:08-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 cd /root
    2019-06-21T02:39:10-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 df -h
    2019-06-21T02:39:15-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 ll
    2019-06-21T02:39:19-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 cat nohup.out
    2019-06-21T02:40:12-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 ps aux |grep btrfs
    2019-06-21T02:40:22-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 df -h
    2019-06-21T02:40:30-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 cat nohup.out
    2019-06-21T02:44:39-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 nohup btrfs-find-root -o 257 -l 0 /dev/vg1001/lv  > 257.roots &
    2019-06-21T02:44:54-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 cat /var/log/bash_history.log
    2019-06-21T02:45:05-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 mount
    2019-06-21T02:45:11-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 df -h
    2019-06-21T02:45:27-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 ps aux |grep btrfs
    2019-06-21T02:45:37-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 kill -9 15178
    2019-06-21T02:45:40-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 ps aux |grep btrfs
    2019-06-21T02:45:56-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 nohup btrfs-find-root -o 257 -l 0 /dev/vg1000/lv  > 257.roots &
    2019-06-21T02:46:02-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 tail -f nohup.out
    2019-06-21T02:46:14-07:00 <NAS NAME> -ash: HISTORY: PID=14367 UID=0 cat nohup.out
    2019-06-23T18:29:12-07:00 <NAS NAME> -sh: HISTORY: PID=7110 UID=1024 sudo -i
    2019-06-23T18:29:14-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 df
    2019-06-23T18:29:17-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 cd /root
    2019-06-23T18:29:17-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 ll
    2019-06-23T18:29:21-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 cat 257.roots
    2019-06-23T18:29:58-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 cat  nohup.out
    2019-06-23T18:32:41-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 cat /var/log/bash_history.log
    2019-06-23T18:33:15-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 cd /root
    2019-06-23T18:33:16-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 source toolbox.sh
    2019-06-23T18:33:16-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0 parse_root_items 257.roots | while read bytenr
    2019-06-23T18:33:16-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0   do
    2019-06-23T18:33:16-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0      btrfs restore -i -D -f "$bytenr" /dev/vg1000/lv /mnt &>/dev/null
    2019-06-23T18:33:16-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0      if [ $? -eq 0 ]; then echo "$bytenr"; fi
    2019-06-23T18:33:23-07:00 <NAS NAME> -ash: HISTORY: PID=7123 UID=0   done
    2019-06-23T18:34:14-07:00 <NAS NAME> -sh: HISTORY: PID=7110 UID=1024 sudo -i
    2019-06-23T18:34:31-07:00 <NAS NAME> -ash: HISTORY: PID=13043 UID=0 btrfs-show-super /dev/vg1000/lv
    2019-06-24T02:56:50-07:00 <NAS NAME> -sh: HISTORY: PID=28174 UID=1024 sudo -i
    2019-06-24T02:56:51-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 df
    2019-06-24T02:58:03-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 cat /var/log/bash_history.log
    2019-06-24T02:58:26-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 cd /root
    2019-06-24T02:58:26-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 ll
    2019-06-24T02:58:39-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 mv nohup.out nohup.out.old
    2019-06-24T02:58:40-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 ll
    2019-06-24T02:58:56-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 nohup bash find_restore.sh /dev/vg1000/lv &
    2019-06-24T02:58:58-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 ll
    2019-06-24T02:59:01-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 cat nohup.out
    2019-06-24T03:01:26-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 ll
    2019-06-24T03:01:38-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 cat nohup.out
    2019-06-24T03:01:50-07:00 <NAS NAME> -ash: HISTORY: PID=28180 UID=0 top
    2019-06-25T00:18:52-07:00 <NAS NAME> -sh: HISTORY: PID=3056 UID=1024 sudo -i
    2019-06-25T00:18:54-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat /proc/mdstat
    2019-06-25T00:18:56-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 df
    2019-06-25T00:19:01-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 df -h
    2019-06-25T00:19:13-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat /etc/fstab
    2019-06-25T00:20:16-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim /var/log/messages
    2019-06-25T00:21:34-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat /proc/mdstat
    2019-06-25T00:22:40-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim /var/log/messages
    2019-06-25T00:25:40-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd /etc/space/
    2019-06-25T00:25:40-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ll
    2019-06-25T00:25:46-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim space_history_20190424_172505.xml
    2019-06-25T00:26:08-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd -
    2019-06-25T00:26:11-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim /var/log/messages
    2019-06-25T00:35:59-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd /etc/space/
    2019-06-25T00:36:00-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ll
    2019-06-25T00:36:05-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim space_history_20190424_172505.xml
    2019-06-25T00:36:57-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat /proc/mdstat
    2019-06-25T00:37:06-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/md2
    2019-06-25T00:37:20-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/md2
    2019-06-25T00:37:24-07:00 <NAS NAME> -ash: SYSTEM:    Last message 'HISTORY: PID=3063 UI' repeated 1 times, suppressed by syslog-ng on <NAS NAME>
    2019-06-25T00:37:24-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -D /dev/md2
    2019-06-25T00:38:41-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 list=`synodiskport -internal`; for i in $list;do echo $i; cat /var/run/synostorage/disks/$i/serial;echo " ";done
    2019-06-25T00:38:50-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 list=`synodiskport -external`; for i in $list;do echo $i; cat /var/run/synostorage/disks/$i/serial;echo " ";done
    2019-06-25T00:39:02-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 synodiskport -external
    2019-06-25T00:39:07-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 synodiskport -ebox
    2019-06-25T00:39:13-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 synodiskport -esata
    2019-06-25T00:39:25-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 synodiskport -eunit
    2019-06-25T00:39:34-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 list=`synodiskport -eunit`; for i in $list;do echo $i; cat /var/run/synostorage/disks/$i/serial;echo " ";done
    2019-06-25T00:40:00-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -D /dev/md2
    2019-06-25T00:40:23-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/sdga5
    2019-06-25T00:41:02-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/sdgb5
    2019-06-25T00:42:13-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/sdgc5
    2019-06-25T00:42:51-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/sdgd5
    2019-06-25T00:43:24-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mdadm -E /dev/sdge5
    2019-06-25T00:43:50-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd
    2019-06-25T00:43:51-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ls
    2019-06-25T00:45:36-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-show-super -f /dev/vg1001/lv
    2019-06-25T00:45:57-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-show-super -f /dev/vg1000/lv
    2019-06-25T00:47:19-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ls
    2019-06-25T00:47:30-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat restore_share
    2019-06-25T00:47:39-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat check_root.sh q
    2019-06-25T00:47:40-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat check_root.sh
    2019-06-25T00:48:41-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat find_restore.sh
    2019-06-25T00:49:10-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree t 1 /dev/vg1000/lv
    2019-06-25T00:49:15-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 /dev/vg1000/lv
    2019-06-25T00:49:59-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 /dev/vg1000/lv  | grep ROOT_REF
    2019-06-25T00:50:23-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 /dev/vg1000/lv  | grep ROOT_REF -C5
    2019-06-25T00:50:34-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 /dev/vg1000/lv  | grep ROOT_REF -A10
    2019-06-25T00:53:35-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 /dev/vg1000/lv | awk '/item.*\(257\ ROOT_REF/{printf "%d ", $6 ;getline; print $9}'
    2019-06-25T00:54:15-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 201 /dev/vg1000/lv | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}'
    2019-06-25T00:54:23-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 201 /dev/vg1000/lv | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T00:54:26-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T00:54:40-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 201 /dev/vg1000/lv
    2019-06-25T00:57:35-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mv /tmp//btrfs-progs-4.x.txz ./
    2019-06-25T00:57:45-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 mkdir btrfs-tool
    2019-06-25T00:57:56-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 tar xf btrfs-progs-4.x.txz -C ./btrfs-tool/
    2019-06-25T00:57:59-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd btrfs-
    2019-06-25T00:58:02-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd btrfs-tool/
    2019-06-25T00:59:14-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 find ./ | grep btrfs-debug
    2019-06-25T00:59:49-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./usr/sbin/btrfs-debug-tree -t 201 /dev/vg1000/
    2019-06-25T00:59:52-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./usr/sbin/btrfs-debug-tree -t 201 /dev/vg1000/lv
    2019-06-25T01:00:17-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd usr/sbin/
    2019-06-25T01:00:19-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 1 $DEV | awk '/item.*\(257\ ROOT_REF/{printf "%d ", $6 ;getline; print $9}'
    2019-06-25T01:00:29-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 1 /dev/vg1000/lv | awk '/item.*\(257\ ROOT_REF/{printf "%d ", $6 ;getline; print $9}'
    2019-06-25T01:01:11-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 DEV=/dev/vg1000/lv
    2019-06-25T01:01:17-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 201 $DEV | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T01:01:19-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T01:01:26-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T01:01:28-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T01:01:41-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T01:01:43-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T01:05:00-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd -
    2019-06-25T01:05:02-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd -
    2019-06-25T01:05:44-07:00 <NAS NAME> -ash: SYSTEM:    Last message 'HISTORY: PID=3063 UI' repeated 1 times, suppressed by syslog-ng on <NAS NAME>
    2019-06-25T01:05:44-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 tar xf /tmp/btrfs-progs-4.x.txz -C /root/btrfs-tool/
    2019-06-25T01:05:50-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T01:05:53-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T01:07:50-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 tar xf /tmp/btrfs-progs-4.x.txz -C /root/btrfs-tool/
    2019-06-25T01:07:52-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV | awk '/item.*INFO/{printf "%s ", $6;getline;getline;print $2}' > aa
    2019-06-25T01:08:56-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cat aa
    2019-06-25T01:09:14-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV
    2019-06-25T01:09:17-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV  > aa
    2019-06-25T01:09:19-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim aa
    2019-06-25T01:09:47-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim aa
    2019-06-25T01:09:57-07:00 <NAS NAME> -ash: SYSTEM:    Last message 'HISTORY: PID=3063 UI' repeated 1 times, suppressed by syslog-ng on <NAS NAME>
    2019-06-25T01:09:57-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -b $DEV
    2019-06-25T01:10:04-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -b 10212392665088 $DEV
    2019-06-25T01:10:11-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -b $DEV
    2019-06-25T01:10:16-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ./btrfs-debug-tree -t 201 $DEV
    2019-06-25T01:10:27-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -b 5890641081019210 $DEV
    2019-06-25T01:11:44-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-find-root -o 814 -l 0 /dev/vg1/volume_X  > 257.roots
    2019-06-25T01:11:55-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-find-root -o 814 -l 0 /dev/vg1000/lv  > 814.roots
    2019-06-25T01:20:21-07:00 <NAS NAME> -sh: HISTORY: PID=10081 UID=1024 sudo -i
    2019-06-25T01:20:31-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cd btrfs-tool/usr/sbin/
    2019-06-25T01:20:34-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:20:43-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 htop
    2019-06-25T01:21:04-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 tail -f /var/log/messages
    2019-06-25T01:21:27-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cd
    2019-06-25T01:21:29-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 257.roots
    2019-06-25T01:27:04-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cd -
    2019-06-25T01:27:07-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:27:15-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 htop
    2019-06-25T01:27:24-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 cd
    2019-06-25T01:27:38-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 nphup btrfs-find-root -o 814 -l 0 /dev/vg1000/lv > 814.roots &
    2019-06-25T01:27:42-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 nohup btrfs-find-root -o 814 -l 0 /dev/vg1000/lv > 814.roots &
    2019-06-25T01:27:45-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cd -
    2019-06-25T01:27:48-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:27:59-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs
    2019-06-25T01:28:07-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:28:08-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:31:34-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs
    2019-06-25T01:31:37-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T01:35:37-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T01:35:40-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:42:22-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T01:42:24-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T01:59:41-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T01:59:43-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T02:11:04-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T02:11:05-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T02:33:47-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T02:33:50-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T02:37:58-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T02:37:59-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T02:50:31-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ps aux | grep btrfs-find
    2019-06-25T02:50:36-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 cat 814.roots
    2019-06-25T02:50:42-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 vim 814.roots
    2019-06-25T02:51:20-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 vim 814.roots
    2019-06-25T02:51:30-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 ls
    2019-06-25T02:52:14-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 source toolbox.sh
    2019-06-25T02:52:39-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0 parse_root_items 814.roots | while read bytenr
    2019-06-25T02:52:39-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0   do
    2019-06-25T02:52:39-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0      btrfs restore -i -D -f "$bytenr" /dev/vg1/volume_1 /mnt &>/dev/null
    2019-06-25T02:52:39-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0      if [ $? -eq 0 ]; then echo "$bytenr"; fi
    2019-06-25T02:52:40-07:00 <NAS NAME> -ash: HISTORY: PID=10086 UID=0   done
    2019-06-25T02:53:02-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 htop
    2019-06-25T02:53:12-07:00 <NAS NAME> -sh: HISTORY: PID=10081 UID=1024 sudo -i
    2019-06-25T02:53:26-07:00 <NAS NAME> -ash: HISTORY: PID=2502 UID=0 parse_root_items 814.roots | while read bytenr;   do      btrfs restore -i -D -f "$bytenr" /dev/vg1/volume_1 /mnt &>/dev/null;      if [ $? -eq 0 ]; then echo "$bytenr"; fi;   done
    2019-06-25T02:53:29-07:00 <NAS NAME> -ash: HISTORY: PID=2502 UID=0 source toolbox.sh
    2019-06-25T02:53:30-07:00 <NAS NAME> -ash: HISTORY: PID=2502 UID=0 parse_root_items 814.roots | while read bytenr;   do      btrfs restore -i -D -f "$bytenr" /dev/vg1/volume_1 /mnt &>/dev/null;      if [ $? -eq 0 ]; then echo "$bytenr"; fi;   done
    2019-06-25T02:53:50-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 htop
    2019-06-25T02:56:22-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 vim 257.roots
    2019-06-25T02:57:37-07:00 <NAS NAME> -ash: HISTORY: PID=2502 UID=0 parse_root_items 814.roots | while read bytenr;   do      btrfs restore -i -D -f "$bytenr" /dev/vg1000/lv /mnt &>/dev/null;      if [ $? -eq 0 ]; then echo "$bytenr"; fi;   done
    2019-06-25T03:04:40-07:00 <NAS NAME> -sh: HISTORY: PID=10081 UID=1024 synologconvert /var/log/synolog/.SYNOSYS > synosys
    2019-06-25T03:04:57-07:00 <NAS NAME> -sh: HISTORY: PID=10081 UID=1024 sudo -i
    2019-06-25T03:05:15-07:00 <NAS NAME> -ash: HISTORY: PID=27248 UID=0 synynologconvert /var/log/synolog/.SYNOSYSDB > synosys
    2019-06-25T03:05:22-07:00 <NAS NAME> -ash: HISTORY: PID=27248 UID=0 synnologconvert /var/log/synolog/.SYNOSYSDB > synosys
    2019-06-25T03:05:26-07:00 <NAS NAME> -ash: HISTORY: PID=27248 UID=0 synologconvert /var/log/synolog/.SYNOSYSDB > synosys
    2019-06-25T03:05:28-07:00 <NAS NAME> -ash: HISTORY: PID=27248 UID=0 vim synosys
    2019-06-25T03:07:12-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 btrfs-debug-tree -t 1 $DEV | awk '/item.*\(257\ ROOT_REF/{printf "%d ", $6 ;getline; print $9}'
    2019-06-25T03:09:46-07:00 <NAS NAME> -ash: HISTORY: PID=3063 UID=0 ls
    2019-06-26T19:16:41-07:00 <NAS NAME> -sh: HISTORY: PID=27431 UID=1024 sudo -i
    2019-06-26T19:18:04-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 cd /root
    2019-06-26T19:18:05-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ll
    2019-06-26T19:18:23-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 df -h
    2019-06-26T19:21:05-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 nohup btrfs-find-root -o 814 -l 0 /dev/vg1000/lv  > 814.roots &
    2019-06-26T19:21:10-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ll
    2019-06-26T19:23:13-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 nohup btrfs-find-root -o 260 -l 0 /dev/vg1000/lv  > 260.roots &
    2019-06-26T19:23:16-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ll
    2019-06-26T19:23:26-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 cat 260.roots
    2019-06-26T19:24:39-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ll
    2019-06-26T19:24:45-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ps aux |grep btrfs
    2019-06-26T19:25:08-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 cat /var/log/bash_history.log
    2019-06-26T19:36:51-07:00 <NAS NAME> -ash: HISTORY: PID=27437 UID=0 ll
    2019-06-27T19:21:54-07:00 <NAS NAME> -sh: HISTORY: PID=23029 UID=1024 sudo -i
    2019-06-27T19:21:57-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 df
    2019-06-27T19:22:01-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 cd /root
    2019-06-27T19:22:02-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:22:13-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 cat 260
    2019-06-27T19:22:16-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 cat 260.roots
    2019-06-27T19:22:40-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:23:12-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:23:16-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 df -h
    2019-06-27T19:23:31-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 cd /volumeUSB1/usbshare/
    2019-06-27T19:23:32-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:23:54-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 cd /root
    2019-06-27T19:23:55-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:26:22-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 nohup bash restore_btrfs_from_roots.sh /root/814.roots 0 /dev/vg1000/lv /volumeUSB1/usbshare/Volume3_Backups &
    2019-06-27T19:26:25-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 ll
    2019-06-27T19:27:12-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 nohup bash restore_btrfs_from_roots.sh /root/260.roots 0 /dev/vg1000/lv /volume2/Volume3_Media/ &
    2019-06-27T19:27:18-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 top
    2019-06-27T19:27:29-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 df -h
    2019-06-27T19:29:15-07:00 <NAS NAME> -ash: HISTORY: PID=23124 UID=0 df -h
    2019-06-30T18:25:18-07:00 <NAS NAME> -sh: HISTORY: PID=27597 UID=1024 sudo -i
    2019-06-30T18:25:20-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 df
    2019-06-30T18:25:25-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 df -h
    2019-06-30T18:25:32-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 cd /volume2
    2019-06-30T18:25:33-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 ll
    2019-06-30T18:25:38-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 cd Volume3_Media/
    2019-06-30T18:25:39-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 ll
    2019-06-30T18:25:42-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 cd ..
    2019-06-30T18:25:50-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 ps aux| grep btrfs
    2019-06-30T18:26:19-07:00 <NAS NAME> -ash: HISTORY: PID=27679 UID=0 df -h
    2019-06-30T21:55:03-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 history
    2019-06-30T21:55:44-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 cd /var/log
    2019-06-30T21:55:45-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 ls
    2019-06-30T21:56:09-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 cat syslog.log
    2019-06-30T21:56:13-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 sudo cat syslog.log
    2019-06-30T21:57:21-07:00 <NAS NAME> -sh: HISTORY: PID=11779 UID=1024 sudo cat bash_history.log

     

    DSM 6.2 Loader

    in Loaders

    Posted

    1 hour ago, martva said:

    I'm trying to wrap my head around this loader.

     

    I'm using the following setup:

    - DSM version prior update: DSM 6.1.7-15284 UPDATE2

    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - HP Microserver N54L 

    - Additional comments: I have an extra nic installed: Intel Pro 1000 PT PCI Express Gigabit NIC

     

    Now according to the start post, it says the system will panic when running DSM 6.2.1+ is not having a e1000e NIC.  I've also read that this ONLY APPLIES to an ESXi setup.  So I can safely assume that the when upgrading the newer 6.2 DSM I will not run into any problems with the intel pro nic?

     

    And is this still valid:

    Builtin card will work with 1.03b loader and DSM 6.2.

    It WILL NOT work with DSM 6.2.1 and 6.2.2

     

    The 1.03b loader seems to panic whenever an e1000e compatible card is not in the system.  It doesn't matter whether it's virtual or physical.  Therefore many folks have added Intel PCI NICs and disable onboard or other NICs to HP baremetal systems to get it to work.  There are many, many posts about this.  I don't think your PT card uses the e1000e driver, but that is pretty easy to verify. Check the DS3615 6.2 driver list to be sure (see my signature for links to the driver spreadsheets).

     

    I'm not sure if the 1000PT card works fine on the 1.04b loader.  1.04b does seem more functional with embedded drivers - however, many that are in the DS3615 PAT file are not in the DS918 PAT file. Again, check the DS918 6.2 driver list to be sure.

     

    1 hour ago, martva said:

    Is it also possible to do a cross-upgrade from ds3615xs to ds918+? Or is a clean install adviced here. Thank you in advance.

     

    Yes, you can switch DSM platforms, you are just installing a new loader which results in a system migration.  No different than moving disks from physical Diskstation to Diskstation.

    • Like 1

    Volume degraded

    in DSM 6.x

    Posted

    You probably have a power or SATA cable problem with the drive that keeps failing, it appears to be physically disconnected from the system momentarily.  It could be a drive problem too but I'd check cabling first.

     

    You are rolling the dice with your recovery method.  Any degraded array needs to be treated very carefully.  You have probably already lost some data given the crashed status.

     

    DSM tracks all disks by model and serial number.  Once it decides a disk itself has crashed irrevocably, it will flag it in /var/log/disk_overview.xml.  You can edit the file yourself and delete the tag for that particular disk.  Reboot and DSM will regenerate it as a new drive with no flags.

     

    9th Gen Intel CPU

    in The Noob Lounge

    Posted

    I'm glad you found something that worked for you.  The comment about ESXi and RAID is strange.  ESXi does support a software RAID in the virtualization layer, but the whole point of running DSM is not to do that and allow DSM to provide the software RAID anyway.

     

    Many folks have installed virtualized DSM with KVM under a generic Linux installation; it would seem that you've done the equivalent but using UNRAID as your Linux environment.

     

    9th Gen Intel CPU

    in The Noob Lounge

    Posted · Edited by flyride

    Just for others that search and find this thread.  9th Gen Intel CPU's (and really all Haswell and later Intel CPU's) work fine with XPEnology.

     

    OP's problem is with his particular motherboard NIC being too new for the driver and no effective way to add a driver with the latest DSM versions.

    One solution would have been to add a compatible add-in Intel NIC as many have done.  Virtualization also would solve the NIC compatibility problem.

    Stupid question: Going from 6.1 loader to 6.2

    in Answered Questions

    Posted

    @Jastsai, unless someone has EXACTLY the hardware you do (i.e. you can find it in the DSM upgrade threads), you have to make the determination for yourself.  Maybe try this:

     

    1. Set aside your old loader and disks, and build up a new loader on a new USB on your AMD platform, with a spare drive.  Install DSM 6.1.x like you already have running.

    2. Install 1.03b on the new USB and boot it.  It should prompt you to migrate.  Once done, verify that it boots into DSM ok and your test configuration is intact.  If so, congrats, your hardware works with the new loader on DSM 6.1

    3. Now use Control Panel to try and upgrade to the latest 6.2, or download the 6.2 PAT file of your preference and install a prior version.

    4. If it works and boots back into DSM, congratulations, your hardware works with DSM 6.2.x and you should expect to have the same result with your production system.

     

    To upgrade your production system (or return to the 6.1 version of your production system) just replace the test USB and disk with the ones you removed.  Regardless, it would be wise to have a backup of your data prior to upgrade.

     

    If the above doesn't work at some step, you can bring your results back to the forum and folks will be more than willing to help.

    Stupid question: Going from 6.1 loader to 6.2

    in Answered Questions

    Posted · Edited by flyride

    Hmm, calling people out as arrogant isn't the way to curry favor for help.  Anyone you could possibly reach with that comment has spent countless hours trying to help many, many people such as yourself. Based on your questions, both you and OP present with little or no evidence of effort to understand DSM and how the XPenology loader works.  And only slightly below the veneer of that request is a challenge to be assured you won't lose data, which you cannot possibly get from someone on an online forum.  It's your responsibility, nobody else's, to make sure your data is safe.

     

    Let's spell it out: All the loader does it let us boot DSM on non-Synology hardware. Nothing more, nothing less.  Any other behavior is attributable to DSM, Synology's operating system.  Yes, it's based on Linux, but that's not a limiting factor.  Many XPenology users never launch the shell, nor do they need to. If you want to be successful running DSM on XPenology, it will be in your interest to know something about DSM.  There are many, many places to learn about how to do things with DSM, not the least of which are Synology's forums.

     

    So here are a couple of key points that ARE, literally, embedded in the tutorials.  Hopefully they will help steer you in the right direction.

    • Upgrading DSM from 6.1 to 6.2 is a function of DSM.  Not the loader.
    • If you want to upgrade from 6.1 to 6.2, you'll need to install a 6.2 compatible version of the loader (either 1.03b or 1.04b), otherwise DSM will crash once upgraded
    • The 6.2 compatible loader must also work with your hardware, which isn't a guarantee even if you were successfully running DSM 6.1.
    • Installing a new loader is analogous to moving your disks to a new Synology Diskstation -  DSM will prompt for migration or upgrade.
    • Migrating and/or upgrading DSM isn't inherently a data-destroying process, if done properly.  Again, this is a DSM behavior
    • Any upgrade or migration operation can fail for many reasons, including loader incompatibility (ref hardware issues above) or user mistake.
    • Those who attempt an upgrade or migration operation without a data backup plan are, bluntly, foolish

    To you, OP and anyone else who wants to upgrade - it's very much in your interest to build up a test environment and validate your upgrade plan each and every time before subjecting your production system and data to risk.  This is repeated again and again in the tutorials.  It is one of the benefits of a virtualized (i.e. ESXi) environment - it makes it very easy to test without extra hardware.

     

    Good luck to you and OP.  Your linarrogant friends online will be waiting to help if you run into trouble.

     

    • Like 1

    Cloning Synology disk to new (bigger) disk..

    in Answered Questions

    Posted

    Your limitations on disk bays, and your procedure is making it much harder than it needs to be.

    Synology will automatically expand your volumes when you grow in a "normal" fashion (i.e. mirror a larger HDD, etc).  Your idea of the RAID1 migration would have accomplished this.

     

    The only way to expand now is to manually edit via command line.  There are a million different permutations between RAID/LVM/non-LVM/etc that Synology's scripts handle without fuss.  Not so easy to address all those permutations manually... the solution is probably pretty simple, but be sure you know what you have before just blindly executing commands that edit your partition and filesystems.

    See: https://xpenology.com/forum/topic/14091-esxi-unable-to-expand-syno-volume-even-after-disk-space-increased/

    DSM 6.2 Loader

    in Loaders

    Posted

    Legacy boot and MBR are two different things....

     

    MBR (master boot record) is a partition type, and should only be required if you are using really old hardware that cannot support a GPT partition.

     

    Legacy boot is the BIOS boot model prior to the current UEFI implementation.

     

    Gigabyte J3455N-D3H with Jun's Loader v1.04b DS918+

    in DSM 6.x

    Posted · Edited by flyride

    13 hours ago, real3x said:

    I finally made the jump for the update from 6.2.1-23824 Update 6 to 6.2.2-24922 Update 2, i only use a custom extra.lzma without i915 drivers, and everything work nicely, onboard Lan

     

    Tested functional with my J4105-ITX, except I did not check transcode which I don't use.  Well done!

    I want to build a NAS

    in The Noob Lounge

    Posted · Edited by flyride

    1 hour ago, adicontakt said:

    I don"t have enough time to complete all the settings , I am very busy at work and at home

    On ‎7‎/‎27‎/‎2019 at 2:10 AM, adicontakt said:

    No one? 

     

    I realize that there are difficulties with language translation and subtleties in meaning here, but this is audacious.  You don't have time to follow through but expect other folks to volunteer their time to help, and are instantly critical when they don't drop everything to research your own obscure hardware for you inside of 24 hours?

     

    A little courtesy and humility goes a long way.

×
×
  • Create New...