I've been successfully using remastersys for a long time. Now suddenly I'm getting "kernel panic" when loading a newly made disc.
Has anything changed software wise? Or might this be a hardware related issue? Somewhat confusing as this system has been running now for several years unchanged with the exception of newer Mint editions.
I've been using Mint 13 & 14 64 bit Maya versions.
As a test I loaded a Mint 13 32 bit Maya mastered on my other system and it booted fine.
Remastersys kernel panic
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Remastersys kernel panic
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Mint-21.0 Mate 64 bit / LMDE-5 64 bit
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Re: Remastersys kernel panic
Tried burning on a different internal burner. Got similar error message when I tried booting disc on my laptop.
Does this error message make sense?
20.255567 Kernel panic - not syncing: attempted to kill init! exitcode=0x00000200
20.255567
20.255623 Pid: 1, comm: init Not tainted 3.5.0-17-generic #28-Ubuntu
20.255658 Call Trace:
20.255658 ffffffff816744c4 panic+0xba/0x1c9
20.255707 ffffffff81057ffe do_exit+0x81e/0x8e0
20.255736 ffffffff8105841f do_group_exit+0x3f/0xa0
20.255766 ffffffff81058497 sys_exit_group+0x17/0x20
20.255797 ffffffff81689d29 system_call_fastpath+0x16/0x1b
20.255848 panic occured, switching back to text console
Does this error message make sense?
20.255567 Kernel panic - not syncing: attempted to kill init! exitcode=0x00000200
20.255567
20.255623 Pid: 1, comm: init Not tainted 3.5.0-17-generic #28-Ubuntu
20.255658 Call Trace:
20.255658 ffffffff816744c4 panic+0xba/0x1c9
20.255707 ffffffff81057ffe do_exit+0x81e/0x8e0
20.255736 ffffffff8105841f do_group_exit+0x3f/0xa0
20.255766 ffffffff81058497 sys_exit_group+0x17/0x20
20.255797 ffffffff81689d29 system_call_fastpath+0x16/0x1b
20.255848 panic occured, switching back to text console
Mint-21.0 Mate 64 bit / LMDE-5 64 bit
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Re: Remastersys kernel panic
Another test this time on my Acer laptop. Installed Mint 14 Maya 64 bit. Prepared what looked like a good remaster.
Yet when I load the disc I get the same errors as posted above.
Might this be a kernel version based error?
Yet when I load the disc I get the same errors as posted above.
Might this be a kernel version based error?
Mint-21.0 Mate 64 bit / LMDE-5 64 bit
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Re: Remastersys kernel panic
bump
Mint-21.0 Mate 64 bit / LMDE-5 64 bit
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm