Problems to keep Kali 2016.1 up-to-date on persistent USB

PURPOSE: TO KEEP KALI 2016.1 UP TO DATE ON BOOTABLE USB

Am an old Linux fan, but new to Kali... used to use Backtrack while back
so far so good with latest Kali! Excellent work...

DO NOTE!
Have searched through Kali Docs & Forums re this issue,
but no luck ;(
(pardon if I missed something)

NOW
I followed the following steps to set up Kali 2016.1 on USB

http://docs.kali.org/downloading/kal...ve-usb-install
http://docs.kali.org/downloading/kal...sb-persistence

This is what gparted showed me

(parted) print devices
/dev/sda (320GB)
/dev/sdb (16.0GB)

(parted) select /dev/sdb
Using /dev/sdb

(parted) print
Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.8kB 2852MB 2852MB primary boot, hidden
2 2852MB 2945MB 93.4MB primary fat16
3 2945MB 10.0GB 7055MB primary ext3

Everything was working fine after reboot... persistence fine, etc.

Then I did this, in order to ensure all up-to-date
(after booting from USB, then option to use persistent Kali from USB)

1) apt-get update
..that worked fine to update from
http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease
All good at this point...

2) Then from System Settings, I did "Details"
and then "Check for Updates"
Package Updater showed
"There are 1626 updates available"
>>>This might be where I went wrong??

3) Clicked on "Install Updates"
this downloaded +-1.5GB to USB
...and then gpk process went into "hang" mode
hogged CPU to 99% for hour or what
I had to kill the package updater
...it was going nowhere

4) After reboot, if I re-do "Check for Updates"
it still shows 1626 updates available

5) But alas, apt-get does not work anymore, I get this error

root@kali:~# apt-get update
Hit:1 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

6) Running dpkg as directed gives these errors

root@kali:~# dpkg --configure -a
dpkg: dependency problems prevent configuration of wpasupplicant:
wpasupplicant depends on libc6 (>= 2.15); however:
Package libc6:amd64 is not installed.

dpkg: error processing package wpasupplicant (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent processing triggers for libc-bin:
libc-bin depends on libc6 (>> 2.21); however:
Package libc6:amd64 is not installed.
libc-bin depends on libc6 (<< 2.22); however:
Package libc6:amd64 is not installed.

dpkg: error processing package libc-bin (--configure):
dependency problems - leaving triggers unprocessed
Setting up libc-l10n (2.23-4) ...
dpkg: dependency problems prevent processing triggers for systemd:
systemd depends on libc6 (>= 2.17); however:
Package libc6:amd64 is not installed.

dpkg: error processing package systemd (--configure):
dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for man-db:
man-db depends on libc6 (>= 2.17); however:
Package libc6:amd64 is not installed.

dpkg: error processing package man-db (--configure):
dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent configuration of locales:
locales depends on libc-bin (>> 2.23); however:
Version of libc-bin on system is 2.21-6.

dpkg: error processing package locales (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of rpcbind:
rpcbind depends on libc6 (>= 2.16); however:
Package libc6:amd64 is not installed.

dpkg: error processing package rpcbind (--configure):
dependency problems - leaving unconfigured
Setting up locales-all (2.23-4) ...
Errors were encountered while processing:
wpasupplicant
libc-bin
systemd
man-db
locales
rpcbind

**Please help**

1) How do I get apt-get update to work again?
2) What is best practice to keep Kali on USB up to date?
3) Any other tips / related limitations on USB?

Thanks for any help!

QUICK UPDATE

Ok I managed to resolve the apt-get issue with this

apt-get -f install
Now this is working

root@kali:~# dpkg --configure -a

root@kali:~# apt-get update
Hit:1 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease
Reading package lists... Done

However, I'd still like to confirm

WHAT IS BEST PRACTICE re KALI UPDATES
if YOU USE PERSISTENT USB???

What do do??
What NOT to do??

Thanks!

Pardon, I am new to this forum
if I did not provide sufficient background info:

My problem is:
I am not sure what the best practice is to
do updates of my Kali set up, being on persistent USB

Kali version: 2016.1, GNOME
64 bit architecture
USB

The ERRORS I have been getting were listed in my original post
I have not seen the same issue on Kali Docs or Forums

I have posted an update before this of getting around
1) the apt update error
2) the dpkg error

***OUTSTANDING FROM ME***

Please clarify the Kali Policy with regard to updates
IF I am mainly consuming Kali from a persistent USB boot?
...guess the rolling method, etc is relevant...

Please provide clear, step wise advice re this??

NOTE: These Kali document(s) might require update @ these URLs

http://docs.kali.org/downloading/kal...ve-usb-install
http://docs.kali.org/downloading/kal...sb-persistence
http://docs.kali.org/kali-dojo/03-ka...nce-encryption

Thanks!

I had this same issue on your original post... so i re-installed fresh, then tested to see what would happen if I just let it run its course. Approx. 36 hours later (the time it took for me to just get back to it again) there was a couple windows for proceeding or something like that that also appeared to hang after clicking an option for them. I repeated my wash my hands of it attitude and walked away again letting it do as it wants. Approx.24 hours (once again the time it took to get back to it again) later, everything seemed to work fine. I rebooted to ensure that a reboot did happen. I figured it was a combination of my slow Latitude E5510 Laptop with I3 Intel Core and slow 2.0 USB port. I would assume that the times would very depending on your system so I won't waist time trying to figure out how long it would actually take me to do this without waiting days to get back to it. I was once told patience is a virtue. It would seem to be accurate in my case. I also used full encryption in case you were wondering.

I do apologize for the seemingly useless info, I do however feel it is relevant. It did produce a different outcome then when I interrupted the update because I thought it had frozen. Then I realized that maybe that heavy load on the Processing really was for a reason. Again, I have old equipment. Works great for testing stuff. ;)

Hope it was useful to you.

@Personal

Thanks,
it's very relevant cause am also using an older laptop for this R&D

WISH:
That Kali docs are bit more clear on best practices re if it runs from persistent USB
I mean specific to keeping it updated...