I'm using opensuse 11.1,syetm specification is following
CPU entium 4 2.93GHz
motherboard:asus
Hardisk:40 gb maxtor
Ram:1 GB
my system getting hang periodically after some time and the kernal showing the following error message
[Code]...
I am dual booting winxp and opensuse 11.2 on a 80gb harddrive with 3 partitions. first primary conatins xp, second logical and active contains opensuse and third primary holds data. i want to create another partition after /dev/sda3 using the free space from /dev/sda3.can u advise me if it is possible? and if yes, what do i need to consider. here is the output of fdisk -l
Code:
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x285adb1d
[Code]...
I am running 11.3 for about 4 months and it suddenly started to hang intermittently, sometimes many times a day. Once KDE restarted and other times the screen went black. Most of the time it was just hanging and I needed to force a shutdown. The only clue I got is KDE displayed a notification saying "Disabling IRQ #24" not long after it started to go nuts.
After searching around, I figured the problem was with my external video card so I pulled it out 2 days ago and so far it didn't freeze again. After searching around some more, I found many users fixed very similar issues by upgrading to kernel 2.6.35 and I am ready to go for this solution. But now, I couldn't find out how to upgrade the kernel. People said it can be done in Yast but I only see version 2.6.34. What is the easiest way to upgrade?
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel.
Red Hat nash version 4.2.1.13 starting
sda: assuming drive cache: write through
sda: assuming drive cache: write through
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd-dev failed: 2
Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info:
Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I have been dual-booting Vista and openSUSE 11.2 until my SUSE install is fully functional and now and I want rid of Vista and to reclaim the space for Linux.
Code:
fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x28000000
[Code].....
sda2 and sda3 are the Vista partitions. sda2 is a recovery partition and sda3 is the main partition. All data is safely copied from sda3 and now I want to reformat them for SUSE. I not bothered about partition resizing i.e. I am happy to just have the sda2/sda3 space available to SUSE and mount them somewhere.
1) Do I need to do anything about the boot table first or can I just reformat sda2 & sda3?
2) How should I format sda2/sda3? I'm guessing I need to unmount them and then format. Should I use ext4 or something else? Which command/tool should I use?
During the file system check of an ext3 partition at boot I get the following output:
The super-block could not be read or does not describe a correct ext2 filesystem. If the device is still valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate super-block:
I'm then forced to login in as root and given the following prompt:
I'm reluctant to do as advised by the output and run e2fsck -b because it is not an ext2 filesystem.
Although I can still enter runlevel 5, it doesn't seem to recognise mouse and keyboard input in KDE so my system is effectively redundant at the mo. For this reason any short term workarounds are welcome, but a fix is needed. This problem is part of a longer saga to do with recovering a Windows Vista installation which started failing to boot. I have used both Vista and SUSE tools to try and recover my bootloader to no avail, and this has been the result. If more detail about this is needed please ask and I can explain what I have done.
My server is DELL server. There are occur error about HDD (EXT3-fs error) more detail about the error
# dmesg
.
.
EXT3-fs error (device sdb1): ext3_lookup: unlinked inode 142214653 in dir #142213149
Aborting journal on device sdb1.
ext3_abort called.
[code]....
After upgrading from opensuse 11.1 to 11.2 I get the following error messages while booting the system caused by the initial filesystem check routines:
ERROR: Couldn't open /dev/null (Too many open files)
ext2fs_check_if_mount: Too many open files while determining whether ... is mounted.
fsck.ext3: Too many open files while trying to open ...
I found a new version of the e2fsprogs at the OBS package claiming to fix this problem. But installing this new version did not solve my problem.
Here some information about the affected system:
Operating System:openSUSE 11.2 (i586)
Installed e2fsprogs:e2fsprogs-1.41.11-4.1.i586
Number of LVs:35 (all ext3)
I can only boot if I comment out some of the filesystems in my /etc/fstab. It seems that the number of filesystems must be less or equal 32.
The system frequently freezes the screen. The mouse is still moveable but there is no reaction on any click. Keyboard does not work either (pushing Num-Lock does not toggle the Num-Lock light on the keyboard). However, Alt-Print-b works for a reboot. The only other way out is to turn of the computer.I had this effect some time ago where I thought it was a problem due to the NVIDIA graphics driver. Since then, I changed back to the standard VESA driver and thought the problem would be gone. Just a thought
I toggled through the log files in /var/log which had the file date/time of the crash but I could not find any hint.Which log files could I look as well to dig for the problem? Or any idea for such an effect?
I had left a small windows partition for some programs like MS Office, (I'd failed to install it with wine :-( ) so I was dual booting OpenSUSE 11.3 & Vista. When I decided to replace Vista with Win 7, the grub was missing, I formated the Vista partition, then tried to boot into SUSE before installing win 7. there was some command line, that i tried the instructions I had found on the forums so I typed
grub
find /boot/grub/menu.lst
and I got (hd0,1) so I
root (hd0,1)
[code]....
I got an error about missing (hd0,1), when I pressed enter I got a menu not the one I was used to. When I chose to boot OpenSUSE 11.2 or the failsafe I got error 17 "cannot mount partition" so found a bit of assistance from the following page: How to fix GRUB after Windows breaks it, and how to edit the GRUB menu - Super User when I press "e" and change root (hd0,1) to (hd0,2) then boot by pressing b, I get the usual SUSE boot screen, then the bootup process stops with some text displayed on the screen. there was a lot of text but the following is what I jotted down: the superblock could not be read or does not describe a correct ext2.
superblock corrupt e2fsck with an alternative superblock
e2fsck -b 8193
fsck failed. Mounting root device read-only
[code].....
I am in serious trouble apparently.
System boots up to loading NVIDIA drivers, it shows mouse pointer then it hangs up!
This happened after brutal force rebooting, because system did not responded properly (especially Nautilus). Probable cause:
forget to unmount.cifs a windows shared folder in the network (mounted with mount.cifs). It happened to me already sometimes (to forget umount.cifs), but never ending with this permaenent hanging up)
-tried automatic system repair with suse boot DVD. It repaired something + changed the bootloader. Problem still there
-rebooted--> system hanging up after NVIDIA drivers. code...
I'm having an issue when I'm trying to install SuSE linux onto my desktop.I go through all the steps and everything looks okay, but when it starts to install the packages, I get an error message that basically says:kernel.desktop - unable to install, exit status 127.I have a ATI X1950 video card in the computer, as well as a AMD 64 FX CPU in the system.
View 7 Replies View RelatedI have installed many Linux distributions, but I have never tried openSUSE! So I thought it must be time to try it. I pop the dvd in(I checked the md5 of the iso and checked on the bootable disk) and when I go to install it pauses on the "Probe hard disks"Things I have done:
- Re-checking the integrity of the disk and iso.
- Tried booting with the safe kernel.
- Tried leaving it for ages
I have been trying and failing to install openSUSE 11.3 for the last couple of days to replace my Ubuntu install.
I have downloaded the openSUSE-11.3-GNOME-LiveCD-i686.iso (have downloaded numerous times in case it was a problem with the mirror I used) and done the standard dd stuff, as well as trying it from my windows partition with the ImageWriter app.
When I try and boot with the USB drive plugged in my system hangs at the boot screen and the usb drive starts flashing as if it is being read, this continues indefinitely and never goes beyond the boot screen and i eventually take the usb drive out and restart.
When plugging the drive in when Im in ubuntu it shows up as "openSUSE Live CD GNOME" and all the files seem to be there. In gparted it doesn't recognise the partitions or anything but I presume this is normal... Also reduces the size of my drive to the size of the Live CD but again I presume this is normal...
I have also tried installing using the NET iso however I have exactly the same outcome.
This laptop is a Acer Travelmate 8371 and has had Ubuntu, Mint, and Windows 7 all installed from the same USB drive. There is not optical drive so I have no other ways to install openSUSE.
After the lastest update 11.2 also suffers from the problem already reported here for 11.3. I am lucky to have two linux partitions and was actualy able to boot into the second partition. From this second system I could repair this or at least a quick-n-dirty fallback to be able to boot.
1. Copied the 2.6.21.12-0.2 version for initrd and vmlinuz from /boot to /first_partition/boot
2. Copied the /first_partition/boot/grub/menu.lst.old to /first_partition/boot/grub/menu.lst to reset to the old menu.
After boot the system could start but modules were not loaded.
3. copied /lib/modules/2.6.31.12-0.2-desktop from the second partition to the first.
4. The same for /usr/src/linux-2.6.31.12-0.2*
Now my system will boot and start modules such as network and sound. Still, was this correct? I don't know for sure if there are some issues that I haven't discovered yet. And obviously, what will happen with future updates (either kernel or other)?
i have hd encryption activated on my swap and home disks. now every 20 min or so (not really periodic but definetly reproduceable) my system hangs completely for about 4 - 10 sec while the hd led is on. i have a dual core cpu which makes this even more odd. could this be a side effect of hd encryption especially on the swap partition?
View 3 Replies View RelatedI have a 500Gb external disk (esata) used a part of a backup cycle. I tried to mount it for the next backup cycle and an i/o error was detected in the ext3 journal. I fixed the bad block but that lost the data in the block and ran fsck.ext3. This resulted in a damaged file system message and a scan of the disk and fsck finished ok. The disk mounts rw. I am not really sure if I should reformat this disk. I have copied the backups off the disk and in any case there are later backups. Reformatting is not a problem but takes time and I would prefer not to do it if it is not required but I want a clean file system
openSUSE 11.1 X86-64
I have just installed 11.3, 3.2.1.4-1.2-i586 rpm openSUSE-11.3-1.82. OpenOffice, which I use a frequently came up with an error message - "JRE is Defective"."OpenOffice.org requires a Java routine environment (JRE) to perform this task.The selected JRE is defective. Please select another version or install another JRE and select it under Tools-Open Office.org-JRE". Clicking the "OK" on the third or fourth try brought up a spreadsheet.I checked the installed version and found it identical to OpenOffice.org latest version: 3.2.1.4. I then reinstalled and now it goes through the loading process and flashes a blank page, presumably the function selection screen without any prior warning.
I use a 32 bit PC with 512k RAM. When I loaded 11.2 I received a warning message that some applications might not work, but I went ahead and found no problems with any of the applications that I use. Installing 11.3, no warning was given.I have gone through the posts and found only one similar where it would not load on a system with Gnome.
It is my first try getting Linux on my pc which is an Acer Aspire Z5610. This is not the first time for me when I am getting an Kernel Panic error on this computer.
I looked up google hoping to find an answer and I found out that it may be my BIOS's fault. I currently have Windows 7 on this PC. I have a Phoenix BIOS and there is an update for it called "Bios Linux" on the official Acer support website.
OK, after this short introduction, that's the error:
I really hope to get support for this problem as I can not literally install any other OS to this PC than Windows 7 because they fail with Kernel Panic.
Tried other Linux Editions and even Mac OS Intel Edition and IAtkos V1 and V7 and they all give kernel panic.
I am trying to install a 11.3 virtual machine through Xen on a 11.3 installation. I am trying to install from the opensuse DVD. I get to this point, setting up everything (I can only do paravirtualization) Then the DVD spins for a little while and after that I am returned this error message "device 0 vif could not be connected opensuse....."
I tried a bunch of different settings in the previous screen and I always end up with this error I googled around and it seem to be a problem in different distros but I could not spot a solution at all
I have some trouble booting the current KDE Live Cd (11.2) on my Laptop. I tried USB and CD both. The laptop hangs on the bios bootscreen and I cant select any further option like a boot device. No problem I have with an Ubuntu CD.
View 9 Replies View RelatedNew Intel x64 system installed with Opensuse 11.1 (like the KDE 3.5 option) and has been running well until today. Booting stops at "starting jexec services". Even while booting under "failsafe" system halts at "starting jexec services". Unable to boot to command prompt to attempt repair. Ran "repair" option from install disc with no good results. Still will not boot past jexec services.
View 2 Replies View RelatedEvery time I boot up OpenSUSE 11.3 it hangs at the same "position" for approximately 3 minutes and then continues to boot. Unfortunately I see no corresponding error log e.g. in dmesg output. Hence, I don't know what is the reason for that. Here is my dmesg output. The delay occurs at 20 seconds after beginning of boot process (line 1085). I also analyzed the boot process with bootchart.
My computer: Notebook Lenovo ThinkPad R400.
By trying to install opensuse 11.4 / 1 the installation hungsup at a late level. After rebooting the system, the configuration goes on. When finishing the installation on that way, there are no menus so you can to simply nothing. The problem of system hanging exists also with version 11.3 final release but after rebooting the configuration goes on and when finished, you have the menus.
View 1 Replies View RelatedI tried to install OpenSuse 11.3 on my brand new pc, which already had Windows 7 proffessional in it, and I went step by step through the installation without changing anything. It didn't work. I tried for a second time and this error message kept popping up: "Creating device modes with udev 2.0436224] [drm: i915_diver_load]*ERROR*Detected broken BIOS with 262140/2644kb of video memory stolen. 2.0436224] [drm: i915_diver_load]*ERROR*Disabling GEM(try reducing stolen memory or updating the BIOS to fix)"
And then a lot of letters and numbers wich make no sense to me. Now the only way I can initiate OpenSuse is with the OSuse boot dvd and on failsafe mode.
i install kernel rpm after i boot that kernel network not working kernel name : kernel-rt-trace-2.6.24.7-132.el5.centos.i686 [URL] error "Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
View 1 Replies View RelatedI had some issues with my system hanging on the automatic configuration of the install so I searched the web for the issue. After reading this thread: Hangs at end of SuSe 11 install I used acpi=off apm=off nolapci as the install options and it worked. My question is, do I need to add those options to the /grub/menu.lst or will the install do that?
View 9 Replies View RelatedI just installed OpenSUSE 11.4 on a completely blank machine, empty disks, etc. using a Network Install. The install appeared to run OK, but when it rebooted to do the configuration, it hung. I tried a manual reboot a couple of times, then booted in FailSafe mode - came up OK and ran through the auto-config. Now, it still boots up ok in FailSafe, but in normal mode I get the wallpaper on the screen, but it hangs there.
View 9 Replies View RelatedI have installed Fedora-9 and i customized my kernel. But i did a big mistake in the last steps while customizing. Unfortunately i have executed below shell cmd. grub-install /dev/sda windows drive is not visible But /dev/sda3 is a windows vista file system, now sda3 file system is not in visible for both in linux and also vista OS. How can i retrieve my data back in vista sda3. Here is the info of system
$ su -c '/sbin/fdisk -l'
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
I have 2 hdds, with encrypted / and /home. Besides there are four other (encrypted ext4) partitions I use rarely. In Fedora 11 at boottime I gave the luks passphrase for / and home and the system booted as intended.
Whenever I needed those extra encrypted partitions I mounted them in Nautilus. Now, in Fedora 12 at boottime dracut tries to open all the encrypted partitions, / and /home are mounted fine, but opening all the other partitions gave the following messages in messages.log:
Quote:
dracut: luksOpen /dev/sdb6 luks-02a0e706-a26f-4019-a2a0-88a0366a994d
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-304
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: Buffer I/O error on device dm-0, logical block 124
[code]....
...and these messages are repeated with the other partiitions, and the boot time takes very, very long. How can I tell dracut to ignore those extra encrypted partitions at boottime?