System halted linux �������

Uncompessing Linux crc error System Halted

Лиди из за чего это может быть и как это исправить?

Re: Uncompessing Linux crc error System Halted

Ошибка при проверке контрольной суммы архива (скорее всего bz2).

Что делать: восстановить файл сжатого образа ядра на диске (или пересобрать и ядро).

Re: Re: Uncompessing Linux crc error System Halted

Я пересобирал ядро несколько раз но ниче не пашет. Как востановить?

Re: Uncompessing Linux crc error System Halted

Что за дистрибутив? Что за ядро?

Модель и возраст харда, положение раздела / (или /boot).

Re: Re: Uncompessing Linux crc error System Halted

Дистрибутива нет. Это lfs. Ядро 2.4.20. Хард сиагейт. Раздел если смотреть из редхада то /mnt/S (/dev/hda6). Кстати если грузиться с дискеты где ядро 2.4.7-10 (дискета от редхада) то все запускается правда нет ни звука не поддержки vfat. Что делать я его столько собирал 🙁

Re: Uncompessing Linux crc error System Halted

>Что делать я его столько собирал 🙁

У меня такое дурное предположение, что это за-за ошибок либо в компилляторе, либо в архиваторе.

Каким компиллятором собираешь и каким рекомендовано собирать данное ядро.

Попробуй взять конфиг ядра от Красной шапочки и пересобрать ядро с ним.

Re: Uncompessing Linux crc error System Halted

Может быть диск сыпится, а ядро ставится на дырявую облясть — поробуй прочекать винт а конфиг ядра не поможет — тут битый bzImage то бишь архив

Источник

Thread: System halted — Won’t power off!

Thread Tools

Display

System halted — Won’t power off!

Hey all i have a new install of ubuntu 8.04 Desktop — all updates installed. Everything seems to run ok? although the entire system wont power off.
System runs through text on screen and ends with just

And hands there forever, some bits in the PC turn off, as i can hear them click off and less sounds comes out but i dont know what they are :S

Please help! this is the «family» PC for my mum and she isnt «computer friendly» and i dont think she will want to hold teh power button every time -__-

Re: System halted — Won’t power off!

If that doesn’t work you can try (especially if this is an old machine) to add the option acpi=force to the end of your kernel line in /boot/grub/menu.lst

Last edited by yaztromo; August 28th, 2008 at 02:40 PM .

Re: System halted — Won’t power off!

whey hey! thanks dude, that link worked perfect =]

Re: System halted — Won’t power off!

I have one of those machines that has to either have ACPI turned off in the BIOS, or I have to boot with acpi=off.

My machine works good except it doesn’t power off when I shutdown, just stops at «System Halted» with the power still on.

So after trying different things such as apm=power_off in grub.cfg / menu.lst, and apm in /etc/modules, etc. nothing was working for me.

What finally worked for me was a tip from this article by Michael Dougherty, where I booted with pci=noacpi in grub.cfg / menu.lst.

For Ubuntu Karmic 9.10, I made the following changes after making a backup copy of the «/etc/defaults/grub» configuration file:

sudo vi /etc/defaults/grub

Change the line
GRUB_CMDLINE_LINUX_DEFAULT=» acpi=off quiet splash»

to
GRUB_CMDLINE_LINUX_DEFAULT=» pci=noacpi quiet splash»

then run this to apply the changes and rebuild your grub.cfg
sudo update-grub

After rebooting, my machine shuts down without issue.

Ubuntu GNU/Linux is awesome!
Shannon VanWagner

Last edited by Shannon_VanWagner; February 8th, 2010 at 03:43 PM .

Источник

Thread: Uncompression error — system halted — reinstalling kernel and grub

Thread Tools

Display

Uncompression error — system halted — reinstalling kernel and grub

I have lubuntu 13.04. Few days ago I upgraded my kernel up to 3.8.0.21.37. After that at reboot I was hit by «uncompression error — system halted». Message appears right after «loading initrd». After that I try to do repair by myself. I started livecd, chroot to my system, then reinstall kernel (apt-get purge/install linux-image), update-initrams -u -k all and I reinstall grub but all that didn’t solve my problem. I have no more idea what’s wrong.
To be more precisely I have grub on my flashdisc and all my system on the hard drive. That configuration has been working for me for month now and I previously updated kernel without any problem.
Oh, there was one issue. Upgrading kernel up to 3.8.0.21.37 I hit ouf of space. Thus I removed older kernel and reinstalled new kernel once more. I guess this could be the cause of my troubles.

