General :: Diagnosis An Unstable System / Seeing File System Is Not Clean During Boot?
Feb 22, 2010
So 2 days ago everything was all fine on my machine. Has been for about a month, but all of a sudden as of yesterday I have no sound, I am seeing IRQ interupts on boot, During boot I am seeing file system is not clean, , and swap space is being used for the first time while doing normal task, etc. These are 2 new hard drives in RAID 1 with ReiserFS. I should have used a newer FS but thats a whole other argument.
Anyways here we go.
The system is Debian Lenny amd64
Physical RAM 4GB + 6GB swap
/var/log/messages
Code:
Feb 21 07:35:09 Sarah kernel: imklog 3.18.6, log source = /proc/kmsg started.
Feb 21 07:35:09 Sarah rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3994" x-info="http://www.rsyslog.com"] restart
code....
I have a 500 GB external USB hard drive that I use for putting images and backup data into.I had some problems with it not automounting today, and in trying to access the drive I got errors indicating that an operation was already in progress. Eventually it mounted on it's own, but I unmounted it and ran "Check Filesystem" from the Disk Utility program on the drive, just to be sure. After a while, it finished and told me that the file system was "NOT clean".So, what does that mean, and how do I fix it? Before I unmounted it, I was able to navigate the mounted filesystem, so it doesn't appear totally hosed.
I want to perform a clean install on my machine - it's had loads of rubbish installed, and is a real mess. Trouble is, while I have downloaded the ISO file, I do not have any blank CDs. Is there a way to mount the ISO and run the installer from within a running system? Probably not, but I thought I'd ask in case I missed something.
I can't login due to my file-system being full. I found the main area with the large usage. Var/log is taking 99.5% of my var folder. On a full file-system scan Var/log is taking up 85% of disk use. File-system capacity is 36 gig. Temp is cleared after each boot.
What can I do to clean up any unnecessary files. I can only boot in safe mode and have limited navigation skills. To get scan results I booted a live-disc.
Vista Recovery Windows 7 GRUB Extended -->Fedora 12 (ext4)
so, I shrunk my recovery in Windows 7 successfully, and booted into my Fedora 12 live cd to run Gparted, and move the partitions so that the free space could go towards fedora, I did such, and then I couldn't expand the partition to my dismay. Next, I woke up this morning, tried to boot to fedora to run SSH, grub loaded, but when I tried to boot fedora, I got the "File system check failed" error, and when I tried 7, it just went to a blank screen with a single "_" in the top left-hand corner.
I just recently installed ubuntu 9.10 in my upstairs computer. It is a single boot system.Downstairs I have a dual boot system. I have windows vista and ubuntu 9.10 installed. It worked fine. I wanted to make this a single boot system and uninstall ubuntu 9.10. I cannot get rid of the grub bootloade
I am getting occasional errors during the boot process.One at the beginning and one or two when I switch to single user mode.I 'd like to run the system file checker to fix any possible errors.But when I run fsck in the terminal I get the message:Code:
mansour@ubuntu-notebook:~$ fsck fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010)
I recently bought 2 RAM modules, 1GB each, to upgrade my system replacing the 460 MB I had before.Once replaced, I started my system and checked with 'free -m' that the system can see them and uses them.But my system became unstable, and it gets stuck (hangs) after 20-40 minutes and I have to do a hard reboot to get it back to work.
Also flash-player crashes few minutes after playing no matter which browser I use.
I have made an upgrade after installing my new RAM and have the latest Kernel installed.
Can anyone answer me the color code of the linux file system?
Especially, for those which have different colors in the background also like some have green background colors and are written in green some have yellow background and are written in black,why is it so? Also please explain me the color code of other also.
I did a fresh install of SuSE 11.4 (WIN7 TOO) and changed my Larger HD1 to the first HD. I was installing and got this error first: the boot loader is installed on a partition that does not lie entirely below 128GB The system might not boot if BIOS supports only lba24 (result is error during install grub mbr) status loc dev/sdb6
I continued with the install and then got:
Yast2 error occured while installing GRUB ver 0.97 (640k lower/3072k upper memory) [minimal bash-like lineediting is supported? for the first word, TAB lists possible command completition anywhere else TAB lists possible completion of a device/filename] grub setup --stage2=/boot/grub/stage2 --force4-lba (hd0,5) (hd0,5) Error 25 disk read error grub> quit
I'm a little bit confused with partitioning the filesystem in Linux. the difference between creating the file system with fdisk and mkfs (when formatting the disk). I can't clearly tell my problem, so please look at this picture:
I am using Gentoo Linux and for a while now, the root file system is mounted read-only on booting. For obvious reasons, this is quite annoying as most services do not start up correctly (I do not use a separate file system for /var). After the system is up, I have to log in, remount the root file system read-write, fix /etc/mtab, mount all other file systems in from /etc/fstab and then start up all the missing daemons. I know that there are ways to make a system run properly with a read-only file system, but I would rather restore the old behaviour of a writable root file system.
The strange thing is that after running mount / -o remount,rw, the file system is mounted in writable mode without any errors. I suspected some problem with fsck, but now I have disabled automatic file system checks on the partition (tune2fs -c0 -i0).When I run dmesg, only these lines mention the partition at all, although I am not sure if not something gets lost because /var/log is not writable:
EXT3-fs (sda5): mounted filesystem with writeback data mode</code> EXT3-fs (sda5): using internal journal The line in /etc/fstab looks like this:
EDIT: This thread has taken a different turn, please go down to viewtopic.php?f=30&t=64242#p370832 Below is I originally wrote, now totally irrelevant.:D I am delighted/bored with my one Debian Squeeze install, so I've decided to free up a partition to play with another configuration of the universal OS.At the moment I am liking the looks of the supposedly not so unstable Sid; what's the ideal download/install path to get Sid up and running? Is it:1) I already have a live Squeeze GNOME DVD lying around; should I install that again and upgrade to Sid?
My work machine crashes 1-3 times a day, and I often lose work. This is getting very frustrating--I've never known a Linux system to be so unstable.
When it freezes, I can still move the mouse around. I believe it's also still doing some background tasks, since files have finished copying before and my music will still be playing, if it was before. But the mouse cursor doesn't change, and it's totally nonresponsive.
The trouble is, I don't know how to diagnose this problem, to tell you something less vague. I might be able to check, to see what's going on? The problem usually comes about when I'm doing something--either loading a new web page, or starting a new program, or even when I just hit a button. Otherwise, I'm just stumped.
I recently assembled a new desktop computer, the following is the hardware details
CPU: intel core i7 2600 Motherboard chipset: intel Z68, GIGABYTE GA-Z68A-D3H-B3 Video card: Geforce GTX 560 Ti
I tried to install ubuntu 11.04 i386 and X86-64 version. Both of them are quite unstable.The system is easy to crash because of network problem and the internet connection is extremely slow. I also install window 7 in the same computer while the wired network is doing well.
I bought a new SD card which I intend to put some MP3s on - except that I can't write to it because it tells me the destination is Read Only. No-probs thinks I: I'll just reformat it.
"Error creating file system: helper exited with exit code 1: cannot open /dev/mmcblk0p1: Read-only file system"
Various chmod commands all result in Read-only file system. I tried umount then mount commands, but it couldn't find it to mount once I'd unmounted it using the same /media/ file path (I assume it's the only one).
My Redhat Enterprise Linux 4 with 6x partitions (/, /boot,/home, /usr, /var, /tmp) of 6.0 GB IDE Hardisk was working quite fine. I decided to create LVM on /home and /var partitions but due to some errors occured and I delete the /home partitions. That's why partition table altered. I then delete 4,5,and 6th partitions (/home, /var, /tmp) partitions and now try to create one by one but following error is coming:-
[Code]....
The Super block could not be read or do not describe a clear ext2 file system. E2fsck b 8193 <device> I have tried following commands,but could not successful:- e2fsck -p /dev/hda7 (where hda7 was created but afterthat it was deleted) e2fsck -a /dev/hda7
I have an XP laptop, currently running very low on HDD space and RAM capacity, waiting to be replaced. Very slow indeed. It recently had problems booting up, and now takes about 20 minutes to get fully started. Is it safe/advisable to run the demo version of Ubuntu from the LiveCD? I really can't afford to trash or crash my computer, it's got lots of important data on it etc.
Ive been searching for days and days trying to get this monitor to output in 1366x768 on Ubuntu 10.04. I knew it was possible, i did it late one night about a month back, but my system became unstable (not due to the resolution, i had setup a firewall to block all incoming till i unlock it, then another application to connect before i log in, and somehow it managed to lock out my keyboard on the login screen AND the recovery console, so i decided to just reinstall it)
Anyways, i found out exactly how to do it (for the Acer 183h that is). Ive spent about 48 hours total pouring through documents and found the documentation for nvidia-settings (easy find, i know, i was hoping to find an easy solution like what im typing up)
So, i figured out I could use Nouvaeu to get the proper settings (since all the modeline calcs dont do 1366, only 1360.) What i did was i went into the log file for the xorg,conf right after i installed, and in there somewhere near the middle it says what the timings are.
Code:
And i inputed that modeline into the monitor section, like so:
Code:
One of the two EDID commands is an old one, i just left it in there so when i was searching throught the xorg log i could find the section really quickly.
(BTW, im not sure if these timings are 100 accurate until i reboot my livecd and check, but im sure thier pretty damn close, and my monitor hasent exploded yet if your worried bout it, grab your livecd, open your xorg.conf, and it "should" be in the monitor section)
Next, i had to input all the Options to not search for different modes into the device section:
Code:
And finally, i had to set the screen to output the 1366x768, entering Modes "1366x768_60_0"
Code:
In the Modeline and Modes section, its VERY important that you have it in the format i have it in. The Modeline name MUST be completely custom, by adding either letters or extra _0.
And thats it!
Reboot, restart X, whatever (I prefer reboot, gives me time to ponder ) and you should be good to go.
(I know this may seem like a beginners knowledge type of thing, but im a beginner, pretty damn bright, and it still took me 4 days So, if this helps just one other person, ive done my part)
Im also pretty sure this method will work with other wide screen monitors, as long as you get the timings off Nouveou via LiveCD or installing the driver.
I've had ubuntu installed on this computer, and I've updated it all the way up to Lucid from Dapper over the years. I'd like to clean out settings and old programs that might not be needed anymore to make it more like a fresh install, as I've noticed some problems that people with fresh installs don't seem to have. Two indicators for Empathy Computer Janitor freezes Weird system tools and wine entries, etc.
Have just assembled a new computer and thought I would install the 64 bit version of openSUSE 11.2 in a "Windows free zone". After a hiccup or two I have managed to get a system of sorts running but on trying to copy files from my old computer(via a memory stick) it tells me that Vfat is an unknown file system.On my old computer I am running 32 bit openSUSE 11.2 as a dual boot system with Windows XP and have no problems moving files between the two different file systems.Is it possible to get a 64 bit file system to read 32 bit file system drives and if so how do I do it?
When I was on Ubuntu/Debian based Linux Distros, I would open up the terminal and type sudo apt-get autoremove && sudo apt-get clean && sudo apt-get autoclean to clean up my system and I would also use Ubuntu Tweak to clean up as well, what commands do I use with Fedora 14 KDE to clean up my system?
The purpose of that topic is to identify if there is any way to totally clean a debian system and make it like a fresh installed system (of course i amn't refering to packages because aptitude is just perfect?
I've been testing Mate since couple of weeks on my Jessie and now I'm convinced that is the perfect DE for me. So I would like to uninstall Gnome 3 without disturbing Mate and my system as well because both DE share many dependencies. If this is very risky I would like at least get rid of all gnome packages which are not shared with Mate.
I was using Fedora 9 until about 1 month ago when my hard drive crashed. I installed F12 on a new hard drive last week. Due to some other software issues (empathy), I decided I should try to get the latest updates. PackageKit kept giving errors and would not update. So, I researched and found that I needed to run " su -c 'yum update' " for the first update then PackageKit would work. I did this and after about an hour of updating, the screen went black. Nothing you can do at that point but hard reboot.
When I did that, I could only get a "GRUB" command line. I played with it for a minute but really I have no idea what to do with GRUB cmd (beyond my experience level). So I decided to wipe it out and reinstall F12. I did that, and was just working thru the updates again. Same thing happened, went to black screen. I have not rebooted it yet, but Im sure when I do, it will be GRUB again. What in the world am I supposed to do with this? I am not a Linux star, but I have been using it for around 8 years now with various distros, so I would say I have at least moderate experience.
Upon boot up, I get lots of new lines added to log files in /var/log concerning apparent problems during boot up. The boot sequence does attempt to show the failure or success during each step as it transitions to the final run level, but is there a good manual or procedure on how to fix each transition, so as to cut down on the amount of pesky warning or error messages?
I am a bit concerned that running a system with warning messages is a bit like running a car low on oil. In the past the goal was to have a perfectly running linux system that came up all the way, and yes, I have seen such. This meant knowing how kernel things work, etc, but still, I would think we would want to pay attention to such things as
[ 1127.997470] ALSA usbaudio.c:1274: 2:1:1: cannot get freq at ep 0x1 [ 894.166132] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
and others and work to bring them to a minimum.
Right now I am working on things piecemeal as I go along, and it will take a lot of time.
I didn't dump the 10K's of log files into this message forum, in case someone asks to see the details, but I am just striving to have the system come up clean, and not with a message like:
Warning: Skipped 98 probes
(whatever that means?? did the kernel just mean that it knew that it is supposed to check 98 things but failed? or that 98 things should have gotten checked but didn't?)
After 8 years of using Mac, which I do enjoy, I decided to jump into the open source community. So I bought a brand new Thinkpad SL510 and installed Ubuntu 10.10 (32 bit) using the entire disk, thus erasing Windows.
The installation process was very easy and the system generally works great. It's fast and I love the interface.
Just encountered one annoying issue which I don't think I should be confronted with, using a freshly installed Unix-based OS: a few times, the system entirely froze. I couldn't move the mouse pointer anymore, the keyboard no longer responded (eg. when hitting Shift Lock the light didn't come on). Waited for several minutes but nothing happened at all. So I had to turn off the computer by pressing and holding the power button.
This has only happened a few times so far, but a few times too many. When it happened, I only had Firefox open, or Firefox and Twinkle. The last time it happened, the screen colours gradually went gray before everything came to a halt.
As per the subject line, the latest slackpkg doesn't honor the blacklist when using the clean-system option. It tries to make my multilib system unhappy.I fixed this by changing line 656 in /usr/libexec/slackpkg/core-functions.sh
