View Issue Details

IDProjectCategoryView StatusLast Update
0003510Kali LinuxGeneral Bugpublic2025-07-14 09:15
ReporterRazvan Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
Product Version2016.1 
Summary0003510: dpkg always fails to configure a random package when dist-upgrade, then read-only file sistem
Description

Machine:Raspberry pi 3 b
Using: kali linux arm raspberry pi 2/3(the same error on raspberry 1)...
Fresh boot...first updating packages then trying apt-get dist-upgrade. The upgrade starts normally but usually after 10-20 minutes the dpkg almost always (19/20)gives an error like unrecoverable fatal error, or error processing archive, then I get a read only file system.

Steps To Reproduce

1.apt-get update
2.apt-get dist-upgrade

Attached Files
IMG_20160830_185313.jpg (741,703 bytes)
inputoutput.png (1,134,454 bytes)
filesystem.jpg (27,747 bytes)   
filesystem.jpg (27,747 bytes)   

Activities

kimocoder

kimocoder

2016-08-30 21:39

reporter   ~0005709

Hi there! I've been testing Kali on both Raspberry PI 2/3 and have been experiencing input/output errors several times, both on Kali (using Berrybot) and the official Raspian distro. Sometimes it seems like when running several processes, makes the filesystem crash, which is not a Kali problem but seems more likely to be a PI problem infact. Beef Framework (Beef-XSS) does also have a memory problem on Raspberry and WPScan installation is kinda tricky because of a Ruby problem again, just to have that said. Have done some research on it on my own Raspberries and thats the conclusion for now, that tricky ARM :)

kimocoder

kimocoder

2016-08-30 21:41

reporter   ~0005710

Tip time.. to remount filesystem to read/write, use "mount -o remount,rw /filesystem.example"

Razvan

Razvan

2016-08-31 07:57

reporter   ~0005718

Hi Kimocoder! Fisrt of all thanks!
And second, is there anything I can do to prevent this from happening?

kimocoder

kimocoder

2016-09-01 16:28

reporter   ~0005727

I have not found a solution to this yet, but i will be looking into it the next days. I will put my findings for a solution here when im onto it. This error (input/output) can be reproduced when running a big apt-get upgrade package installation

Razvan

Razvan

2016-09-01 20:03

reporter   ~0005729

Ok, thank you,looking forward to your findings.
I have in mind to return the raspberry pi 3 and buy an odroid c2 instead...Should it work better than Rpi?

kimocoder

kimocoder

2016-09-01 20:37

reporter   ~0005730

The odroid got more ram, and the rpi problem is also a ram problem (it seems)

look @ https://www.offensive-security.com/kali-linux-arm-images/

For Odroid C2 support.
More ram, arm64 arch.. should work better with Kali than RPI. Beef will also work on Odroid, but not on RPI duo to low ram.

kimocoder

kimocoder

2016-09-03 09:52

reporter   ~0005753

Well, i uploaded a picture reproducing the input/output error. on package installation everytime. I've been looking around for a solution, but it smells like memory corruption over here. On a clean Raspian Lite installation, pull the plug and reboot and run "dpkg --configure -a && apt-get -f install" will fix missing and broken packages.

I also consider buying the Odroid XU4 because you mentioned the C2, but i would rather go for the OctaCore XU4 and performance. eMMC storage for OS, rather than SDCARD is ALSO a big advantage over Raspberry PI.

Sorry you're problem did not get resolved, the Raspberry is the most community loved and supported but it surely could had both more ram and faster storage/filesystem.

Have a great weekend!

Razvan

Razvan

2016-09-04 19:30

reporter   ~0005765

Thank you very much for all your answers. I ordered an Odroid C2, I am waiting for it to be delivered and I will tell you how it works with Kali.

Have a great week! :)

rhertzog

rhertzog

2016-09-05 16:06

administrator   ~0005779

I/O errors are not really fixable, they are either a sign of defective hardware (memory, flash) or a consequence of a nasty kernel bug. Maybe there's something in the RPI 3 that triggers such a problem... but we're not kernel developers so that there's not much for us to do about this report. Hence closing it.

Double check your hardware I would say (with memtest and filesystem write tests).

Issue History

Date Modified Username Field Change
2016-08-30 18:29 Razvan New Issue
2016-08-30 18:29 Razvan File Added: IMG_20160830_185313.jpg
2016-08-30 21:39 kimocoder Note Added: 0005709
2016-08-30 21:41 kimocoder Note Added: 0005710
2016-08-31 07:57 Razvan Note Added: 0005718
2016-09-01 16:28 kimocoder Note Added: 0005727
2016-09-01 20:03 Razvan Note Added: 0005729
2016-09-01 20:37 kimocoder Note Added: 0005730
2016-09-03 09:44 kimocoder File Added: inputoutput.png
2016-09-03 09:52 kimocoder Note Added: 0005753
2016-09-03 09:53 kimocoder File Added: filesystem.jpg
2016-09-04 19:30 Razvan Note Added: 0005765
2016-09-05 16:06 rhertzog Note Added: 0005779
2016-09-05 16:06 rhertzog Status new => closed
2016-09-05 16:06 rhertzog Assigned To => rhertzog
2016-09-05 16:06 rhertzog Resolution open => not fixable
2025-07-14 09:15 g0tmi1k Priority immediate => normal