Solved

Kernel/Disk hackers only

Posted on 2000-04-17
2
287 Views
Last Modified: 2011-04-14
I have a 40G drive that I have been running under 2.2.14 and later for quite a while. Yesterday, I accidentially auto-mounted the drive under kernel 2.2.13.  Since it can't handle that large of a drive layout, it did lots of nasty things to my drive. (They scrolled by too fast to see) Now I've got lots of unknown filetypes, and directories that want to be files. For example:

?---------   0 root     root            0 Dec 31  1969 in

Under 2.2.13, fdisk thinks:

Disk /dev/hdc: 32 heads, 63 sectors, 6935 cylinders
Units = cylinders of 2016 * 512 bytes
   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             1     39703  40020592+  83  Linux native
Command (m for help): v
Total allocated sectors 80041186 greater than the maximum 13980960

My question is: When I go back to a sane kernel, is there a way to recover my information?

*Experts only, please*
0
Comment
Question by:dmag
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Accepted Solution

by:
kiffney earned 300 total points
ID: 2726929
Booting to the older kernel probably didn't do anything to your drive.  Just boot back to the newer kernel.  Booting doesn't change the master boot record or the partition table.  (Running 'lilo' does, but you didn't do that, right?)  It's possible that some of the files in  /var/log/ may be messed up.  But you should not do anything else under that kernel because you do run the risk of corruption if you write a bunch of files before you switch.  And when you do switch back, make sure to edit /etc/lilo.conf so that you can't boot to the old kernel any more.  

If you do have any problems, you can sometimes recover with 'debugfs'.  However, it's complicated and probably unnecessary, and if you fool with it when you don't need to, you could cause REAL problems.  So just boot back to 2.2.14 in 'single' mode, runs fsck, and if there are problems, post back here.
0
 
LVL 1

Author Comment

by:dmag
ID: 2745719
Hey, you were right. I thought it did nasty things to my drive..
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up Secure Ubuntu server on VMware 1.      Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions. 2.      Power on th…
The purpose of this article is to demonstrate how we can use conditional statements using Python.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

737 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question