Find the answer to your Linux question:
Results 1 to 9 of 9
I can't get into my desktop. I'm just getting comfortable with linux... Here's what I have when I boot up doing fast boot Creating device nodes with udev udevd[294]: failed ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25

    Can't Boot SuSE 12.1 x64


    I can't get into my desktop.
    I'm just getting comfortable with linux...
    Here's what I have when I boot up

    doing fast boot
    Creating device nodes with udev
    udevd[294]: failed to execute ' /etc/sysconfig/network/scripts/ifup-sysctl' '/etc/sysconfig/network scripts/ifup-sysctl lo -o hotplug' : No such file or directory

    Trying manual resume from /dev/sdb1
    Invoking userspace resume from /dev/sdb1
    resume: libcrypt version: 1.5.0
    Trying manual resume from /dev/db1
    Invoking in-kernel resume from /dev/sdb1
    Waiting for device /dev/sda2 to appear: ok
    fsck from utiil-linux 2.20.1
    [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a -C0 /dev/sda2
    fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2 /dev/sda2:
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid then blah blah blah...try running e2fck -b 8193 <device>

    fsck failed. Mounting root device read-only.
    Mounting root /dev/sda2
    mount -o ro,acl,user_xattr -t ext4 /dev/sda2 /root
    [3.882787] EXT4-fs (sda2): VFS: Can't find ext4 filesystem
    mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error. In come cases useful info is found in syslog - try dmesg | tail or so

    could not mount root filesystem -- exiting to /bin/sh
    sh: cannot set terminal process group (-1): Inappropriate ioctl for device
    sh: no job control in this shell

    $e2fsck -f /dev/sdb1
    sh: command not found

    cat /etc/fstab
    /dev/sda2 / ext4 defaults 1 1

    dumpe2fs /dev/sda1 | grep -i superblock
    sh: dumpe2fs: command not found

    I spent the whole day at work between phone calls looking up what a superblock is and some insight into the linux filesystem which is some pretty neat stuff, but my main problem here is...I don't have a /bin/bash shell, hence not being able to execute these diagnostic commands?

  2. #2
    Linux Guru
    Join Date
    Oct 2007
    Location
    Tucson AZ
    Posts
    3,102
    Is this a new installation? Have you been able to boot it successfully at all? If so, what changes were made immediately prior to this happening?
    What's on sdb1? Is Suse the only operating system you have? Did you run fsck as root user?

  3. #3
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25
    Hello yancek,

    It's a new install.
    I've had it running before.
    I put a second HDD in there (NTFS).
    No OS on this second HDD.
    After that it came to this screen.
    I haven't tried running as root but I'll try that tonight after work.
    SuSE is the only one on here.
    And I haven't tried

  4. #4
    Linux Guru
    Join Date
    Oct 2007
    Location
    Tucson AZ
    Posts
    3,102
    The most commone reason for getting the "command not found" error is trying to run a command as a normal user which requires root privileges.
    Did you create a separate /boot partition during the installation? or just the / and swap? You might run the "fdisk -l" command (without quotes, uppercase L in command) to get partition/drive information to post

  5. #5
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25
    Quote Originally Posted by yancek View Post
    The most commone reason for getting the "command not found" error is trying to run a command as a normal user which requires root privileges.
    Did you create a separate /boot partition during the installation? or just the / and swap? You might run the "fdisk -l" command (without quotes, uppercase L in command) to get partition/drive information to post
    Yeah that would make sense...because the sbin commands aren't in my PATH if I'm not root. I'll try sudo and see how that goes.

  6. #6
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25
    And I configured my system with:
    100 MB /boot
    60 GB /
    32 GB swap
    I believe I have 30 GB /var and the rest of the 1 TB for /home

  7. #7
    Linux Guru
    Join Date
    Oct 2007
    Location
    Tucson AZ
    Posts
    3,102
    32GB for swap is way too much. Even if you have limited RAM, 2GB should be enough.
    Did you configure sudo on your Suse install? It is not enabled by default on Suse. Just use su and.

  8. #8
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25
    Quote Originally Posted by yancek View Post
    32GB for swap is way too much. Even if you have limited RAM, 2GB should be enough.
    Did you configure sudo on your Suse install? It is not enabled by default on Suse. Just use su and.
    Alright, so:
    su
    Command not found.

    ls /sbin:
    blkid blogd fsck fsck.ext4 halt ifup insmod killall5 modprobe pidof reboot resume showconsole udevadm udevd

    On my other SuSE box I have quite a few more commands in /sbin!

    I could always blow this drive away considering I just finished downloading the new 12.2

    And I forgot to mention that the /swap is actually the only partition on a separate physical disk.

  9. #9
    Just Joined!
    Join Date
    Aug 2012
    Posts
    25
    Well I just wiped everything out and am waiting for 12.2 to finish.
    I'm not sure what caused this to happen in the first place.
    The computer was never shut off abruptly.
    I've only had it running for a few days.
    I did put a second SATA in there (NTFS) just data, no OS...
    Strange how I only had just a small list of commands available in /sbin though...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •