Syntax Question on 'rsyncd.conf' on Windows

[Tim Evans via rsync]

Cygwin distribution of rsync for Windows contains an example rsyncd.conf,
excerpt below:

[cDrive]
path = /cygdrive/c/
comment = Entire C Drive

Having trouble setting up a second Windows physical drive.  Is the
"cygdrive" designation a reference to the full system root, so that  syntax
for Windows Drive "E:" would therefore be referenced "/cygdrive/e/"?

Or is there a different syntax for non-C: drive?

Thanks.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsync: [generator] failed to set permissions : Operation not supported (95)

[Mario Marietto via rsync]

root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# tune2fs
-l  /home/ziomario/Scrivania/antmicro/aosp_images/system-rw.img
tune2fs 1.45.6 (20-Mar-2020)

Filesystem volume name:   /
Last mounted on:
 /home/ziomario/Scrivania/antmicro/aosp_images/system-rw
Filesystem UUID:  b7ee4a86-92bc-4530-a645-7e825127fb90
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent 64bit flex_bg sparse_super large_file
huge_file dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options:user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  196608
Block count:  786432
Reserved block count: 39321
Free blocks:  755396
Free inodes:  196597
First block:  0
Block size:   4096
Fragment size:4096
Group descriptor size:64
Reserved GDT blocks:  383
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
Flex block group size:16
Filesystem created:   Tue Apr  6 14:18:55 2021
Last mount time:  Tue Apr  6 14:19:15 2021
Last write time:  Tue Apr  6 14:19:15 2021
Mount count:  1
Maximum mount count:  -1
Last checked: Tue Apr  6 14:18:55 2021
Check interval:   0 ()
Lifetime writes:  1733 kB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
Default directory hash:   half_md4
Directory Hash Seed:  be3ec3f4-13ef-48f7-87bd-0b6e50e80127
Journal backup:   inode blocks



Il giorno mar 6 apr 2021 alle ore 16:34 Mario Marietto <
marietto2...@gmail.com> ha scritto:

> root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images#
> tune2fs -l /dev/sda1
>
> tune2fs 1.45.6 (20-Mar-2020)
> Filesystem volume name:   
> Last mounted on:  /
> Filesystem UUID:  84d024e0-c8c7-42c0-ad3e-c3e0c1cacdb7
> Filesystem magic number:  0xEF53
> Filesystem revision #:1 (dynamic)
> Filesystem features:  has_journal ext_attr resize_inode dir_index
> filetype needs_recovery extent 64bit flex_bg sparse_super large_file
> huge_file dir_nlink extra_isize m
> etadata_csum
> Filesystem flags: signed_directory_hash
> Default mount options:user_xattr acl
> Filesystem state: clean
> Errors behavior:  Continue
> Filesystem OS type:   Linux
> Inode count:  30531584
> Block count:  122095703
> Reserved block count: 6104784
> Free blocks:  16457913
> Free inodes:  27534246
> First block:  0
> Block size:   4096
> Fragment size:4096
> Group descriptor size:64
> Reserved GDT blocks:  1024
> Blocks per group: 32768
> Fragments per group:  32768
> Inodes per group: 8192
> Inode blocks per group:   512
> Flex block group size:16
> Filesystem created:   Mon Aug  3 22:23:38 2020
> Last mount time:  Tue Apr  6 10:46:45 2021
> Last write time:  Tue Apr  6 10:46:44 2021
> Mount count:  173
> Maximum mount count:  -1
> Last checked: Sun Feb 28 12:33:46 2021
> Check interval:   0 ()
> Lifetime writes:  34 TB
> Reserved blocks uid:  0 (user root)
> Reserved blocks gid:  0 (group root)
> First inode:  11
> Inode size:   256
> Required extra isize: 32
> Desired extra isize:  32
> Journal inode:8
> First orphan inode:   22414454
> Default directory hash:   half_md4
> Directory Hash Seed:  3ff09b4a-bf6b-41ac-844d-310aebf87fbf
> Journal backup:   inode blocks
> Checksum type:crc32c
> Checksum: 0xf4add38b
>
>
>
> Il giorno mar 6 apr 2021 alle ore 16:11 Kevin Korb via rsync <
> rsync@lists.samba.org> ha scritto:
>
>> Those aren't really rsync errors they are just rsync telling you what
>> the kernel told it.  The only thing I see wrong in your paste is that
>> you didn't use a trailing / on the source+target.  Those do mean
>> something to rsync.  The only thing I see wrong in the instructions is
>> the use of dd to make a file of a specific size.  The truncate command
>> does that much better.
>>
>> Anyway, check the mount options on the file system (use the mount
>> command it will show them) and the options on the filesystem itself with
>> tune2fs -l.  My guess is that either ACLs or XATTRs are not enabled and
>> they probably are in use since the instructions told you to tell rsync
>> to copy those.  You can also try running rsync without the -A and -X to
>> confirm.
>>
>> On 4/6/21 9:50 AM, Mario 

