Ask your questions here.
Post a reply
fsmithred

- fsmithred
- Posts: 2101
- Joined: Wed Mar 09, 2011 9:13 pm

## Re: Trouble shooting no ISO file made

Sat Mar 07, 2015 1:06 pm

That, too should be there, because xorriso depends on the libisoburn1 package. It's in my jessie at /usr/lib/libisoburn.so.1.
Something is non-standard about your installation. What steps did you take to remove systemd? (And what were you starting with? Testing netinstall? Upgrade from wheezy?)
apt-get install libisoburn1
or maybe..
apt-get -f install
(with no packages)
orbspider

- orbspider
- Posts: 40
- Joined: Mon Oct 07, 2013 9:35 am

## Re: Trouble shooting no ISO file made

Sat Mar 07, 2015 1:29 pm

now --reinstall libisoburn1

Code:
  `xorriso: error while loading shared libraries: libisofs.so.6: cannot open shared object file: No such file or directory
  `

then a --reinstall libisofs6

Code:
  `xorriso: error while loading shared libraries: libburn.so.4: cannot open shared object file: No such file or directory
  `

then a --reinstall libburn4

Code:
  `xorriso: error while loading shared libraries: libjte.so.1: cannot open shared object file: No such file or directory
  `

then a --reinstall libjte1
and finally a result! The ISO made. what happened to all those needed parts, I really can't say! I don't ever go removing libs from the system, so its weird.
fsmithred

- fsmithred
- Posts: 2101
- Joined: Wed Mar 09, 2011 9:13 pm

## Re: Trouble shooting no ISO file made

Sat Mar 07, 2015 7:10 pm

Well, if you removed systemd, then I can guarantee that other stuff left with it. If you say what steps you took to remove it, then maybe someone can reproduce it, or if it happens to someone else, we can say, "Yeah, that exact same thing happened to orbspider, and here's the fix..."
orbspider

- orbspider
- Posts: 40
- Joined: Mon Oct 07, 2013 9:35 am

## Re: Trouble shooting no ISO file made

Sun Mar 08, 2015 5:49 am

I had problems removing systemd which I found I had after dist-upgrading to Jessie.
I followed online instructions (from http://without-systemd.org of all places - a fake site?) that did
apt-get install sysvinit-core sysvinit sysvinit-utils
apt-get remove --purge --auto-remove systemd
but I found my system booting to a grub rescue prompt after that, so I chrooted from Live to repair grub, to no avail, so I think I reinstalled systemd to get boot back.
then I found the better way of doing
apt-get install sysvinit-core sysvinit systemd-sysv-
and I think that's what worked in the end, keeping systemd installed, but no systemd-sysv - correct?
orbspider

- orbspider
- Posts: 40
- Joined: Mon Oct 07, 2013 9:35 am

## Re: Trouble shooting no ISO file made

Sun Mar 08, 2015 6:21 am

The iso I finally made doesn't boot fully, it hangs at

Code:
  `Authentication failure
  INIT: Id "1" respawning too fast: disabled for 5 minutes`

for Id 1 unil 6... and its recurring if i let it sit there.
Any ideas??
orbspider

- orbspider
- Posts: 40
- Joined: Mon Oct 07, 2013 9:35 am

## Re: Trouble shooting no ISO file made

Sun Mar 08, 2015 6:38 am

I'm still missing some lib's right? /sbin/getty is present, what else is needed for live boot?
fsmithred

- fsmithred
- Posts: 2101
- Joined: Wed Mar 09, 2011 9:13 pm

## Re: Trouble shooting no ISO file made

Sun Mar 08, 2015 12:11 pm

I haven't tried to remove systemd from jessie. The jessie-sysv isos were made from a minimal wheezy install that pinned anything with systemd in its name to -1 (don't install) before upgrading to jessie. So systemd was never in the system, nor was anything that depended on systemd.
I've seen similar messages where the system wants to wait for five minutes because something didn't work right at boot. That seems to be a systemd thing. Try booting into single-user mode and check 'ls -l /sbin/init' to see if it's symlinked to systemd. And check 'cat /proc/cmdline' to see if systemd was called from the boot command.
To boot single - at the isolinux/syslinux boot menu, press TAB and type single at the end of the append line, then ENTER.
Is this a valuable installation? You can muck around in runlevel 1 to try to figure out how your system is screwed up and how screwed up it is. Try running things like 'apt-get -s -f install' 'apt-get -s autoremove' and 'deborphan' (you may have to install deborphan). The '-s' will simulate the action and just tell you what it would do. Also 'aptitude search ~isystemd' to see what's installed.
Here's a pretty good explanation of the error message:
http://raspberrypi.stackexchange.com/qu ... -5-minutes
orbspider

- orbspider
- Posts: 40
- Joined: Mon Oct 07, 2013 9:35 am

## Re: Trouble shooting no ISO file made

Sun Mar 08, 2015 1:07 pm

Ok I tried the single boot, /sbin/init is not a symlink
the cmdline showed up ubninit - sorry I didn't write it all down, that's from unetbootin which I use for making the live usb, as it has been consistent always, and no sign of systemd
so my choices are to rebuild debian or go back to systemdonk :\
Post a reply
Jump to:

Powered by phpBB © phpBB Group.

phpBB Mobile / SEO by Artodia.