On Thu April 13 2023 01:52:30 Michael J. Manley via tde-devels wrote:
Alright everyone, got it back up and running.
So not fun having to deal with bad drives! Luckily it was just mirror content so it wasn't a huge job to restore the containers :D
Hi Michael,
Sorry for the delay in getting back to you. I've been on the road.
Looks like the mirror has a permission problem with rsync:
$ rsync mirror.nasutek.com::trinity/ @ERROR: chroot failed rsync error: error starting client-server protocol (code 5) at main.c(1817) [Receiver=3.2.3] $
Thanks,
--Mike