On Wed, Apr 25, 2018 at 11:56:09AM +0300, Андрей Василишин wrote: > Package: sysvinit-core > Version: 2.88dsf-59.9 > > Hello! > New linux-image-4.9.0-6-amd64 4.9.82-1+deb9u3 and old > linux-image-3.2.0-4-amd64 3.2.96-2 does not want boot with sysvinit-core. > After installation systemd-sysv 232-25+deb9u2 all working fine. > > [ 0.228833] DMAR-IR: Failed to copy IR table for dmar1 from previous > kernel > [ 2.4575631 Failed to execute /init (error -2) > [ 2.4573031 Kernel panic - not syncing: No working init found. Try > passing i > nit= option to kernel. See Linux Documentation/init.txt for guidance.
Are you sure there isn't something wrong with your hardware or perhaps your filesystem? These versions are old enough that such a regression would have been reported long time ago: 4.9.82-1+deb9u3 is stable-sec (and stable point release) from 2018-03-03, 3.2.96-2 is oldoldstable-sec from 2017-12-10. What happens if you reinstall sysvinit-core (in case its files were corrupted on the disk)? What if you boot with init=/bin/bash ? Also, mixing packages from two releases apart is not supported, at least officially (usually still works) -- for example, systemd in Stretch has a hard requirement of kernel >= 3.13 which that 3.2 you mention is obviously older than. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the CT scan to prove that! ⠈⠳⣄⠀⠀⠀⠀
