# Error updating **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [June 14, 2025, 3:38pm UTC](https://discussions.flightaware.com/t/error-updating/98608 "2025-06-14T15:38:13Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\ **Post date:** [June 14, 2025, 3:38pm UTC](https://discussions.flightaware.com/t/error-updating/98608/1 "2025-06-14T15:38:13Z")
Using Sudo Apt-get update and upgrade I recieved some errors. Any Ideas whats up? Reading changelogs… Done (Reading database … 49297 files and directories currently installed.) Preparing to unpack …/0-piaware-release\_10.0.1~bpo10+1\_all.deb … Unpacking piaware-release (10.0.1~bpo10+1) over (9.0.1~bpo10+1) … Preparing to unpack …/1-piaware\_10.0.1~bpo10+1\_armhf.deb … Unpacking piaware (10.0.1~bpo10+1) over (9.0.1~bpo10+1) … Preparing to unpack …/2-piaware-support\_10.0.1~bpo10+1\_all.deb … Unpacking piaware-support (10.0.1~bpo10+1) over (9.0.1~bpo10+1) … dpkg: error processing archive /tmp/apt-dpkg-install-U06GvR/2-piaware-support\_10.0.1~bpo10+1\_all.deb (–unpack): unable to stat ‘./etc/initramfs/post-update.d’ (which I was about to install): Structure needs cleaning Preparing to unpack …/3-dump1090-fa\_10.0.1~bpo10+1\_armhf.deb … Unpacking dump1090-fa (10.0.1~bpo10+1) over (9.0~bpo10+1) … dpkg: error processing archive /tmp/apt-dpkg-install-U06GvR/3-dump1090-fa\_10.0.1~bpo10+1\_armhf.deb (–unpack): unable to stat ‘./etc/lighttpd/conf-available’ (which I was about to install): Structure needs cleaning dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack …/4-dump978-fa\_10.0.1~bpo10+1\_armhf.deb … Unpacking dump978-fa (10.0.1~bpo10+1) over (9.0~bpo10+1) … dpkg: warning: dump978-fa: unable to stat config file ‘/etc/default/dump978-fa’ (= ‘/etc/default/dump978-fa’): Structure needs cleaning dpkg: error processing archive /tmp/apt-dpkg-install-U06GvR/4-dump978-fa\_10.0.1~bpo10+1\_armhf.deb (–unpack): unable to stat ‘./etc/default/dump978-fa’ (which I was about to install): Structure needs cleaning dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack …/5-skyaware978\_10.0.1~bpo10+1\_armhf.deb … Unpacking skyaware978 (10.0.1~bpo10+1) over (9.0~bpo10+1) … dpkg: error processing archive /tmp/apt-dpkg-install-U06GvR/5-skyaware978\_10.0.1~bpo10+1\_armhf.deb (–unpack): unable to stat ‘./etc/lighttpd/conf-available’ (which I was about to install): Structure needs cleaning dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack …/6-piaware-web\_10.0.1~bpo10+1\_all.deb … Unpacking piaware-web (10.0.1~bpo10+1) over (9.0~bpo10+1) … dpkg: error processing archive /tmp/apt-dpkg-install-U06GvR/6-piaware-web\_10.0.1~bpo10+1\_all.deb (–unpack): unable to stat ‘./etc/lighttpd/conf-available’ (which I was about to install): Structure needs cleaning dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack …/7-beast-splitter\_10.0.1~bpo10+1\_armhf.deb … Unpacking beast-splitter (10.0.1~bpo10+1) over (9.0~bpo10+1) … Errors were encountered while processing: /tmp/apt-dpkg-install-U06GvR/2-piaware-support\_10.0.1~bpo10+1\_all.deb /tmp/apt-dpkg-install-U06GvR/3-dump1090-fa\_10.0.1~bpo10+1\_armhf.deb /tmp/apt-dpkg-install-U06GvR/4-dump978-fa\_10.0.1~bpo10+1\_armhf.deb /tmp/apt-dpkg-install-U06GvR/5-skyaware978\_10.0.1~bpo10+1\_armhf.deb /tmp/apt-dpkg-install-U06GvR/6-piaware-web\_10.0.1~bpo10+1\_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ---
**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\ **Post date:** [June 14, 2025, 8:31pm UTC](https://discussions.flightaware.com/t/error-updating/98608/2 "2025-06-14T20:31:14Z")
> [@w7psk](#): > > Preparing to unpack …/0-piaware-release\_10.0.1~bpo10+1\_all.deb The OS on your microSD card is debian 10 (Buster). This is too old. Better re-image with latest piaware sd card image which has OS debian 12 (Bookworm). ---
**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\ **Post date:** [June 14, 2025, 11:50pm UTC](https://discussions.flightaware.com/t/error-updating/98608/3 "2025-06-14T23:50:18Z")
Thanks, I think Ill have to do that as it crashed my system. Poop ---
**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\ **Post date:** [June 15, 2025, 1:07am UTC](https://discussions.flightaware.com/t/error-updating/98608/4 "2025-06-15T01:07:48Z")
Great, and now the SD reader on my wifes laptop doesnt work. And my new laptop doesnt include one. SO Amazon to overnight a reader and a new SD card for good measure. Hopefully will beat the 24hr offline tick. ---
**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\ **Post date:** [June 15, 2025, 3:02am UTC](https://discussions.flightaware.com/t/error-updating/98608/5 "2025-06-15T03:02:09Z")
When I get the new config installed, is SSH activated with the new builds now or do we need to add that blank file to enable it? ---
**Author:** ![geckoVN](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/geckovn/32/136508_2.png) [@geckoVN](https://discussions.flightaware.com/u/geckoVN)\ **Post date:** [June 15, 2025, 3:35am UTC](https://discussions.flightaware.com/t/error-updating/98608/6 "2025-06-15T03:35:42Z")
SSH is disabled by default for security. You can enable it with a blank file or by running raspi-config ---
**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\ **Post date:** [June 15, 2025, 4:23pm UTC](https://discussions.flightaware.com/t/error-updating/98608/7 "2025-06-15T16:23:04Z")
well that was fun. Its back up and running with a new microusb. Decided to go 16gb instead of 8 since I was ording it. Restarting was easy. Even getting FR24 back going was easy. Ill do the charts later. ---
**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\ **Post date:** [June 15, 2025, 7:11pm UTC](https://discussions.flightaware.com/t/error-updating/98608/8 "2025-06-15T19:11:19Z")
> [@w7psk](#): > > well that was fun. Its back up and running with a new microusb. Decided to go 16gb instead of 8 since I was ording it. Glad to know you could write image to new microSD card without any problems, and you are up & running. Out of my 4 Pis, first two are running on same 8Gb microSD cards for last 9 years (since 2016). Third one is also running on 8Gb but for last 7 years (since 2018). The 4th one uses 16Gb microSD card, and is running only for last 3 years (since 2022). I purchased this 16 Gb one because 8 Gb one was no more available in my local computer store. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/system/32/38558_2.png) [@system](https://discussions.flightaware.com/u/system)\ **Post date:** [June 15, 2026, 7:11pm UTC](https://discussions.flightaware.com/t/error-updating/98608/9 "2026-06-15T19:11:41Z")
Closed on June 15, 2026, 7:11pm UTC This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.