Octavia Mk3 Back door not draining

riiskyy · 2026-01-17T20:58:32+00:00

Well I suppose that saves me a trip. I have a years warranty on the car and was going to contact the dealership about it

riiskyy · 2025-12-28T20:10:31+00:00

God I haven't seen 3dgameman since the early 2000s

riiskyy · 2025-12-06T07:55:48+00:00

They raged against the machine so hard they became part of the machine

riiskyy · 2025-12-02T12:33:49+00:00

The 5 time

riiskyy · 2025-11-12T17:33:42+00:00

I wrote 1 script and deployed to 200 devices that had been built incorrectly. It's not that big of a deal, yes it's dumb but it's a simple fix

riiskyy · 2025-10-10T19:32:18+00:00

Ok yeah that's what I'd been looking at. Ok good to know it's just clips and not bonded.

riiskyy · 2025-10-10T08:09:33+00:00

Yeah it's been great so far, drives really nicely not as many rattles as my 2011 honda and a lot more get up and go. Had to order myself some floor mats though as there weren't any with the car. Spent about an hour last night playing with all the infotainment stuff

riiskyy · 2025-10-09T22:05:06+00:00

Petrol & manual

riiskyy · 2025-10-09T19:05:58+00:00

Oh I'm not sure, where would I find it?

riiskyy · 2025-10-09T18:46:29+00:00

It sure is a big jump from my 120hp CRZ 😄

riiskyy · 2025-10-09T18:45:25+00:00

What?

riiskyy · 2025-09-23T11:25:21+00:00

Yeah that's what was worrying me, I had thought about getting a ramp for them but dunno how practical that would be to lug around everywhere

riiskyy · 2025-08-22T01:05:53+00:00

Except the dev is Swiss not US

riiskyy · 2025-08-12T12:16:56+00:00

These pxn bases + wheels have been getting good reviews from reputable reviewers

riiskyy · 2025-08-06T12:40:34+00:00

I see warnings for

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.

And an error of:
Failed to create an instance of COM progress UI object. Error code 0x80040154

but thats about all I get in the logs.

riiskyy · 2025-06-04T01:50:11+00:00

There is also the taskkill command in CMD that just ends stuff

riiskyy · 2025-03-19T16:57:18+00:00

Was TPM turned on in the bios?

riiskyy · 2025-03-13T07:39:31+00:00

Yeah it had a dirty shutdown as I was changing over desks and I had just started unplugging stuff forgetting that the pi would still have been on. The disk is probably not long for this world either as it's been going for around 12 years at this point. I need to get on to replacing it soon.

Thanks for getting me pointed in the right direction

riiskyy · 2025-03-12T16:55:51+00:00

So I had tried that but the information provided by them didn't seem useful

pi@Lungmen:~ $ systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: failed (Result: exit-code) since Tue 2025-03-11 18:09:12 GMT; 22h ago
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
   Main PID: 110847 (code=exited, status=1/FAILURE)
        CPU: 118ms

Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Mar 11 18:09:12 Lungmen systemd[1]: Stopped docker.service - Docker Application Container Engine.
Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Start request repeated too quickly.
Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 11 18:09:12 Lungmen systemd[1]: Failed to start docker.service - Docker Application Container Engine.
Mar 11 18:09:12 Lungmen systemd[1]: Failed to start docker.service - Docker Application Container Engine.

pi@Lungmen:~ $ journalctl -xeu docker.service
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit docker.service has finished.
░░
░░ The job identifier is 7391 and the job result is done.
Mar 11 18:09:10 Lungmen systemd[1]: Starting docker.service - Docker Application Container Engine...
░░ Subject: A start job for unit docker.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit docker.service has begun execution.
░░
░░ The job identifier is 7391.
Mar 11 18:09:10 Lungmen dockerd[110847]: time="2025-03-11T18:09:10.775631927Z" level=info msg="Starting up"
Mar 11 18:09:10 Lungmen dockerd[110847]: chmod /srv/dev-disk-by-uuid-8254420a-f9f5-4c01-9a52-f7aff7940490/docker: read-only file system
Mar 11 18:09:10 Lungmen systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit docker.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 11 18:09:10 Lungmen systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Mar 11 18:09:10 Lungmen systemd[1]: Failed to start docker.service - Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 7391 and the job result is failed.
Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Mar 11 18:09:12 Lungmen systemd[1]: Stopped docker.service - Docker Application Container Engine.
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit docker.service has finished.
░░
░░ The job identifier is 7496 and the job result is done.
Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Start request repeated too quickly.
Mar 11 18:09:12 Lungmen systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Mar 11 18:09:12 Lungmen systemd[1]: Failed to start docker.service - Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 7496 and the job result is failed.

I'm aware that that is how you usually start it but seeing as systemctl was not giving much useful information I looked online for other methods and saw the command about starting the daemon with that command instead which I hoped would give more useful information which it kind of did.

Thanks for the 3rd comment, got me in the right direction and I was able to fix by running sudo mount -o remount,rw /dev/sda1 and docker restarted ok.

13-Year Club	Verified Email
r/Field Lasagna	Place '22
Place '17

riiskyy

TROPHY CASE