Last edited by darekch; May 24th, 2013 at 07:19 PM . Reason: Helped myself. System fixed.

Re: Uncompression error — system halted

I also did memtest of my RAM which is perfectly ok.

Re: Uncompression error — system halted

I think I know what’s the cause of my problem. During boot grub doesn’t see my hdd. The problem is that the live cd does see my drive and I can perfectly mount and use the drive. So it seems that my drive is OK. I say grub doesn’t see my drive because I don’t see the drive in busybox (which appears few minutes after unsuccessful boot). Now under this busybox I can’t find my hard drive in /dev/ or in /dev/disk/by-uuid/. In both directories I see only my 2 flash drives (one with grub for boot, other with live cd). Thus I can’t even boot from busybox. Anybody has an idea what’s wrong?

Re: Uncompression error — system halted

Ok, I’ve managed to help myself. It took 3 long evenings, but at the end I fix it. Unfortunetly I can’t describe verbose fix description as trying to fix the problem I go through too many cases. However I will describe process that helped me — reinstalling kernel + grub.

. Below instructions are rather for average linux users. I thought that to fix my system I need to completly remove /boot directory! IF YOU ARE BEGINNER YOU DON’T WANT TO DO THAT. I make this decision as apt was reinstalling kernels without failure but my system couldn’t boot.

Preparations

