Computer won't boot after Jessie Install

[nokel81]

Hello,
So I needed gtk3.0+ >3.10 and with Wheezy I only got 3.4 so I decided to upgrade to Jessy (as Jessy does have support for >3.10). I followed the steps on the debian site to upgrade and when through the dist-upgrade and the upgrade but after a reboot when I tried to upgrade libgtk3.0+ it said that I needed a new kernel but for some reason had tried to install enough and was far enough along that when I tried to upgrade my kernel from a non-standard 3.12 to the standard 3.16(I believe) it said that it was not possible. Both commands recommend I use apt-get install -f to fix but that did not. I decided to reboot but then I hit a snag, I computer would not boot past bluetooth, I can get to the root console (which is good) and have tried to blacklist bluetooth from loading.

Currently, the bootup cycle stops at a bluetooth bnep and will not continue (have left computer for 1 hour plus with no more output). I have a backup of the data on the disks. I was wondering if anyone would know how to remedy this problem.

[kiyop]

I followed the steps on the debian site to upgrade

Write the "debian site" URL concretely and what you did concretely.

after a reboot when I tried to upgrade libgtk3.0+

Write concrete command you executed.

it said that I needed a new kernel but for some reason had tried to install enough and was far enough along that when I tried to upgrade my kernel from a non-standard 3.12 to the standard 3.16(I believe) it said that it was not possible.

I wonder if you executed wrong commands or wrong procedure.
Jessie uses 3.16 kernel by default. Maybe you made a mistake in upgrading to Jessie.

Currently, the bootup cycle stops at a bluetooth bnep and will not continue (have left computer for 1 hour plus with no more output). I have a backup of the data on the disks. I was wondering if anyone would know how to remedy this problem.

Can you boot the debian with root console?

Both commands recommend I use apt-get install -f to fix but that did not.

Boot to root console and execute

Code: Select all

apt-get install -f

and post the results.
You can save the results to hogehoge.txt by

Code: Select all

apt-get install -f 2>&1|tee hogehoge.txt

Furthermore, you can mount a partition of an USB media by

Code: Select all

lsblk

to confirm the partition and if it is /dev/sdb1,

Code: Select all

mount -t auto /dev/sdb1 /mnt -o rw

to mount the partition.
You can copy hogehoge.txt into the partition by

Code: Select all

cp hogehoge.txt /mnt/

or directly

Code: Select all

apt-get install -f 2>&1|tee /mnt/hogehoge.txt

If you cannot boot to root console, boot with system rescue cd or so.
https://www.system-rescue-cd.org/System ... d_Homepage
Be careful. On system rescue cd, /mnt contained /mnt/windows or so.

Cf) Currently, live debian page is not shown: http://live.debian.net/

You may be able to chroot to the root partition of the installed debian by the following:
If the root partition of the installed debian is /dev/sdXY,

Code: Select all

mkdir /mnt2
mount -t auto /dev/sdXY /mnt2 -o rw

Also mount the partitions used by the installed debian under /mnt2. You can find such partitions by

Code: Select all

cat /mnt2/etc/fstab

As for fstab, read http://man7.org/linux/man-pages/man5/fstab.5.html
For example, if a partition the UUID of which is BLAHBLAH is mounted on /home by the installed debian,

Code: Select all

mount -t auto UUID=BLAHBLAH /mnt2/home -o rw

After mounting all the partitions used by the installed debian,

Code: Select all

mount -t proc proc /mnt2/proc
mount --bind /dev /mnt2/dev
mount --bind /dev/pts /mnt2/dev/pts
mount --bind /sys /mnt2/sys
chroot /mnt2 /bin/bash

to chroot into the root partition of the installed debian.
After chrooting, you can execute some commands as if you logged in as root user to the installed debian.
After finishing what you want to do under the installed debian,

Code: Select all

sync
exit
sync
umount /mnt2/dev/pts /mnt2/proc /mnt2/sys
umount /mnt2/dev
umount /mnt2
sync

[nokel81]

So I followed this website: https://www.debian.org/releases/stable/ ... ading.html


Then to upgrade libgtk3.0+ I ran this command: sudo apt-get install libgtk-3-0

The output of “apt-get install -f” was:

Reading package lists…
Building dependency tree…
Reading state information…
Correcting dependencies… Done
The following extra packages will be installed:
udev
The following packages will be upgraded:
udev
1 upgraded, 0 newly installed, 0 to remove and 989 not upgraded.
355 not fully installed or removed
Need to get 0 B/877 kB of archives.
After this operation, 5,339 kB of additional disk space will be used.
Do you want to continue [Y/n]? Reading changelogs…
Preconfiguring packages…
Reading database … 217532 files and directories currently installed
Preparing to unpack .../udev_215-17+deb8u3_amd64.deb …
Since release 198, udder requires support for the following features in
the running kernel:

- inotify(2) (CONFIG_INOTIFY_USER)
- signalfd(2) (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2) (CONFIG_FHANDLE)
- timerfd_created(2) (CONFIG_TIMERFD)
- epoll_create(2) (CONFIG_EPOLL)

Please upgrade you kernel before or while upgrading udev.

AT YOUR OWN RISK, you can force the installation of the version of udder
WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
AT TJE MET REBOOT by creating the /etc/udev/kernel-upgrade file.
There is always a safer way to upgrade, do not try this unless you
understand what you are doing!


dpkg: error processing archive /var/cache/apt/udev_215-17+deb8u3_amd64.deb (--uppack):
subprocess new pre-installation script returned an error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/udev_215-17+deb8u3_amd64.deb
Error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the stuid helper is not correct
E: Sub-process /user/bin/dpkg returned an error code (1)


Thank you for your help

[kiyop]

So I followed this website: https://www.debian.org/releases/stable/ ... ading.html

Almost all ways to solve your problem are written in the above URL.

Have you did the procedures suggested at the following sections in the above URL ?

4.2.1. Review actions pending in package manager
4.2.2. Disabling APT pinning
4.2.3. Checking packages status
4.2.4. The proposed-updates section
4.2.5. Unofficial sources
4.3. Preparing sources for APT

If you did not, check the files written in the above sections and modify them properly.

If you did, execute the following and post the results:

Code: Select all

