I am running Suse 11.0 and the system had stopped working. I booted from the disk and chose repair system. Now I can get to the Give root password for login and it accepts the password, but I get the line
(repair filesystem) #
My system got stuffed after a trivial online update, it downloaded a new kernel update, I rebooted and now it won't boot at all saying "FATAL: Could not load /lib/modules/126.96.36.199-0.1-desktop/modules.dep: No such file or directory", then some stuff, then "mount: unknown filesystem type 'ext4'", "could not mount root filesystem"... It's on my laptop without a DVD drive and I've only got a LiveCD USB stick which doesn't have a YAST system repair tool. Is there any way to repair a system without a DVD drive?
I was trying to upgrade to 11.2 from 11.1 by upgrading the OS online. However my internet connection failed and the upgrade has now messed up my system. I have a dual-boot system with Windows XP and I'm wondering if it would be OK in getting the DVD and selecting update? Or do I have to change the boot log etc?
Im probally just being a noob here but for the projects sake I thought it would be good to identify this problem. I have an old advent laptop and I tried to install Opensuse from DVD on it. I followed the installation as normal but when I tried to boot it said some sort of check was forced and then I have to enter the admin/root password upon doing this I got the message system repair # in red. I have tried to repair the system through the installation DVD and tried re-installing it but I still get the same message.
It used to be that the dvd menu offered an option to "repair the installed system". THis was really very convenient. The openSUSE 11.3 dvd for x86 now only gives a "system rescue" option which leads to command line directl. Where have been "the repair the installed system" tools? How can we access them now? What is a reasonable set of tips that's supposed to be used after logging into "system rescue"?
I have a following problem: Recently my drive with Ubuntu 9.4 has mysteriously stopped working, i.e. when I switch the computer on it informs me that GRUB didn't find the filesystem. Well, I suppose it happens.
First, I though it was due to the drive dying, but I popped it in an external enclosure and HDTune told me the drive was fine. Wanting to recover the files on the drive before reinstalling I first tried to mount it in said external enclosure under Windows (I have Win Ext2 driver installed which used to work just fine). This time, however, drive gets assigned a letter but upon opening it Windows popped up an error saying that the drive was not formatted and whether I would like to format it then.
Unfazed by this streak of failures I tried to mount it under Linux but, alas, to no avail. I might have tried every single -t operator under mount command but it still won't budge and let me mount.
I'm new to openSUSE, this is the first time i try to install openSUSE version 11.4. on my IBM Thinkpad T43 (on which SUSE Linux version 8.0 has been running before without problems). I have downloaded the ISO images and successfully burned the ISO images on a blank DVD. Having placed my openSUSE DVD in the drive and rebooted my laptop I can see the boot screen.
I then select installation with arrow up/down and press enter. Choosing language and keyboard layout works fine, as well as accepting the license agreement. However, when it comes to 'System Probing' the installation stops at 'Search for system files'. The cursor shows a little turning disk but the rest of the screen is blocked.
I got connecting to our NAS over NFS working perfectly. Direct NAS Reading & Writing - How? But on Saturday I found out it had stopped working. For no apparent reason, not straight after an update either I don't think. When I manually try to mount --verbose:
mount 192.168.100.14:/IHL /mnt/IHL --verbose mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Tue Jul 6 14:48:32 2010 mount.nfs: text-based options: 'addr=192.168.100.14' mount.nfs: Unable to connect to 192.168.100.14:111, errno 111 (Connection refused) mount.nfs: mount to NFS server '192.168.100.14:/IHL' failed: System Error: Connection refused
Corresponding fstab line that used to work just fine. 192.168.100.14:/IHL /mnt/IHL nfs auto 0 0 For now, I can drop back to Samba but this is a PITA as I can't open OpenOffice documents and write to them directly on the NAS. The fact smb://192.168.100.14/IHL works proves networking wise we're cool too. There is no firewall between this PC and the NAS, the NAS is instructed to allow my PC's LAN IP full access. OpenSuse's software firewall has been told to allow NFS Client too. Why would this setup break out of nowhere? How can I debug this best? I see nothing relevant in /var/log/messages How can I get it to work again? A hopeful reboot didn't do its usual wonders...
Turns out I downloaded the openSUSE 11.3 DVD Full and well, I see that in the boot options, I do not see the option "Repair System", only:
"Install" "Booting from Hard Disk" "Verify installation media" "Firmware Test" "Test Hardware"
No more, and I see that everyone leaves the option, as in version 11.2, to "System Restore / Repair System" Is there any way to get it? I need to repair GRUB, as I appear, I had it in a logical partition and therefore I have GRUB errors, since the re-installation of windows and then deleting it, I thought of this. Any way to get this option by the Live CD or what? Is it a BUG in version 11.3?
my system stopped booting after recent update.When I select desktop it goes to splash screen an dies.Have to hit reset key.If I select nomodeset it boots fine excepts graphic resolution is 1280x1024 instead of 1680x1050.System is sandy bridge, Asus P8H67-M EVO, Intel Graphics enabled no other grapics cards, Suse 11.4 64 bit.I do my updates with zypper up.
Playing with the Box, I deleted a Raid-0 partition intentionally, saved it, and reboot drops me to (Repair Filesystem#) prompt. I notice during boot-up that the box didn't find /dev/md0, which is expected.
So what's the recovery procedure, since I can't edit #/etc/fstab, permission denied.
#fdisk -l shows all other partitions.
Not much familiar with fsck/e2fsck, yet like to give it a try.
The desktop effects on my system stopped working. They were working fine up to a couple of days ago. Now it says I need to check my configuration for xorg. How do you do that?
Also this appears to have started after another user was using my system and crashed it. They said that it just shut-off with no explanation as to what happened.
lspci -v shows this
HTML Code: 01:05.0 VGA compatible controller: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device ff02 Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 16
How do I get back to the systems default drivers?
I do NOT wish to have to reinstall F14 yet again because the system has been very stable since the last install.
I am using Fedora core 10. I have changed my partition size of Linux from windows. After I finished resizing the partition, I rebooted my system to the Linux platform. While booting it gave me an error: repair filesytem #1: I don't know what to do?
My main PC has AN Athlon X2 4600+ on an Asus M2npv-vm. Has been working fine for ages running Ubuntu. Today it the system locked up and I had to do a reset. Since then it will not connect to the router or cable modem. I can connect another PC to the router, so that looks okay.
What can I do to test the network connection from Ubuntu? It's not even getting an IP.
I suppose it could be something has died in the hardware, but want to eliminate other possibilities first.
I'm running Kubuntu 9.10 (Karmic), and my System Monitor (a.k.a. Task Manager) has stopped working. I had been using the graphical version of the app because it was easier and faster for me to deal with. I know that there is a command line solution for this, but I also know it involves having to know the task number of the program I want to kill (I've got a game that I love to play, but only closes cleanly about 10% of the time). I've posted a couple of screen shots to show the errors... The first one is the error message itself (I have to hit 'OK' on this twice to clear it), and the second one is the resulting empty window of the System Monitor
I recently updated my Debian jessie system (for the first time in a few months). It broke my video driver (fortunately a dpkg-reconfigure fixed that) and my wireless driver (forget how I fixed that...), and my sound. ALSA still thinks I have an output device, I've set volumes all the way up in alsamixer.
In vlc and firefox, I can't hear anything using the default audio out (which I think is pulseaudio), nor can I hear anything if I ask them to use ALSA output directly. I've tried rebooting, killing/manually starting pulseaudio, etc to no avail.
I think it was either the kernel upgrade (went from 3.10 to 3.13) or a configuration option in some sound subsystem that broke. To be clear, sound was working perfectly before the upgrade. My machine is an Ivy Bridge-era Zenbook.
Original disk: XP NTFS primary Linux / ext4 logical Linux /home ext4 logical Win 7 NTFS logical NTFS data logical swap space NTFS recovery partition
I tried to install linux, as there was a problem with XP overwriting grub, I chose write grub to /dev/sda8 (which is where the linux install was appearing earlier).
I guess this borked the filesystem somehow. Now the NTFS data partition and the swap space are appearing as one free space. Well actually before that some linux live CDs (including gparted were seeing the entire drive as unpartitioned). I had to go into XP and delete the /ext4 partitions.
Is there any way for me to recover the NTFS data partition ?
but I know a fair amount about the OS. I really like openSuSE, and I was trying to install 11.2 on my laptop, completely blank hdd. It installed just fine;I used the default options (the partition scheme was /boot, swap, root, /home) and started thesktop without a hitch. However, when I restarted, my BIOS would not even recognize an OS on the hard drive. I was also unable to boot using the installation DVD. I tried to use the repair feature, and I would either get a message saying that the boot loader was corrupt,d could not be repaired, or that the package database didn't match the version of openSUSE installed. I've tried re-installing multiple times, all with the same results. I have tried different partition schemes and I've tried different booting settings, such as enabling boot from root or /boot partition
I am new to Opensuse, I used Fedora for more than a year and installed OS 11.4 64bit to experience the awesome KDE that Opensuse offers. I added KDE 4.6 Stable: Index of /repositories/KDE:/Release:/46/openSUSE_11.4/x86_64 It worked fine since the install(I installed 11.4 this Saturday), suddenly yesterday I don't remember what I did, KDE stopped working. What happens is I login using kdm, then all the stuff loads up but when I try to open anything the whole KDE freezes. If I clicked the launcher on bottom bar it opens only at the beginning, then if I press anything inside the launcher things freeze. Then even the launcher freezes too.I rememeber doing 2 things I did before restart:1) I did sudo zypper dup2) I changed my theme to Qtcurve gtk look. I thought the problem might be because of the QTCurve theme and even uninstalled using alt+f2 command line restarted, no change
I have made the mistake of installing windows XP on one of my drive after I've upgraded to opensuse 11.3 on my other drive. Now, my computer is always booting to XP and doesn't load Grub anymore... I guess I should have seen it coming I previously had similar problems with my boot loader which I could resolve using the Repair boot loader utility distributed with the installation DVD. Apparently, this utility is not distributed anymore with opensuse 11.3... so I'm a little lost. I'd like a bit of advise before I start messing with Yast / boot loader and potentially break everything.
My system is setup as follows: sda is partitioned into sda1 (swap), sda2 (root / in ext4), sd3 (/home in ext3) and sd4 (/windows/F in NTFS containing virtual machines) sdb is partitioned into sdb1 (my Windows XP install in NTFS) and sdb2 (another storage drive in NTFS).
Problem: xsane recognizes my scanner, but when I try to "Acquire Preview" or scan it doesn't do anything. It's like it can't communicate with the scanner. It waits till I click cancel.Sane is setup correctly - I tried skanlite and it works just fine
I recently upgraded to 11.3 and must say am highly disappointed. Between the multitude of problems, and sudden lack of long standing tools ( Sax2, system repair, loss of functionality in software installer), this to me has been a major step backward.
Now I have found out Samba as well has stopped working, sort of. I can still copy from windows share to my Suse box, however copying from Suse to the windows share now results in an error, the details for which just say invalid argument. Also note there are no logs in /var/logs/samba so I don't really have a clue whats happening.
My java-plugins stopped working. I can'tlog on to my webbank and Danish authorities without it. I've tried in Google Chrome, Konqueror, Firefox and Opera. None of them works. All browsers report that java is enabled. According to yast2 I have: