Jump to content

Mandriva won't boot


kilimanjaro
 Share

Recommended Posts

Aloha Everyone

 

I am running mandriva 2008 on my laptop, and yesterday if refused to boot. It has been acting weird lately. I have been having trouble changing permissions on files, and putting music onto my ipod.

 

Yesterday it gave me this while trying to boot:

 

fsck.ext3: no such file or directory while trying to open /dev/sda5

/dev/sda5:

The superblock could not be read or does not describe a correct ext2 filesystem. If device is valid and it really contains ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>

 

/dev/hda6: clean, 116703/10682368 files, 20717953/21352385 [failed]

 

*** An error occured during the file system check.

*** Dropping you to a shell; the system will reboot

*** when you leave the shell

Give root password for maintenance

(or type Control-D to continue):

 

 

Anybody know what I should do now?

 

 

[moved from Software by spinynorman]

Link to comment
Share on other sites

@kilimanjaro: Please check my post again, I have edited it to show the correct drive.

 

If running e2fsck doesn't help you could try using a rescue cd to make repairs: http://trinityhome.org/Home/index.php?wpid=2&front_id=1

Edited by {BBI}Nexus{BBI}
Link to comment
Share on other sites

Have you done this?

 

e2fsck -b 8193 /dev/sda5

 

since /dev/sda5 was mentioning a bad superblock? And what were the results after running it? What did it say?

 

Also, what is the filesystem on /dev/sda5? Are you sure it's ext2 and not ext3? Or something else? Perhaps the config in /etc/fstab is badly configured because I've had errors generated before when it was listed wrong in /etc/fstab.

Link to comment
Share on other sites

Aloha Ian

 

So the response I got was:

 

"The superblock could not be read or does not describe a correct ext2 filesystem. If the device is 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 superblock: e2fsck -b 8193 <device>"

 

I tried it with both sda5 and hda6. I'm not sure what ext2 and ext3 are, so I don't know what it should be.

Link to comment
Share on other sites

ext2 and ext3 are similar, except ext3 has journaling whereas ext2 does not. Can you post/check the contents of /etc/fstab so we can see what your filesystem types are meant to be for these particular partitions.

Link to comment
Share on other sites

I wonder if there is a bug somewhere because I had a similar failure with mandriva a while back (during cooker 2008.1). I tried to get the filesystem going again but it was just too much work. Ubuntu detected no filesytem errors and could read everything just fine, so I backed up my files and whiped to disk and reinstalled.Reinstalling took me far less time than trying to figure out how to recover....

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...