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 > <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/ > <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,0x09000000 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 00000000000e90a0 /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, Florida k...@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