Re: rsync: [generator] failed to set permissions : Operation not supported (95)

[Mario Marietto via rsync]

root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# tune2fs
-l /dev/sda1

tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name:   
Last mounted on:  /
Filesystem UUID:  84d024e0-c8c7-42c0-ad3e-c3e0c1cacdb7
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent 64bit flex_bg sparse_super large_file
huge_file dir_nlink extra_isize m
etadata_csum
Filesystem flags: signed_directory_hash
Default mount options:user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  30531584
Block count:  122095703
Reserved block count: 6104784
Free blocks:  16457913
Free inodes:  27534246
First block:  0
Block size:   4096
Fragment size:4096
Group descriptor size:64
Reserved GDT blocks:  1024
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
Flex block group size:16
Filesystem created:   Mon Aug  3 22:23:38 2020
Last mount time:  Tue Apr  6 10:46:45 2021
Last write time:  Tue Apr  6 10:46:44 2021
Mount count:  173
Maximum mount count:  -1
Last checked: Sun Feb 28 12:33:46 2021
Check interval:   0 ()
Lifetime writes:  34 TB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 32
Desired extra isize:  32
Journal inode:8
First orphan inode:   22414454
Default directory hash:   half_md4
Directory Hash Seed:  3ff09b4a-bf6b-41ac-844d-310aebf87fbf
Journal backup:   inode blocks
Checksum type:crc32c
Checksum: 0xf4add38b



Il giorno mar 6 apr 2021 alle ore 16:11 Kevin Korb via rsync <
rsync@lists.samba.org> ha scritto:

> Those aren't really rsync errors they are just rsync telling you what
> the kernel told it.  The only thing I see wrong in your paste is that
> you didn't use a trailing / on the source+target.  Those do mean
> something to rsync.  The only thing I see wrong in the instructions is
> the use of dd to make a file of a specific size.  The truncate command
> does that much better.
>
> Anyway, check the mount options on the file system (use the mount
> command it will show them) and the options on the filesystem itself with
> tune2fs -l.  My guess is that either ACLs or XATTRs are not enabled and
> they probably are in use since the instructions told you to tell rsync
> to copy those.  You can also try running rsync without the -A and -X to
> confirm.
>
> On 4/6/21 9:50 AM, Mario Marietto via rsync wrote:
> > Hello.
> >
> > I want to virtualize correctly Android 10 on top of my Jetson nano
> > (arm64) using qemu and kvm on ubuntu 18.04. This is the tutorial that
> > I'm following :
> >
> > https://github.com/antmicro/kvm-aosp-jetson-nano
> > 
> >
> > everything went good until this command :
> >
> > |sudo rsync -avxHAX system-r{o,w}/
> >
> > |
> >
> > |something is not good because I get a lot of errors when I transfer the
> > files and permissions from the source to the destination path (both are
> > on the same disk and on the same ext4 partition. You can see the full
> > log with the errors here :
> >
> > |
> >
> > https://pastebin.ubuntu.com/p/W9GjPCt8G4/
> > 
> >
> > the consequence of these errors is that when I try to emulate android
> > with qemu like this :
> >
> > |qemu-system-aarch64 \ -enable-kvm \ -smp 4 \ -m 2048 \ -cpu host \ -M
> > virt \ -device virtio-gpu-pci \ -device usb-ehci \ -device usb-kbd \
> > -device virtio-tablet-pci \ -usb \ -serial stdio \ -display sdl,gl=on \
> > -kernel aosp/Image \ -initrd aosp/ramdisk.img \ -drive
> > index=0,if=none,id=system,file=aosp/system.img \ -device
> > virtio-blk-pci,drive=system \ -drive
> > index=1,if=none,id=vendor,file=aosp/vendor.img \ -device
> > virtio-blk-pci,drive=vendor \ -drive
> > index=2,if=none,id=userdata,file=aosp/userdata.img \ -device
> > virtio-blk-pci,drive=userdata \ -full-screen \ -append
> > "console=ttyAMA0,38400 earlycon=pl011,0x0900 drm.debug=0x0 rootwait
> > rootdelay=5 androidboot.hardware=ranchu androidboot.selinux=permissive
> > security=selinux selinux=1 androidboot.qemu.hw.mainkeys=0
> > androidboot.lcd.density=160" |
> >
> >
> > this is the error that I get :
> >
> > [ 2.532754] init: init first stage started!
> > [ 2.535936] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab
> > from dt
> > [ 2.540632] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
> > default fstab
> > [ 2.546246] init: Failed to fstab for first stage mount
> > [ 2.549616] init: Using Android DT directory
> > 

Re: rsync: [generator] failed to set permissions : Operation not supported (95)

[Mario Marietto via rsync]

root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# mount

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,noexec,relatime,size=16338980k,nr_inodes=4084745,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=3274048k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs
(ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/pids type cgroup
(rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup
(rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/devices type cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=829)

mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs
(rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/var/lib/snapd/snaps/anbox_210.snap on /snap/anbox/210 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/dev/nvme0n1p1 on /boot/efi type vfat
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

/var/lib/snapd/snaps/core_10859.snap on /snap/core/10859 type squashfs
(ro,nodev,relatime,x-gdu.hide)
fusectl on /sys/fs/fuse/connections type fusectl
(rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs
(rw,nosuid,nodev,noexec,relatime)
/var/lib/snapd/snaps/core18_1988.snap on /snap/core18/1988 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_10908.snap on /snap/core/10908 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core20_975.snap on /snap/core20/975 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core20_904.snap on /snap/core20/904 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-34-1804_66.snap on /snap/gnome-3-34-1804/66
type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sdc1 on /media/ziomario/isoarm type ext4 (rw,noatime)
/var/lib/snapd/snaps/gnome-3-28-1804_145.snap on /snap/gnome-3-28-1804/145
type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snap-store_481.snap on /snap/snap-store/481 type
squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snap-store_518.snap on /snap/snap-store/518 type
squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-34-1804_60.snap on /snap/gnome-3-34-1804/60
type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk-common-themes_1514.snap on
/snap/gtk-common-themes/1514 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk-common-themes_1506.snap on
/snap/gtk-common-themes/1506 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snapd_11107.snap on /snap/snapd/11107 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/dev/sdg1 on /media/ziomario/Android type ext4 (rw,noatime)
/var/lib/snapd/snaps/whatsdesk_20.snap on /snap/whatsdesk/20 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snapd_11402.snap on /snap/snapd/11402 type squashfs
(ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/telegram-desktop_2551.snap on
/snap/telegram-desktop/2551 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core18_1997.snap on 

Re: rsync: [generator] failed to set permissions : Operation not supported (95)

[Kevin Korb via rsync]

Those aren't really rsync errors they are just rsync telling you what
the kernel told it.  The only thing I see wrong in your paste is that
you didn't use a trailing / on the source+target.  Those do mean
something to rsync.  The only thing I see wrong in the instructions is
the use of dd to make a file of a specific size.  The truncate command
does that much better.

Anyway, check the mount options on the file system (use the mount
command it will show them) and the options on the filesystem itself with
tune2fs -l.  My guess is that either ACLs or XATTRs are not enabled and
they probably are in use since the instructions told you to tell rsync
to copy those.  You can also try running rsync without the -A and -X to
confirm.

On 4/6/21 9:50 AM, Mario Marietto via rsync wrote:
> Hello.
> 
> I want to virtualize correctly Android 10 on top of my Jetson nano
> (arm64) using qemu and kvm on ubuntu 18.04. This is the tutorial that
> I'm following :
> 
> https://github.com/antmicro/kvm-aosp-jetson-nano
> 
> 
> everything went good until this command :
> 
> |sudo rsync -avxHAX system-r{o,w}/
> 
> |
> 
> |something is not good because I get a lot of errors when I transfer the
> files and permissions from the source to the destination path (both are
> on the same disk and on the same ext4 partition. You can see the full
> log with the errors here :
> 
> |
> 
> https://pastebin.ubuntu.com/p/W9GjPCt8G4/
> 
> 
> the consequence of these errors is that when I try to emulate android
> with qemu like this :
> 
> |qemu-system-aarch64 \ -enable-kvm \ -smp 4 \ -m 2048 \ -cpu host \ -M
> virt \ -device virtio-gpu-pci \ -device usb-ehci \ -device usb-kbd \
> -device virtio-tablet-pci \ -usb \ -serial stdio \ -display sdl,gl=on \
> -kernel aosp/Image \ -initrd aosp/ramdisk.img \ -drive
> index=0,if=none,id=system,file=aosp/system.img \ -device
> virtio-blk-pci,drive=system \ -drive
> index=1,if=none,id=vendor,file=aosp/vendor.img \ -device
> virtio-blk-pci,drive=vendor \ -drive
> index=2,if=none,id=userdata,file=aosp/userdata.img \ -device
> virtio-blk-pci,drive=userdata \ -full-screen \ -append
> "console=ttyAMA0,38400 earlycon=pl011,0x0900 drm.debug=0x0 rootwait
> rootdelay=5 androidboot.hardware=ranchu androidboot.selinux=permissive
> security=selinux selinux=1 androidboot.qemu.hw.mainkeys=0
> androidboot.lcd.density=160" |
> 
> 
> this is the error that I get :
> 
> [ 2.532754] init: init first stage started!
> [ 2.535936] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab
> from dt
> [ 2.540632] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
> default fstab
> [ 2.546246] init: Failed to fstab for first stage mount
> [ 2.549616] init: Using Android DT directory
> /proc/device-tree/firmware/android/
> [ 2.555116] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
> default fstab
> [ 2.560762] init: First stage mount skipped (missing/incompatible/empty
> fstab in device tree)
> [ 2.566906] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
> [ 2.571227] init: execv("/system/bin/init") failed: No such file or
> directory
> [ 2.593768] init: #00 pc 000e90a0 /init
> [ 2.599958] reboot: Restarting system with command 'bootloader'
> 
> -- 
> Mario.
> 

-- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb  Phone:(407) 252-6853
Systems Administrator   Internet:
FutureQuest, Inc.   ke...@futurequest.net  (work)
Orlando, Floridak...@sanitarium.net (personal)
Web page:   https://sanitarium.net/
PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

rsync: [generator] failed to set permissions : Operation not supported (95)

[Mario Marietto via rsync]

Hello.

I want to virtualize correctly Android 10 on top of my Jetson nano (arm64)
using qemu and kvm on ubuntu 18.04. This is the tutorial that I'm following
:

https://github.com/antmicro/kvm-aosp-jetson-nano

everything went good until this command :

sudo rsync -avxHAX system-r{o,w}/

something is not good because I get a lot of errors when I transfer
the files and permissions from the source to the destination path
(both are on the same disk and on the same ext4 partition. You can see
the full log with the errors here :

https://pastebin.ubuntu.com/p/W9GjPCt8G4/

the consequence of these errors is that when I try to emulate android with
qemu like this :

qemu-system-aarch64 \
-enable-kvm \
-smp 4 \
-m 2048 \
-cpu host \
-M virt \
-device virtio-gpu-pci \
-device usb-ehci \
-device usb-kbd \
-device virtio-tablet-pci \
-usb \
-serial stdio \
-display sdl,gl=on \
-kernel aosp/Image \
-initrd aosp/ramdisk.img \
-drive index=0,if=none,id=system,file=aosp/system.img \
-device virtio-blk-pci,drive=system \
-drive index=1,if=none,id=vendor,file=aosp/vendor.img \
-device virtio-blk-pci,drive=vendor \
-drive index=2,if=none,id=userdata,file=aosp/userdata.img \
-device virtio-blk-pci,drive=userdata \
-full-screen \
-append "console=ttyAMA0,38400 earlycon=pl011,0x0900
drm.debug=0x0 rootwait rootdelay=5 androidboot.hardware=ranchu
androidboot.selinux=permissive security=selinux selinux=1
androidboot.qemu.hw.mainkeys=0 androidboot.lcd.density=160"


this is the error that I get :

[ 2.532754] init: init first stage started!
[ 2.535936] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab from
dt
[ 2.540632] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
default fstab
[ 2.546246] init: Failed to fstab for first stage mount
[ 2.549616] init: Using Android DT directory
/proc/device-tree/firmware/android/
[ 2.555116] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
default fstab
[ 2.560762] init: First stage mount skipped (missing/incompatible/empty
fstab in device tree)
[ 2.566906] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
[ 2.571227] init: execv("/system/bin/init") failed: No such file or
directory
[ 2.593768] init: #00 pc 000e90a0 /init
[ 2.599958] reboot: Restarting system with command 'bootloader'

-- 
Mario.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html