1. Grab live cd with same architecture as Your system you will rescue (32- or 64- bit).
2. Run live cd. Chroot from live cd into your system you will rescue (read http://ubuntuforums.org/showthread.php?t=1581099 for info how to chroot). All next steps are described in the context of root@chroot-system-to-rescue.

Uninstalling kernels and grub

1. cd /boot; ls -l
2. for all listed kernels try to uninstall them:

   Clean apt if you can’t uinstall kernel
   Installing new kernel I got Out of space error — my boot partiton was too small. This caused that I got partially installed kernel which I could not uninstall or install as there was some failure in post-installation scripts. Working solution for such situation is to clean apt and manually remove kernel related files from /boot

   Now try uninstall kernel You couldn’t uninstall previously — apt should tell you it’s not installed so go to /boot and remove kernel’s related files

   Install kernels and grub

   If you have similar files then this store have to end with success. Reboot and keep your fingers crossed.

   Источник

   Linux Mint Forums

   Welcome to the Linux Mint forums!

   [SOLVED] Decoding Failed — System Halted Linuxmint 20

   [SOLVED] Decoding Failed — System Halted Linuxmint 20

   Post by GaryD » Wed Aug 26, 2020 10:40 pm

   I think this is the best category to post this in.

   So, I have a Linuxmint 20 installation (Kernel 5.4.0-40) on SSD. This was an upgrade from 19, and from a known working system using:
   — CPU: Core i7 920
   — Motherboard: Gigabyte GA-EX58-UD3R

   Now, I transferred the SSD to another system with the following components:
   — CPU: XEON X5670
   — Motherboard: Gigabyte GA-EX58A-UD3R

   And when I boot from the SSD, I get the error:

   The error just occur randomly. Sometimes it boot up all the way, some times it doesn’t.

   What seems to be the problem here? Tried all on the SATA ports, tried all configurations, SATA, RAID, IDE mode. The issue still appears randomly on every boot.

   Any help would be greatly appreciated.

   UPDATED: 09-12-2020
   [PROBLEM SOLVED] Decoding Failed — System Halted Linuxmint 20

   SOLUTION: RAM SLOT RE-ORIENTATION FOR DUAL CHANNEL MODE. This is based on actual test — trial and error.

   

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by arvy » Thu Aug 27, 2020 1:28 am

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by GaryD » Thu Aug 27, 2020 2:10 am

   Would you advise me to apply the supposed fix — even the error does not persist?

   Error occurs randomly on every boot. Some times it show, some times not.

   So what Im doing for now is — suspend/resume the machine.

   

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by ricardogroetaers » Thu Aug 27, 2020 3:11 am

   

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by antikythera » Thu Aug 27, 2020 3:26 am

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by Pjotr » Thu Aug 27, 2020 4:41 am

   This should make it easy to apply a workaround (and it’s completely risk-free, so no worries):
   https://easylinuxtipsproject.blogspot.c . .html#ID26
   (item 26)

   It’s risk-free, because all it does is switching the unpacking method back to what it was before Mint 20 (namely gzip). Theoretically this might make your boot process take a few more seconds, but I’ve been unable to detect any lengthening of the boot duration. Probably because the unpacking with lz4 was unsuccessful to begin with.

   I’ve applied it on all of my machines, even though, strictly speaking, it was unnecessary (they also booted successfully with the error). It just feels better to get rid of that error.

   

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by arvy » Thu Aug 27, 2020 9:19 am

   Would you advise me to apply the supposed fix — even the error does not persist?

   

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by antikythera » Thu Aug 27, 2020 1:22 pm

   Re: Decoding Failed — System Halted Linuxmint 20

   Post by GaryD » Sat Sep 12, 2020 11:43 am

   Hey guys! Thanks for all your inputs.

   Problem solved. Its hardware issue on my side — it’s the RAM configuration.
   I tested it several times and its a memory issue.

   It turned out that the dual memory configuration with the XEON cpu is some what problematic in my motherboard. I changed RAM SLOT configuration and it worked!

   Before, it kept on throwing the error, sometimes it boots up some times it doesn’t.

   Came across a form topic and it mentioned about memory issue, so I did a memory test, and test resulted to loads of memory error. I did further testing using 1 stick of ram at a time, and test went fine. So no real memory issue here.

   So I changed the ram slot configuration for dual-channel mode, not the one recommended by Gigabyte in their official user manual.

   Then tried to boot and bam! It worked!

   No changed in compression whatsoever, altho I tried when I was troubleshooting, but did not worked either.

   Case closed. Tested the machine for the past week and no more bootup problem.

   Источник

   Arch Linux

   You are not logged in.

   #1 2012-11-09 23:54:24

   [Solved] System does not power off, hangs at «System Halted»

   Not sure if this is systemd or kernel related, and after the recent round of upgrades it happens on one of my computers and not the other.

   I’m using systemd and do have systemd-sysvcompat installed, but no daemons are started with initscripts.

   When I power off from the KDE desktop using the poweroff icon in the tray, it gets to the point where it says «System Halted» on the console screen
   but the computer does not power off. If I power off using the physical power button on the computer, exactly the same thing happens.

   However, if I power off using «sudo systemctl start poweroff.target» it works perfectly.

   How can I get it to work properly again in KDE or if I hit the power button? Why does it work perfectly on one computer but not the other?

   Last edited by Zamboniman (2012-11-10 03:41:24)

   #2 2012-11-10 00:18:56

   Re: [Solved] System does not power off, hangs at «System Halted»

   It sounds like your current buttons are bound to the «halt» command. Halt used to poweroff, but this has recently been fixed so halt simply halts.

   Check the bindings for those buttons/menu options and ensure they call shutdown or poweroff instead.

   «UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

   #3 2012-11-10 02:04:27

   Re: [Solved] System does not power off, hangs at «System Halted»

   Like Trilby stated, things have changed since systemd logind took over from consolekit. This post might help: https://bbs.archlinux.org/viewtopic.php?id=147388

   The search function on the forums is a valuable resource.

   Time is a great teacher, but unfortunately it kills all its pupils . — Louis Hector Berlioz

   #4 2012-11-10 03:19:19

   Re: [Solved] System does not power off, hangs at «System Halted»

   Thank you. I did search, and found some information that was not relevant. I did not find the thread referenced above for whatever reason. My search skills are usually pretty good for this sort of thing, so I don’t know why I didn’t find it. I fixed the relevant entry in /usr/share/config/kdm/kdmrc. Still haven’t found where I change the hardware button. I’ll search again.

   #5 2012-11-10 03:40:03

   Re: [Solved] System does not power off, hangs at «System Halted»

   Okay, this has now been solved. Thanks are due to bgc1954 and Trillby for pointing me in the right direction. Very much appreciated.

   My search ability, usually very good, completely failed me on this one. However, a few hints was all I needed.

   To make the power button poweroff instead of halt: edit /etc/systemd/logind.conf and uncomment HandlePowerKey and make sure its value is set to poweroff.

   To make kde poweroff properly, edit /usr/share/config/kdm/kdmrc and look for the [Shutdown] section. Ensure HaltCmd is uncommented and set to /sbin/poweroff.

   As to why the behaviour was different on my other computer, for some reason the relevant kdmrc entry on that computer was commented out. Apparently that makes it work correctly. I don’t know why they were different, as I don’t recall changing either.

   Источник

   Читайте также:  Calculator windows forms c