Re: [Dorset] Filesystem in a LUKS volume unmounts randomly on Raspberry Pi
On 09/09/2020 14:42, Terry Coles wrote: > On Wednesday, 9 September 2020 14:15:08 BST Hamish McIntyre-Bhatty wrote: >> Perhaps this explains some of our issues with the network in previous >> years at the model town, Terry? It might be worth me making a note on >> the forum about it. I'm currently trying a different overlay which is >> supposed to fix the problem at the expense of a little bit of USB >> throughput. > It's certainly worth thinking about. Still having issues with my storage unmounting (this time nothing in dmesg at all), but network seems better so far. Haven't tested throughput. Any thoughts about diagnosing storage unmounting with no explanation is dmesg? This seems rather strange to me. I'm using a powered hub too now, in case I forgot to mention. Other volumes on the same external disk stay mounted. Hamish signature.asc Description: OpenPGP digital signature -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Filesystem in a LUKS volume unmounts randomly on Raspberry Pi
On Wednesday, 9 September 2020 14:15:08 BST Hamish McIntyre-Bhatty wrote: > Perhaps this explains some of our issues with the network in previous > years at the model town, Terry? It might be worth me making a note on > the forum about it. I'm currently trying a different overlay which is > supposed to fix the problem at the expense of a little bit of USB > throughput. It's certainly worth thinking about. -- Terry Coles -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] How to Cancel Existing systemd.timer(5) OnCalendar Values.
On 09/09/2020 12:15, Keith Edmunds wrote: > On Wed, 9 Sep 2020 09:44:44 +0100, hamis...@live.co.uk said: > >> so has anyone experienced cron jobs sporadically (kind of randomly) not >> running when they're meant to? > No, never (and I've been using Linux since the early 90s, and UNIX before > that). > > Set up your cron jobs so that the command is: > > [...] your-command 2>&1 | /usr/bin/logger -t 'my cronjob' > > Then take a look in your syslog files after the cron job has apparently > not run. > > Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ > Yeah, that's why I'm asking - cron sounds bulletproof by a lot of what I've heard. Cheers, I'll do that. At the moment I'm debugging something else wrong with the pi, but I'll give this a shot once that's done. Hamish signature.asc Description: OpenPGP digital signature -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Filesystem in a LUKS volume unmounts randomly on Raspberry Pi
On 09/09/2020 09:41, Hamish McIntyre-Bhatty wrote: > > Cheers for finding that, I didn't really have any luck in my search for > that (or for young Skywalker). > > NB: meant "errors=remount-ro", that was a typo. > > I'm kinda surprised a networking-driver-related OOPS can cause LUKS > volumes to fail (other volumes w/ same filesystem do not get unmounted, > but this one does consistently). > > Hamish Going by what the helpful guy at https://github.com/raspberrypi/linux/issues/3843 says, this might be an issue with the underlying driver for the USB chip in the older pis. The last time it unmounted, all my USB devices reset, so that suggests this is indeed the problem, or at least part of it. Perhaps this explains some of our issues with the network in previous years at the model town, Terry? It might be worth me making a note on the forum about it. I'm currently trying a different overlay which is supposed to fix the problem at the expense of a little bit of USB throughput. Hamish signature.asc Description: OpenPGP digital signature -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] How to Cancel Existing systemd.timer(5) OnCalendar Values.
On Wed, 9 Sep 2020 09:44:44 +0100, hamis...@live.co.uk said: > so has anyone experienced cron jobs sporadically (kind of randomly) not > running when they're meant to? No, never (and I've been using Linux since the early 90s, and UNIX before that). Set up your cron jobs so that the command is: [...] your-command 2>&1 | /usr/bin/logger -t 'my cronjob' Then take a look in your syslog files after the cron job has apparently not run. Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] How to Cancel Existing systemd.timer(5) OnCalendar Values.
On 09/09/2020 09:38, Ralph Corderoy wrote:
> Hi Patrick,
>
>> Is it intentional that OnCalender= has a different spelling of
>> Calend[a,e]r than OnCalendar=20:12?
> Nope! Thanks, that fixes it.
>
> $ systemctl cat updatedb.timer
> # /usr/lib/systemd/system/updatedb.timer
> [Unit]
> Description=Daily locate database update
>
> [Timer]
> OnCalendar=daily
> AccuracySec=12h
> Persistent=true
>
> # /etc/systemd/system/updatedb.timer.d/override.conf
> [Timer]
> OnCalendar=
> OnCalendar=20:12
> Persistent=no
> $
> $ systemctl show updatedb.timer | grep OnCalendar=
> TimersCalendar={ OnCalendar=*-*-* 20:12:00 ;
> next_elapse=Wed 2020-09-09 20:12:00 BST }
> $
>
> Now I just have to work out why updatedb.conf(5)'s PRUNE_BIND_MOUNTS
> doesn't seem to have an effect. :-)
>
Seems like it might be slightly related, so has anyone experienced cron
jobs sporadically (kind of randomly) not running when they're meant to?
On the same pi as has the kernel OOPS issue, I have cron jobs to turn
the power and SD access lights off at night and on at day, and run an
update script in the early morning. For a while now, these don't always
seem to run. I haven't bothered to dive into exactly why, but I was
wondering if there were any common misconfigurations that cause this.
I wouldn't find myself especially surprised if the kernel OOPS was also
somehow knocking CRON out/off-kilter.
Hamish
signature.asc
Description: OpenPGP digital signature
--
Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Filesystem in a LUKS volume unmounts randomly on Raspberry Pi
On 09/09/2020 04:25, Ralph Corderoy wrote: > Hi Hamish, > >> [983261.923836] NETDEV WATCHDOG: enxb827eb7194f1 (lan78xx): transmit queue 0 >> timed out >> [983261.923915] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:466 >> dev_watchdog+0x2b0/0x2b8 > ... >> [983261.924056] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) > ... >> Looks like a kernel oops? > Yes. > https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/comments/43 > is a recent comment on a thread about it. > >> Even though the volume has the "errors=remount-rw" option, it still >> unmounts completely when this happens. Good news is no I/O errors so >> the disk is okay at least. > ‘errors=remount-rw’ is what to do when there's a media error or > something else which can be recovered. You're suffering from a device > driver failure which knocks out a lump of software. Cheers for finding that, I didn't really have any luck in my search for that (or for young Skywalker). NB: meant "errors=remount-ro", that was a typo. I'm kinda surprised a networking-driver-related OOPS can cause LUKS volumes to fail (other volumes w/ same filesystem do not get unmounted, but this one does consistently). Hamish signature.asc Description: OpenPGP digital signature -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] How to Cancel Existing systemd.timer(5) OnCalendar Values.
Hi Patrick,
> Is it intentional that OnCalender= has a different spelling of
> Calend[a,e]r than OnCalendar=20:12?
Nope! Thanks, that fixes it.
$ systemctl cat updatedb.timer
# /usr/lib/systemd/system/updatedb.timer
[Unit]
Description=Daily locate database update
[Timer]
OnCalendar=daily
AccuracySec=12h
Persistent=true
# /etc/systemd/system/updatedb.timer.d/override.conf
[Timer]
OnCalendar=
OnCalendar=20:12
Persistent=no
$
$ systemctl show updatedb.timer | grep OnCalendar=
TimersCalendar={ OnCalendar=*-*-* 20:12:00 ;
next_elapse=Wed 2020-09-09 20:12:00 BST }
$
Now I just have to work out why updatedb.conf(5)'s PRUNE_BIND_MOUNTS
doesn't seem to have an effect. :-)
--
Cheers, Ralph.
--
Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] How to Cancel Existing systemd.timer(5) OnCalendar Values.
Is it intentional that OnCalender= has a different spelling of Calend[a,e]r than OnCalendar=20:12? Patrick -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