cat /etc/apt/sources.list{,.d/*}|grep -v ^#|grep -v ^$

1 upgraded, 0 newly installed, 0 to remove and 989 not upgraded.
355 not fully installed or removed

(snip by kiyop)

Please upgrade you kernel before or while upgrading udev.

Too many packages have not been upgraded by some reason.
Have you executed the following command?
https://www.debian.org/releases/stable/ ... ading-full

Code: Select all

# apt-get dist-upgrade

You should remove the "#" in the beginning.
If you did, was any error message displayed just after the above command?

[Head_on_a_Stick]

Code: Select all

cat /etc/apt/sources.list{,.d/*}|grep -v ^#|grep -v ^$

Code: Select all

grep -v '^#\|^$' /etc/apt/sources.list{,.d/*}

[kiyop]

Code: Select all

grep -v '^#\|^$' /etc/apt/sources.list{,.d/*}

Thank you, Head_on_a_Stick, for telling the better command

[spacex]

Check that your sources are correct, and follow what the other say,
because the below is just a blind longshot as a last attempt...


1.

Code: Select all

 sudo dpkg --configure -a

2.

Code: Select all

sudo aptitude update

3.

Code: Select all

sudo aptitude -s full-upgrade 

And post the output..., so we get to verify that it's fine.

Important, the "-s" in command number 3 stands for "simulate",
so you are only simulating a upgrade. Therefore, it's risk free.

If it looks fine, we will tell you to remove the "-s" and do command number 3 again.
Do not go ahead with the upgrade until someone has cleared it...

[nokel81]

cat /etc/apt/sources.list{,.d/*}|grep -v ^#|grep -v ^$

/etc/apt/sources.list:deb http://ftp.ca.debian.org/debian/ jessie main non-free contrib
/etc/apt/sources.list:deb-src http://ftp.ca.debian.org/debian/ jessie main non-free contrib
/etc/apt/sources.list:deb http://security.debian.org/ jessie/updates main contrib non-free
/etc/apt/sources.list:deb-src http://security.debian.org/ jessie/updates/ main contrib non-free
/etc/apt/sources.list.d/gezakovacs-ppa-wheezy.list:deb http://ppa.launchpad.net/gezakovacs/ppa/ubuntu wheey main
/etc/apt/sources.list.d/gezakovacs-ppa-wheezy.list:deb-src http://ppa.launchpad.net/gezakovacs/ppa/ubuntu wheey main
/etc/apt/sources.list.d/google-chrome.list:deb http://dl.google.com/linux/chrome/deb/ stable main
/etc/apt/sources.list.d/google-chrome.list.save:deb http://dl.google.com/linux/chrome/deb/ stable main
/etc/apt/sources.list.d/mkvmerge.list:deb http://www.bunkus.org/debian/squeeze/ ./
/etc/apt/sources.list.d/mkvmerge.list:deb-src http://www.bunkus.org/debian/squeeze/ ./
/etc/apt/sources.list.d/mkvmerge.list.save:deb http://www.bunkus.org/debian/squeeze/ ./
/etc/apt/sources.list.d/mkvmerge.list.save:deb-src http://www.bunkus.org/debian/squeeze/ ./
/etc/apt/sources.list.d/mono-xarmarin.list:deb http://download.mono-project.com/repo/debian wheezy main
/etc/apt/sources.list.d/virtualbox.list:deb http://download.virtualbox.org/debian wheezy contrib non-free
/etc/apt/sources.list.d/webupd8team-java.list:deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
/etc/apt/sources.list.d/webupd8team-java.list:deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
/etc/apt/sources.list.d/webupd8team-java.list.save:deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
/etc/apt/sources.list.d/webupd8team-java.list.save:deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main



After doing "apt-get dist-upgrade" i got:

Reading package lists... Done
Building dependency tree
Reading state information... Done
You might what to run 'apt-get -f install' to corredt these.
The following packages have unmet dependencies:
consolekit : Breaks udev (< 204-1)
Breaks udev:i386 (< 204-1)
E: Unmet dependencies. Try using -f

[nokel81]

Check that your sources are correct, and follow what the other say,
because the below is just a blind longshot as a last attempt...


1.

Code: Select all

 sudo dpkg --configure -a

2.

Code: Select all

sudo aptitude update

3.

Code: Select all

sudo aptitude -s full-upgrade 

And post the output..., so we get to verify that it's fine.

Important, the "-s" in command number 3 stands for "simulate",
so you are only simulating a upgrade. Therefore, it's risk free.

If it looks fine, we will tell you to remove the "-s" and do command number 3 again.
Do not go ahead with the upgrade until someone has cleared it...

I will do this later

[Bulkley]

All those ppa sources have probably wreaked your system. I suggest you format your drive and do a fresh install. Mixed repositories are frequently fatal.

[nokel81]

How should I save the data that I wish to keep? Can I mount a usb from the cmd line?

[stevepusser]

Was it any surprise that the sources looked like they did?

(If I use that eyeroll smiley any more, its eyes are going to stick like that!)

[nokel81]

Is it possible to change the sources because I can boot into tty1 but that is all

[Bulkley]

How should I save the data that I wish to keep? Can I mount a usb from the cmd line?

Boot a live-CD or USB and use it to copy your important data. Another method is to install a new hard drive and install to it. Then copy your data from the original drive.

[GarryRicketson]

How should I save the data that I wish to keep? Can I mount a usb from the cmd line?

Yes you can ,
Basicly : (one way of many)
===
Edited; Most usb drives are pre-formatted but you might need to format it as well,
you can use "mkfs" to do that:

Code: Select all

 man mkfs 

or "fdisk"

Code: Select all

man fdisk

====

Code: Select all

$ $ dmesg | tail

to determine where the device is, sda, or sdb, etc;
example:

Code: Select all

garry@debian:~$ dmesg | tail
[ 6247.419343] USB Mass Storage support registered.
[ 6248.417064] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Glide     1.27 PQ: 0 ANSI: 6
[ 6248.418506] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 6248.419671] sd 6:0:0:0: [sdb] 122606848 512-byte logical blocks: (62.7 GB/58.4 GiB)
[ 6248.421044] sd 6:0:0:0: [sdb] Write Protect is off
[ 6248.421048] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 6248.421797] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 6248.440189]  sdb: sdb1
[ 6248.443297] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 6248.706684] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! 

The "sdb" is the 58 gb usb stick, and sdb1 is where I have a "fat" partition.

Code: Select all

 mkdir -p /mnt/myusb
 mount -t vfat -o rw,users /dev/sdb1 /mnt/myusb 

Example:

Code: Select all

 mkdir -p /mnt/myusb
mount -t vfat -o rw,users /dev/sdb1 /mnt/myusb 
cd /mnt/myusb
 ls
mydata.txt

You do need to use "sudo" or be "root", in my example,
the only file the usb stick has on it is the mydata.txt , if it a empty stick ,
the directory will be empty.


For details:

Code: Select all

man mount

or
How to mount a usb drive from the command line on a debian system
It would be to your advantage to study some manuals or tutorials on "basic linux commands" if you are going to use Debian or any linux system.

"how should I save the data ?"
Again there are various ways, a simple basic way is to
use "cp"

Code: Select all

man cp

to copy data and files from one place to another.
There is also "dd" a very power full tool, but dangerous in the hands of some one that
does not take the time to read the instructions very care fully.

Code: Select all

man dd

Then "rsync" , I really don't know much about but, I could read:

Code: Select all

man rsync

and after I read it tell you more , if need be,...the manual does say:

rsync(1) rsync(1)

NAME
rsync - a fast, versatile, remote (and local) file-copying tool

And 100s of times on this forum I have noticed that is what many other recommend.

[kiyop]

To nokel81,

All those ppa sources have probably wreaked your system. I suggest you format your drive and do a fresh install. Mixed repositories are frequently fatal.

+1

You should read https://wiki.debian.org/DontBreakDebian

Boot a live-CD or USB and use it to copy your important data. Another method is to install a new hard drive and install to it. Then copy your data from the original drive.

+1

There are some info on live cd at https://distrowatch.com/search.php?category=Live+Medium
https://en.wikipedia.org/wiki/Compariso ... Live_media

Code: Select all

$ $ dmesg | tail

to determine where the device is, sda, or sdb, etc;
(snip by kiyop)

Also, the following commands may be of help.

Code: Select all

lsblk
blkid
fdisk -l
parted -l

Code: Select all

 mkdir -p /mnt/myusb
 mount -t vfat -o rw,users /dev/sdb1 /mnt/myusb 

I wonder if you had better make in /media some directory where you want to mount some partition in a removable media, although you will not use the broken debian anymore.
Refer
http://www.tldp.org/LDP/Linux-Filesyste ... html#media
http://www.pathname.com/fhs/pub/fhs-2.3 ... MOUNTPOINT
https://en.wikipedia.org/wiki/Filesyste ... y_Standard

I suggest rsync or cp rather than dd.

[GarryRicketson]

Kyop has a good point, I agree it would be better to mount it in /media/
In fact normally on my system, usb sticks mount automaticly, to /media/usb0
To that :
(if it did not mount automaticly )

Code: Select all

mount /dev/sdb1 /media/usb0