Ubuntu
schroot package

schroot fails after update from saucy to trusty

Asked by john.d@servergy.com

# schroot -c centos -u root
 # E: centos: Chroot not found

1. What is "Chroot " ?
2. /etc/schroot/schroot.conf file is still present;

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu schroot Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

What is the output of:

lsb_release -a

What are you trying to achieve?

Thanks

Revision history for this message
john.d@servergy.com (john-d-0) said : 		#2

Hi

(trusty)root@jade-rev4:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
(trusty)root@jade-rev4:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 927746568 8954836 871641908 2% /
none 4 0 4 0% /sys/fs/cgroup
/dev 16532340 12 16532328 1% /var/lib/schroot/mount/trusty-47525f73-9182-45db-a2e5-7ffa1144fcaf/dev
tmpfs 3308560 872 3307688 1% /run
none 5120 0 5120 0% /run/lock
none 16542792 76 16542716 1% /run/shm
none 102400 12 102388 1% /run/user
192.168.1.140:/home 425124864 128583680 274946048 32% /work
/dev/sdb1 960904560 41888196 870205256 5% /home2
/dev/sdd1 98828844 41422204 52386332 45% /fedora
/dev/sdd2 106735900 12954500 88359464 13% /centos6
/dev/sdd3 126502524 6361656 113714868 6% /trusty
/dev/sdd4 110594080 61044 104915108 1% /fedora17
/dev/sdc1 110690440 1880584 103187108 2% /centos6a

(trusty)root@jade-rev4:~# schroot -c centos -u root
E: centos: Chroot not found
(trusty)root@jade-rev4:~#

I am trying to run schroot to previously installed instances;

Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#3

Omgubuntu has a guide called " sticking it to Grub " This will show you how you can chroot to the installed OS.

Revision history for this message
john.d@servergy.com (john-d-0) said : 		#4

It was working prior to upgrading trusty

Revision history for this message
john.d@servergy.com (john-d-0) said : 		#5

Thanks actionparsnip, that solved my question.