| 1 |
On Sunday, 17 March 2019 17:05:58 GMT Grant Taylor wrote: |
| 2 |
> On 3/17/19 10:48 AM, Peter Humphrey wrote: |
| 3 |
> > Hello list, |
| 4 |
> |
| 5 |
> Hi, |
| 6 |
> |
| 7 |
> > My little Atom box has a small rescue system which I boot once a week |
| 8 |
> > to back up the main system. The backup script is a simple list of bash |
| 9 |
> > commands to mount partitions and tar them to a USB disk. |
| 10 |
> |
| 11 |
> Please share a copy of the backup script. |
| 12 |
> |
| 13 |
> > While the backup is running I run another script to clean up after |
| 14 |
> > any recent update, which involves removing surplus packages, running |
| 15 |
> > eclean etc. |
| 16 |
> |
| 17 |
> Please share a copy of your cleanup script. |
| 18 |
> |
| 19 |
> > But! At least once per session I have to remount the root filesystem read- |
| 20 |
> > write because something, presumably tar, has caused it to be remounted |
| 21 |
> > read- only. |
| 22 |
> |
| 23 |
> "tar" itself shouldn't alter mounts at all. |
| 24 |
> |
| 25 |
> It is possible that there could be a mount option that causes the file |
| 26 |
> system to be remounted read-only if there is a problem accessing the |
| 27 |
> file system. |
| 28 |
> |
| 29 |
> > Where do I start tracking this down? This behaviour was a factor in |
| 30 |
> > my suspecting an SSD failure, but I've replaced that and still get the |
| 31 |
> > same remounting. |
| 32 |
> |
| 33 |
> But such remounting is not likely on a new SSD. |
| 34 |
|
| 35 |
Yes, it would be unlikely. |
| 36 |
|
| 37 |
|
| 38 |
> I'd need to see the scripts to even hazard a guess as to what might be |
| 39 |
> happening. |
| 40 |
|
| 41 |
Also, in your previous thread you mentioned you were about to run memtest to |
| 42 |
discard the possibility of a faulty RAM. Did you run it overnight and what |
| 43 |
did you get? |
| 44 |
|
| 45 |
-- |
| 46 |
Regards, |
| 47 |
Mick |
Archives