LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-08-2013, 01:14 PM   #1
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Rep: Reputation: 40
Wife's laptop won't boot. Error superblock probe failed.


Code:
(swapper,1,1):ocfs2_fill_super:1039 ERROR: superblock probe failed!
VFS: Cannot open root device "sda1" or unknown-block(8,1)
Please append a correct "root=" boot option; here are the available partitions:
0800     244198584 sda  driver: sd
  0801      9767488 sda1 00000000-0000-0000-0000-000000000000
  0802     19535040 sda2 00000000-0000-0000-0000-000000000000
  0803      3903795 sda3 00000000-0000-0000-0000-000000000000
  0804    210989677 sda4 00000000-0000-0000-0000-000000000000
0b00      1048575 sr0 driver; sr
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Pid: 1, comm: swapper Not tainted 2.6.37.6 #3
Call Trace:
 [<ffffffff81aa1ff6>] panic+091/0x194
 [<ffffffff81aa213a>] ? printk+041/0x43
 [<ffffffff821100c9>] mount_block_root+0x1d4/0x288
 [<ffffffff82110355>] mount_root+0x8a/0xa4
 [<ffffffff821104c9>] prepare_namespace+0x170/0x1a9
 [<ffffffff8210fe26>] kernel_init+0x1d2/0x1e2
 [<ffffffff810037d4>] kernel_thread_helper+0x4/0x10
 [<ffffffff8210fc54>] ? kernel_init+0x0/0x1e2
 [<ffffffff8100370d>] ? kernel_thread_helper+0x0/0x10
This started randomly, I had not done any upgrades or changes. I have since tried reloading slackware from disk with no change. Lilo would not write to the mbr at the end of setup. sda1 is the root partition, sda2 is /usr, sda3 is the swap, and sda4 is /home. I'm out of ideas at this point and looking for some help.

Thanks in advance,
Eric
 
Old 09-08-2013, 01:31 PM   #2
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Original Poster
Rep: Reputation: 40
trying to boot from a usb disk with /dev/sda1 as root produces the same panic. I formated that partition when I when through the reinstall process and ran a check at the same time so I don't think there is a physical problem with the disk.
 
Old 09-08-2013, 01:47 PM   #3
Raveriux
Member
 
Registered: Jul 2013
Location: Lithuania
Distribution: Slackware64 14, Slackware64 -current, Maemo
Posts: 75

Rep: Reputation: Disabled
maybe you have added usb disk when booting or sd card in reader?
 
Old 09-08-2013, 01:59 PM   #4
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Original Poster
Rep: Reputation: 40
There was a sd card in the reader which has never been a problem before. I removed it and tried to boot with the same result. Still kernel panic.
 
Old 09-08-2013, 02:45 PM   #5
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.0 64-bit
Posts: 228

Rep: Reputation: 41
Might be a problem with your 2.6 kernel? Try to reinstall it from the disk, and look here:

http://www.clearfoundation.com/compo...view/id,46626/
 
Old 09-08-2013, 03:29 PM   #6
saulgoode
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 231

Rep: Reputation: 98
I experienced a similar problem about a year ago with my tower PC, except that I was still able to boot from USB drives. What had happened in my case was that the motherboard's SATA controller had gotten confused owing to a faulty cable connection on one of the drives and, even after fixing the cabling, would not properly access the root drive.

Yes, I know that such problems should not theoretically happen, or at least should be recoverable by resetting the BIOS to its defaults; however, resetting the BIOS didn't fix things. Fortunately, I was able to remedy the problem by re-flashing the BIOS (booting the BIOS updater from a USB-connected DVD).

I only mention this as a last resort possibility to consider if all else fails (and assuming you have a means of re-flashing the BIOS).
 
Old 09-08-2013, 03:47 PM   #7
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Original Poster
Rep: Reputation: 40
This problem started on a 3.6.10 Kernel that was working fine. I backtracked to the standard kernel in hopes that it would boot.
 
Old 09-08-2013, 06:14 PM   #8
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Original Poster
Rep: Reputation: 40
I ran systemrescuecd and gparted did not recognize any filesystem on sda1 even though I reformatted it during the reinstall. I used gparted to set it back to ext4. I'm going to try the reinstall again.
 
Old 09-08-2013, 06:36 PM   #9
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,224

Rep: Reputation: 1019Reputation: 1019Reputation: 1019Reputation: 1019Reputation: 1019Reputation: 1019Reputation: 1019Reputation: 1019
As suggested, start looking at hardware. If it was always ext4, why does the kernel think it's OCFS2 ?, Seemed like an unlikely choice for a laptop.
 
Old 09-08-2013, 07:20 PM   #10
em21701
Member
 
Registered: Feb 2008
Location: Rhode Island, USA
Distribution: Slackware12.2 & Slackware64-13
Posts: 247

Original Poster
Rep: Reputation: 40
Letting gparted do the formatting seems to have done the trick. Not really sure why the slackware installer couldn't get it done but wither way it's working now. Thanks for the ideas all.

Eric
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Debugging : probe failed with error -16 barunparichha Linux - Software 1 01-20-2012 02:35 AM
nvidia co-processor probe failed with error -1 potuz Linux - Hardware 2 02-20-2010 11:07 PM
probe of 0000:02:04.0 failed with error -5 shogun1234 Linux - Wireless Networking 2 10-06-2007 01:03 AM
superblock probe failed Cavka Debian 5 10-01-2007 11:16 AM
kernel: vesafb: probe of vesafb0 failed with error -6 Toadman Mandriva 0 05-28-2005 09:13 PM


All times are GMT -5. The time now is 10:46 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration