General :: Embedded Reboot Crash - Error Executing The Reboot Command
May 4, 2011I'm working with Linux 2.6.23 on an embedded device and am receiving the following error executing the reboot command.
View 2 RepliesI'm working with Linux 2.6.23 on an embedded device and am receiving the following error executing the reboot command.
View 2 RepliesI am using sda1 as /, which is a bootable drive. I do not know if my problem is that I did not create a /boot drive. After removing the iso dvd, I tried to reboot and I get this back: -bash: /sbin/reboot: input/output error Then it returns me to the terminal prompt.
View 6 Replies View RelatedI have a gentoo distribution and need to store the information of dmesg collected until a system crash. At present, after a reboot or a crash the information in dmesg are lost and are not available at the next reboot. How can I save all the information in dmesg until a crash and read them after the succeed reboot?I also checked for dmesg.x files in /var/log or similar files but with no success.
View 4 Replies View RelatedI am trying to get a start up script to work, I have a file /etc/init.d/blah (with 755 permissions) with the contents [URL]. I have run "update-rc.d -f blah defaults". But when I reboot the script is not executing.
View 1 Replies View RelatedWhat is the exact way 'reboot -f' command operates? How does it differ from regular reboot/shutdown? Is it proper to restart pc using 'reboot -f', if not why? The reason why I'm asking this: After installing live-distros via USB, I usually do this 'reboot -f' for restarting.
View 1 Replies View Relatedafter playing games using WINE, I noticed that the system went Black screen of death.
I had to hard boot the system and now system is hanging. However, I can ssh into the system from another machine so I know only X windows hung.
I can log in using NX client without any issue, but can not log in from the console.
This is the entry from .xsession-errors:
GNOME_KEYRING_SOCKET=/tmp/keyring-4P86Nb/socket
SSH_AUTH_SOCK=/tmp/keyring-4P86Nb/socket.ssh
Window manager warning: Failed to read saved session file /home/stranger/.config
[Code]....
I haven't seen anything like it before. I have F15 installed dual-boot with Windows Vista, and I've updated packages. Booting into F15 works fine, no issues.
However: if I shut down and reboot into either (a) Windows or (b) even just the BIOS config screen, the system crashes abruptly after about 1 minute (with no warning/error) and tries to reboot. Booting straight back into F15 sometimes seems to cause the issue, but not always.
The reboot then fails, it doesn't even get to BIOS screen - all that happens is disk lights (HDD, DVD-ROM) keep thrashing. Manual reboot (hold power button for 4 seconds until shutdown; press power button to restart) doesn't help; reboot still stalls. Only disconnecting from mains power, reconnecting, and rebooting works.
It might not even be a Fedora issue - I've tried recent Ubuntu and Mint 11 live CDs, and they cause the same problem - but I'm posting here since I like my F15 installation and want to keep it I've noted that older distros on live CD (eg. F14, SuSe 11.3) don't seem to cause this problem. Maybe a recent kernel issue?
How can something in F15 persist across soft reboot and crash a completely different OS?
After a system crash while watching a video with vlc and downloading somthing, i can't reboot my system.In the secure mode i get this informations[4.774621] device-mapper: dm-rai45: installized v0.2594b[ 1166.832045] ACPI: EC: non-query interrupt recived, switching to interrupt modeNow the scree is black (20 minnutes later
View 1 Replies View Relatedit stuck after loading. should got login window. instead it show me a blank page and a blinking courser i can only press ctrl+alt+del it will reboot my laptop n stuck after the loading process
View 2 Replies View RelatedI am running Windows 7 on an HP laptop trying to create a dual boot with Ubunta 9.0.4(?). I left 300 gb in unpartioned space when I loaded Windows 7 to load linux in (new hard drive). I then partioned the 300gb thru Windows using Paragon Hard Disk Manager. After installing Ubunta, it dumps me at the command prompt. Graphics problem?
View 6 Replies View RelatedThis was my first experience with Ubuntu, I was told to switch the hard drives on my computer and put the Windows drive in a safe place for the install. The first time I did the install on the hard drive (which was the clean second hard drive that came with my computer), I either didn't realize I believe I didn't realize I had to click a button and thought the install had gotten stuck, and therefore cut off the install midway through. The second time around the install went without a hitch, and I was able to boot to desktop once. There, I was notified that I needed/should install NVIDIA drivers, I believe version 173 was listed as the next most recent drives (the other was "current"), I have an NVIDIA GeForce 7350LE graphics card, and after installing the drivers, I went to the restart menu as directed and clicked restart, not shut down but restart, and there were several listed errors on the text/DOS screen, shutdown errors I believe (the errors were 5 digits and were something like 56759 or something like that, I can't be certain if I'm remembering right, though, but there were two errors going over again). I then proceeded to turn off the computer manually, and upon it coming on again, instead of the normal Ubuntu flash screen before login, a more choppy Ubuntu 10.10 screen popped up and it led me to the DOS mode, where I was able to login, but it did me no good because I don't know command logic for Ubuntu. The best I did (its the best I ever do when these things happen) is get menus to pop up that are basically useless. I turned the computer off and on again three times, and tried booting directly from disk, but that failed.
I'm actually using the same computer I just reinserted the Windows drive back in after the frustrating experience. Windows has been giving me problems itself, and I really wanted to switch to Ubuntu but I need to know that this is a fluke and not the norm. I can live with this sort of thing being so uncommon I must have did something that was very strange and out of the ordinary to my computer. But if its commonplace, I want to know that too, because that's just something I can't live with.
last -a shows server rebooted, how to identify the source or cause of reboot? thx reboot system boot Wed Feb 16 08:52 (02:0 2.6.21.7-2.fc8xen
View 2 Replies View RelatedI want to reset my password but when I reboot the grub command never comes up. Is there another way?
View 1 Replies View RelatedI would like to know if I can reboot my headless ubuntu machine from command line to a different OS on the same disk. To clarify, I want to do this without having to manually choose in GRUB.
OS1: Ubuntu on sda1- it is the default OS in an always on server.
OS2: Fedora on sda2 - have to login into this once in a while.
There are no monitors attached with the machine. So I cannot manually scroll through grub and choose Fedora. I want to know if there is a command I can issue remotely to the Ubuntu server to reboot to Fedora.
I'm trying to schedule a reboot ,using the 'at' command. Normally to reboot I have to be 'root'. I tried using sudo to start 'at',to no avail. How would I type the command ,using at, to reboot?
View 2 Replies View RelatedFurther to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27)
reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59)
09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this
Code:
shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40)
reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59)
09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip]
reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54)
shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05)
wtmp begins Thu Mar 11 08:25:26 2010
[snip]
reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42)
shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13)
[snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
I have problem with my reboot command.
sudo reboot and sudo halt -f now don't work (they don't reboot)
but sudo halt -p is shutting down my PC.
I've added entries to my Openbox menu labeled Reboot and Shutdown. Problem is, reboot and shutdown h only work as root, and I never login as root. I've tried su-to-root -c reboot, but the menu entries remain unresponsive. I do not have sudo installed because I feel it is a security issue. However, I found that sudo reboot works with the menu entry, but only if my account is set to use sudo without a password in /etc/sudoers. I use tint2 as my panel, but have had no luck with finding a shutdown/reboot button.
View 4 Replies View Relatedi actually registered here because i'm done with my knowledge of linux, errors which cause my sys to hang and/or reboot randomly after some time. They occur while the system is under heavy cpu, heavy mem-read-write, mediocre mem fill, heavy hdd io (for ~20 seconds every ~5 minutes).
problem background we ordered two identical PCs (specs below), one of them brought those sata errors quoted below from /var/log/messages, the other one runs flawlessly. Same Hardware and Software Configuration. Faulty one brought reallocated sectors right at start, mass seek errors, read errors. 1st try: swap cables, change bios mode ata_piix <-> AHCI. Didn't work. Went away for repair. Stupid Techie did only swap hdd, so problems occured again. Shipping for repair again. Board AND hdd exchanged. no more seek/read errors, no more reallocated sectors. But similar sata problems right after 3 days of previously described workload. Following logs are from after the last repair.
[Code].....
How to run a script/command before shutdown/reboot in Debian Jessie.
I created a script myshutdown.sh in /etc/init.d/ to shutdown rTorrent if the reboot or shutdown now -h command was executed.
#!/bin/bash
#rTorrent Shutdown Script
echo "Shutting down rTorrent!"
kill -2 `pidof rtorrent`
I set the file as executable.
sudo chmod +x /etc/init.d/myshutdown.sh
I inserted a symlink in the rc0.d directory with the process order K04.
sudo ln -s /etc/init.d/myshutdown.sh /etc/rc0.d/K04myshutdown.sh
I also inserted a symlink in the rc6.d directory with the process order K04.
sudo ln -s /etc/init.d/myshutdown.sh /etc/rc6.d/K04myshutdown.sh
Apparently rc0.d is for shutdown and rc6.d if for reboot
After reboot it appears that rtorrent does not run (I cannot connect to rtorrent via rutorrent) but really what is going on. I am trying to do this because rtorrent does a hash check on all files if it is not shutdown properly. I just want it to shutdown automatically and safely, before the system shuts down.
I am using Slackware 13.1 on my Asus K40IN, I also use dual boot by LILO with Windows XP. In Windows XP I can reboot or shutdown by select Start -> Turn off Computer, or just physically push the power button, then the machine will shutdown. In my Slackware 13.1, I can physically push the power button, the machine show that it is switching to run level 0, and then it will power off. However, I can not turn it off or restart my machine by the command (run "halt" or "reboot" as root), it show identical things like when I physically push button, but when it turn to status "Restarting machine" or "Turning off machine", my computer hang there, it does not power off machine or restart it. Is there any one experienced this situation? What should I do to fix it?
View 3 Replies View RelatedI've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
last week while I was using ssh to the computer1 inside a NAT as usual, I made another tunnel from the computer1 that I was connecting to, to another computer2 inside that NAT (ssh 192.168.1.130) and after making some changes in computer2 I typed reboot. The computer2 rebooted but the tunnel totally hung and I had to kill it in my laptop. Since that day I haven't been able to ssh to the computer1 as I am used to.
Here is some more information:
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/une/.ssh/id_rsa
[code]....
today i installed nvidia graphic card drivers for fedora13 using yum, after giving reboot command the system hangs during bootin.
View 1 Replies View RelatedIs there a command i can enter into the terminal or over an SSH session to make an Ubuntu system reboot a few hours later? Sometimes I want to reboot my server and it should take place in the middle of the night when I'm asleep.
View 4 Replies View RelatedI wrote a shell script and tried to execute it in separate terminal using command 'gnome-terminal -e <script>'. When executing first time, it went fine.From second time, I am getting error 'There is error creating child process for this terminal' repeatedly.
View 5 Replies View RelatedI use a Dell inspiron 1525, with windows 7 and fedora 8 in dual boot. Ihave broadcom 4310 wireless card to use.. how ever i could not activate my wireless.. so i guess this the right place where i can get a solution to the problem. After installing the ndsiwrapper by yum, i tried to execute the command ndiswrapper -i bcmw15.inf This returns with an error couldn't open bcmw15.inf: No such file or directory at /usr/sbin/ndiswrapper line 219.
View 1 Replies View RelatedI m using Redhat Linux 5......I am trying to install Nero 4 DVD Writer s/w...It is an exe file ...
I have given permission like this:
Then i execute the file like this:
Its showing error like this:
Just done my first ubuntu 10.04 install on a hp pavilion a320a, the install seems to have went well, though while it is shutting down and before rebooting the following error appears across the screen:
[16866.760778 end_request: I/O error dev sr0 sector 504392]
Before this error appears at the bottom of the screen the error scrolls on the screen with a different number at the beginning of the error where 16866 etc (different number each line) remainder of the error remains the same maybe different sector number but not sure, there is way too many to write down in the time they are on the screen.
Well about a week ago my computer acted a bit funny and upon attempting a reboot I hit grub error 17, and really haven't been able to make it past it. A had my original OS on it and get some files off and backed up at least. Backing up, I've only used a single OS of Hardy Heron. I don't understand why I'm being affected by this error when all I have is two harddrives that are used as unbroken partitions. Best advice I've used is to use a live disk, however the one I've currently got is for Lucid Lynx. I'm not sure whether I need to go and get the old version of a live disc since all I want are my files.
I'm content to update to the newer version (though part of me wants to wait for the next one since it's only a few weeks away.) If I could get my system running as it was that'd be great too. I believe the harddrives are fine since both are recognized in bios, just when running the live disk it asks if it wanted to install it or try it first. When running in the trial of Lucid, I can see the second harddrive and access files as I could on Hardy, but I can't see the main one. I really don't know what to do and am considering just starting over and cursing the loss of the data I want to preserve.