Zero w shut down during apt upgrade

Hi!
My zero w always shut down whenever I try to upgrade the os (rasbpian jessie 17/04…) I tried different SD cards and different power supplies on both my pis without success.
Any idea what causes these issues? The power supply provides up to 1.5 A. Do I need more?! I have never experienced anything like this with my pi 3 using the same power supply…

Cheers
Daniel

what does the process say, or log if it’s not possible to catch it as it happens? Could it be that you have no space left on the SD?

If you’ve recently re-formatted an SD card for use with your new Pi, did you remember to expand the filesystem in the raspi-config menu? If your SD card is over 8GB big, you may need to expand your system so that it can update.

The process just freezes completely, just like so:
26 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/79.0 MB of archives.
After this operation, 4,548 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs… Done
Preconfiguring packages …
(Reading database … 31473 files and directories currently installed.)
Preparing to unpack …/tzdata_2017b-0+deb8u1_all.deb …
Unpacking tzdata (2017b-0+deb8u1) over (2016j-0+deb8u1) …
[…]
And then it just freezes. Syslog give no info, you just see some arbitrary entry, and the next one would be info on starting up again (after I reconnect power). I had expanded my system to full capacity of 16 GB, 14 Gigs free…

[Update]
Okay, it seems to be the SD card. I monitored dmesg and eventually got this output:

[Jun29 22:33] mmcblk0: card_busy_detect: error sending status cmd, status 0x4080900
[  +0.000012] mmcblk0: retrying write for general error
[  +0.000302] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000055] mmcblk0: retrying write for general error
[  +0.000256] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000068] mmcblk0: retrying write for general error
[  +0.000263] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000056] mmcblk0: retrying write for general error
[  +0.000252] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000050] mmcblk0: retrying write for general error
[  +0.000278] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000057] mmcblk0: retrying write for general error
[  +0.088883] mmcblk0: mmc_blk_err_check: general error sending stop command, stop cmd response 0x80d00
[  +0.000053] mmcblk0: retrying write for general error
[  +0.000038] blk_update_request: I/O error, dev mmcblk0, sector 2190712
[  +0.000020] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:314: I/O error -5 writing to inode 17444 (offset 0 size 4096 starting block 273840)
[  +0.000014] Buffer I/O error on device mmcblk0p2, logical block 262063
[ +10.185094] mmc0: timeout waiting for hardware interrupt.
[  +0.000023] [239a80f7] CMDD 8 200
[  +0.000009] [239a80f8] SDMA da43a0fc dac27e10
[  +0.000007] [239a80fa] FCM< da43a02c da43a094
[  +0.000006] [239a80fa] RSP  900 0
[  +0.000007] [239a80fb] FCM> da43a02c 0
[  +0.000007] [239a80fb] CMD  19 200
[  +0.000006] [239a80fb] REQ> da43a02c 0
...

So: please stay away from these here: Lexar 16GB microSDHC UHS-I LSDMI16GBB1EU300A

1 Like