VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: VL not recognizing hard drive  (Read 845 times)

rkonrad

  • Member
  • *
  • Posts: 79
VL not recognizing hard drive
« on: April 03, 2012, 10:06:09 am »

I'm not sure if I should be posting this here - but here it goes...

After numerous unsuccessful attempts at installing VL7 on my external hard drive, I finally figured things out (another topic) but the MBR got rewritten numerous times.  The MBR is on internal hard drive, sda1 and now it is unrecognized by VL as well as other distributions.  The disk is healthy as I had previously checked it with "badblocks".  Running fidisk, i discovered that the file system type had changed to  NTFS to HPFS/NTFS/exFAT.  ALL my data is on this drive and I need to access it.  The exFat entry is probably not correct but I thought if I could enable the kernel to recognize this format, maybe I stand some chance of getting at the data. 
Logged

M0E-lnx

  • Administrator
  • Vectorian
  • *****
  • Posts: 3234
Re: VL not recognizing hard drive
« Reply #1 on: April 03, 2012, 10:31:40 am »

two things here.  you speak of mbr and then you speak of sda1.  they are 2 completely different things.  you fan write thr mbr as many times as u want and you will not affect the data in sda1.  the mbr is the first 512 blocks of the drive, which is never touched by the os.  if you really did lose data, it was not by writing the mbr, but most likely formatting partitions or repartitioning.  at any rate, you should search for data recovery tools.   i have had some success in the past but cant remember what i used.

nightflier

  • Administrator
  • Vectorian
  • *****
  • Posts: 4107
Re: VL not recognizing hard drive
« Reply #2 on: April 03, 2012, 12:36:23 pm »

And right away: turn off computer and do not access drive! As M0E-lnx said, start researching rescue tools and live distros.
Logged