It seems that it would be safer to have the DAS array attached permanently to your NAS and access it over the network. That is if your NAS has eSATA port.
That way it would be permanently attached like internal drives and that should avoid these type of synchronization errors - Especially when you use it as RAID0. RAID arrays, especially in striping configuration, do not like to be detached or put to sleep without proper sync and umount. If attaching it permanently to NAS is not an option, autofs with reasonable timeout avoiding the DAS power saving mode, instead of mount in fstab, would probably help too. Hope it helps, Tomas On Sun, 2018-10-14 at 18:26 -0700, John Jason Jordan wrote: > On Sun, 14 Oct 2018 13:45:14 -0700 (PDT) > Rich Shepard <rshep...@appl-ecosys.com> dijo: > > > On Sun, 14 Oct 2018, Ben Koenig wrote: > > > > > Please copy/paste the following command into your terminal and > > > post > > > the output here so that we can offer sensible advice. > > > > > > ls -l /dev/sd* > > > > Ben, > > > > Might lsblk provide John with the same information? > > It does, and I already used it last night. It found /dev/sdc, but not > the partition /dev/sdc1. Gparted had a utility to search a disk for a > filesystem, which I left running overnight. It found nothing, so this > morning I bit the bullet, recreated and formatted the partition, and > then started copying everything from the backup Synology NAS. I > started > the copying at about 9am, and it is now working on letter 'O.' I hope > to be done before bedtime tonight. > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
