Debian Configuration :: Clock Readjusted After System Crashed - Cannot Reboot
Dec 20, 2010
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
I updated squeeze last night for the first time. It worked fine after 1st reboot last night. There was one reboot stalled at "hald" so I shut down and restarted. Worked ok 2nd time around
Today,upon login I got a string of taskbar notification (which I couldnt read as they all overlapped . I was able to see a kernel error message but couldnt report it (network was down) or save it (USB stick not recognised) Some programs worked, others didnt
I have the partedmagic rescue distro on USB stick so have those programs to use in order to fix the problem. Any idea how I can repair this? I tried fdisk for the hell of it. reported clean partition as predicted. I am using debian-testing-amd64-kde.
Debian squeeze (weekly build) with latest kernel "2.6.32-5-686"
installed the latest updates, but latest updates to "Grub pc" crashed my system... it stops before login-screen. Unfortunately i can see any error messages, the screen stays black...
16GB RAI've been running the Debian-based Proxmox VE on it for six months or so with no problems.Today I loaded Centos 5.5 x64. During a reboot, the file system crashed and fsck couldn't repair.I loaded it again, did all the updates, and loaded my applications. On about the third reboot, it crashed again and fsck couldn't fix it.I don't really know where to begin. I doubt seriously that any hardware has went bad since yesterday.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I installed a fresh version of squeeze, with kde, and it worked fine. After I untarred my backup /home and /etc, things came to a standstill. I got a final ERROR code after /home. After a restart I got a 'fix your system' warning requiring a Control-D, which I couldn't type. I had used tar -xzvpPf ...... If I had included a -w, which asks for confirmation before overwriting data, could I have prevented this problem.
I added an ext4dev filesystem to my hard drive as /dev/sda3 and mounted at /share with the goal of putting all of my multimedia files on it and sharing it through NFS. I followed this guide: [url]
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.
I rebooted my vServer (Debian 8) and it doesn't came back up. Well, I used the rescue console on my server and the server seems to be running fine, except the network was broken. So I tried 'ifconfig' but nothing came up. So I tried to enable my interface with 'ifconfig venet0 up', and now it appears in my ifconfig list
My HWaddr doesn't look that well :) 'ip addr' prints this result:
Code: Select allroot@i67svof:/var/www# ip addr 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
These are the last lines in /var/log/syslog:
Code: Select allroot@i67svof:/var/www# tail /var/log/syslog Feb 20 11:34:16 i67svof systemd[1]: Stopping memcached daemon... Feb 20 11:34:16 i67svof systemd[1]: Stopping Network Name Resolution... Feb 20 11:34:16 i67svof systemd[1]: Stopping Regular background program processing daemon... Feb 20 11:34:16 i67svof systemd[1]: Stopping Login Prompts.
[Code] .....
And finally my network config in /etc/network/interfaces
Code: Select all# Auto generated lo interface auto lo iface lo inet loopback # Auto generated venet0 interface auto venet0
I have installed Firestarter, and set it up following some manual (just a simple, baseline setting, nothing fancy). However, after restart I got error message: Starting the Firestarter firewall... failed! and then, later: startpar: service(s) returned failure: firestarter ... failed! Why this happens?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback
I tried to update my main computer from Ubuntu 10.0 to 11.04. I wish I could remember what it said, but it crashed during the update. The lights on the keyboard were flashing on and off as well. When I try to boot, all I get is a black screen and flashing lights. The Ubuntu recover also has the same thing. I am going to try a fresh install. For some reason I am leaning to the power manager, but I am no where near sure.
I've an Blade 1500, sparc64 IIIi with 2 hard disks and 2go of RAM. The computer run with debian 7.7.0 and BSD (opensxce) for each hard disks.
1/ When it's run under BSD there are no problems, the uptime are on many hours. 2/ when it's run under debian with XFCE x-window, the uptime is 4 hours 30 minutes and computer reboot automatically !
Into the control panel i've deactivate the hibernation, screensaver and power management ! I want to find the files for manage the time down. I think that the problem is in XFCE window manager.
I'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.
I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces - /etc/network/interfaces is configured with a static IP and relevant parameters - ifconfig shows eth0 and the correct information - netstat -rn shows the basic default route to the gateway - have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
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
Dual boot system. Boot Linux Fedora 13 and the hardware clock is set to GMT. Boot Windows 7, time is wrong, as it expects the hardware clock to be set to the local time. reset the hardware clock each time I reboot in to the other O/S.
I am having slight issue with setting up file sharing. I have a windows 7 pc and hp proliant microserver running. I have a raid array which I am using as a share for storing music, pictures etc. When I reboot the debian server I can't connect to the server from the windows 7 PC (I have mapped a network drive) until I go on to the server and restart samba with /etc/init.d/samba restart - then everything works fine. I can ping the server with both ip and hostname but the network drive does not connect - this is straight after a reboot. Is the /etc/init.d/samba restart doing something differently to when the server boots? I have read several posts relating to printer sharing issues which point to samba not starting before cups so I am wondering if samba is starting before some of the relevant networking services.
I am using Squessze and Gnome. When I try to use the gui System>Administration>Network or Users and Groups I get the error The configuration could not be loaded. You are not allowed to access the system configuration.Everything was working before. I read around a bit. In some cases,it was caused by mismatching group and password files after using the gui. I do not know how to check if they are matching. Of course I do not know for sure that is the problem in my case.
running Debian Squeeze (standard 32bit squeeze Kernels linux-image-2.6.32-5-486 and linux-image-2.6.32-5-686) happily without trouble on a 64bit capable Samsung laptop featuring an Intel T3200 Dualcore processor. However, when I try to boot using the squeeze 64bit kernel (linux-image-2.6.32-5-amd64) the system proceeds through a few text lines immediately after Grub, and then performs a warm start.
The text output I get immediately after Grub look similar to the ones I get booting the 486 and 686 kernels, without any indication for the reboot behavior. The rebooting also seems to happen before any entry is written into the boot/system log files (logging is enabled). This behavior also occured when I first tried to prime the machine from the Debian squeeze install CD using the amd64 kernel. I'm generally happy with the 32bit kernels, but I'd like to use the amd64 support to do some Java compatibility testing for 64bit architectures.
The Laptop is a Samsung R510-Aura T3200 Delfina with the following Hardware and Setup (using Grub as boot loader):
- Intel Pentium Dual CPU T3200 @ 2.00GHz (see http://ark.intel.com/Product.aspx?id=37160 for details) - NVIDIA GeForce 9200M GS - 3GB RAM + 1GB reserved for GeForce - Konfiguration Details: -- Phoenix Bios
[Code]....
Maybe a strange BIOS-Setting that works with the 32bit kernels but not with the 64bit kernel? I've seen a post on here that indicates someone is running the amd64 kernel on a T3200 successfully, and the chip is definitely 64bit capable, so the reboot behavior is a complete mystery for me
I use Debian testing for six months and I started used it six months ago. I use apt-get distupgrade for long times , but today after apt-get update and apt-get dist-upgrade , my system reboot and can not boot and I see URL...and system can not , I see this errors after grub
There seems to be a problem with Raid on Debian. I got a new Fujitsu Primergy TS 100 S1 server, with hardware Raid (and 2 disks) installed everything nicely over the net including GRUB - but when it comes to reboot the system does not boot.
Is there anybody here who knows about the problem?
I wanted to switch to Linux from Windows so I decide to install Debian. The installation completed successfully but after that the bootloader doesn't show after the system reboot. So it is just black screen. I have an option for booting Debian (which will go to a black screen) and go to command line which looks like command prompt in Windows. I tried going to the command and it shows
grub>
I don't know which command to input since I'm a newbie and not familiar with Linux. I installed Debian from USB using unetbootin. What I should do to successfully install Debian?
I cut paste sys folder, tmp folder, and many more folder to a backup storage place , after that folder icon and other icon converted into txt icon , i can make any folder but can't access, can't open storage, thrash disappear, terminal icon disappear, and also the application and places and system icons, after that someone suggested restarting may help but i can't restart it , so i unplugged the power wire and replugged it and restarted the system but it can't open , all things comes fail, and show INIT: "x" respawning too fast: disabled for 5 minutes. after each 5 mins this msg is repeating
