Help! Zorin 8.1 restarts my PC automatically & I can't shut it down.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Help! Zorin 8.1 restarts my PC automatically & I can't shut it down.
I completed a solo install of Zorin 8.1 (32 bit) on my PC. Prior it had a dual boot, dual software setup of XP and Ubuntu. Now, Zorin automatically reboots itself when I try to turn off the software. I have to pull the electrical plug to get it to stop.
This is an IBM tower computer, model # MT-M 8113-E7U. Zorin shuts down properly and the computer momentarily shuts down but immediately reboots and reopens Zorin up again. I did not delete the existing partitions for this install - I used a live boot disk of Zorin 8.1 and installed it as a solo software install.
Prior to installing Zorin did you have this same issue?
Sometimes triple booting can cause issues but I am not entirely sure if that 's what is causing the reboot.
This may not be so easily diagnosed:-
Zorin is based on Debian and Ubuntu. I'm trying to find out what 'version of Ubuntu' so I can read the release notes to see what the known issues are. (If any)
There is a software called boot infoscript. It 's a bash script that searches all hard drives on a c omputer for information related to booting. (Might help but not sure yet)
I'll look for the thread that one of our members explained about boot intoscript so you can follow along with it. Basically you download the tar.gz (archive pkg) and I think you run it.
Here's a few links to help you learn more on bootinfoscript.
Sorry I am not good with the output of what bootinfoscript provides. I think Mr. Yancek is.
Disk /dev/sda: 80.0 GB, 80032038912 bytes
255 heads, 63 sectors/track, 9730 cylinders, total 156312576 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f2fa5
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 150030335 75014144 83 Linux
/dev/sda2 150032382 156311551 3139585 5 Extended
/dev/sda5 150032384 156311551 3139584 82 Linux swap / Solaris
I think only ONE software is installed here.
Question - What would happen if I do a complete format of C drive and then reinstall Zorin? Would that work? Would Zorin install from the DVD drive if NO software is on the PC? If so, how/where would I enter the format C drive command?
I did not delete the existing partitions for this install - I used a live boot disk of Zorin 8.1 and installed it as a solo software install.
You may not have selected to do that but the output of the fdisk command you posted indicates you did. You have one Linux partition which would be Zorin and an Extended partition which contains your swap partition.
The 'bootinfoscript' is a bash script which you can download and run and it will output a results.txt file which gives information about your drives/partitions and boot files. On their page, there is a Description box and a link in it with instruction on how to use it. I doubt that will help but it's useful to have. Just google 'bootinfoscript' and you will get the site. Post the output and someone should be able to tell you if there is any problem there.
There is no C drive. That's a windows naming convention which came from their predecessor CP/M and I believe IBM before that. Your Zorin is on sda1, the sda refers to the first drive, the one to the first partition. You could try reinstalling it and there should be no problem with that, just install over the current system. Did you happen to do an md5checksum on the Zorin iso? There should be instructions on the download page and there may have been a problem with the iso download. Might also just be hardware. I'm surprised the shutdown command was a problem.
You can get this error when shutdown issues the wrong run level command to the inittab routine. shutdown -h should call runlevel 0. Your system is always calling for runlevel 6 which is reboot. Since this always happens no matter how you ask for a shutdown then the error may be in your initab. Take a look at /etc/inittab. You should have a table in inittab that corresponds to this table in my Debian stable system:
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
Every Linux system has a similar table. Check your inittab table to see if when you ask to run runlevel 0 inittab is instead calling runlevel 6. Here is the same table corrupted to where it will reboot every time you call for a shutdown.
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
Mr Yancek, the live boot disk apparently does more than advertised. When I solo installed Zorin, it must have erased the prior OS along with all partitions there.
As a complete NEWBIE, I'm having trouble following/doing the whole bootinfoscrip process.
Mr Orasis, the power button idea was certainly a possibility so I opened the PC case a was able to test it (along with my neighbor's help and it's operating 100% correctly.
Mr jailbait, your recommendation looks very promising but everytime I use this inside my Terminal window, the results are aways: command not found. I've tried "sudo" in front of this but I get the same results.
How should I be loading this inside of Terminal window? Thank you!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.