Click to See Complete Forum and Search --> : Cant Access other linux hard drive.


JesterDev
08-08-2003, 10:47 PM
Well my work requires me to use windows, and I didnt patch it in time for that stinkin exploit that seems to be getting attacked. Well it hit me, and completly screwed my windows install. I had to format my drive, which was sort of good, cause now I can use less disk space fow windows.. So now I have 2 hard drives, one 120 gig, with 10 gigs for windows and the rest for Linux.

The other 60 gig drive was used for Linux before. It's still there but I cant get to it! I didnt touch this drive at all. I need access to it so I can get my files from it, but it doesnt show up anywhere.

Is there a way I can get access to this drive from my new Linux install?

Hayl
08-08-2003, 10:52 PM
mount it

JesterDev
08-08-2003, 10:58 PM
I would if I could find it. It doesnt show up in my /mnt dir.
And I dont know what it would be called.

Hayl
08-08-2003, 11:01 PM
what hard disk is it?

hda1, hda2, hda3 , hdb6, you don't say in your post.

it doesn't matter if it's not under /mnt. you can jsut create a directory to mount it under there.

jlmb
08-08-2003, 11:12 PM
Originally posted by JesterDev
The other 60 gig drive was used for Linux before. It's still there but I cant get to it! I didnt touch this drive at all. I need access to it so I can get my files from it, but it doesnt show up anywhere.

Is there a way I can get access to this drive from my new Linux install?

Assuming the other drive if your primary master /dev/hda, the other got to be /dev/hdb or /dev/hdc . I can't tell since i don't know how you computer it set up. (hda is primary master, hdb is primary slave, hdc secondary master and hdd is secondary slave).

As Hayl wrote, just create a dir (mkdir) under /mnt and mount your /dev/hdX there.

serz
08-08-2003, 11:14 PM
Create a dir for the hd you want to mount.. lets say:

# mkdir /mnt/linux2
# mount /dev/hd? /mnt/linux2

That's all.

JesterDev
08-08-2003, 11:21 PM
Thanks for the help. /mnt the drives showing are win_c
and win_c2. win_c is my 120gig with a 10 gig partition for windows. And win_c2 is a 2 gig partition on the second drive. The old linux install is on the second dive. So the re remaining 58 gigs that I need to get to would be hdc. ?? Well I'll soon find out.
Thanks again,
JesterDev

jlmb
08-08-2003, 11:29 PM
Frankly I didn't understand the win_c# thing. I guess is the name of the dir where the partitions are mounted.

Hope it works for you.

JesterDev
08-08-2003, 11:31 PM
Ok so it seems to be hdc but when I try:

mount /dev/hdc /mnt/linux2

I get this

/dev/hdc: Input/output error
mount: you must specify the filesystem type

So how would I specify the filesystem type?
It's Mandrake Linux.

Sorry for all the trouble.
JesterDev

serz
08-08-2003, 11:43 PM
mount -t ext3 /dev/hdc /mnt/linux2 ?

JesterDev
08-08-2003, 11:53 PM
I dont know.. That didnt work either. Turns out its hdb7..

mount -t ext3 /dev/hdb7 /mnt/LinuxOther
mount: wrong fs type, bad option, bad superblock on /dev/hdb7,
or too many mounted file systems

I mounted hdb6 first thinking that might be it, but it seems to be where lilo was. So I made another dir and tried to mount it there(LinuxOther).

Well either way.

jlmb
08-09-2003, 12:17 AM
You are trying to guess which partition you have?

cfdisk /dev/hda
or
cfdisk /dev/hdb
or
cfdisk /dev/hdc
or
cfdisk /dev/hdd

Look at the partitions on each disk. That way you know what you have.

-----------
Just look, do not delete/edit anything since you can mess your installations

Kionon
08-14-2003, 06:54 PM
I'm having very similar problems and I've tried everything so far in this thread. However, the other harddrive worked fine with this set up for quite a while. Then I had some OS problems among other things, and now it doesn't work. The error message I get is:


Aug 13 15:54:31 Usagi kernel: hdb:hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
Aug 13 15:54:31 Usagi kernel: end_request: I/O error, dev 03:40 (hdb), sector 0
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=0, sector=0
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
Aug 13 15:54:31 Usagi kernel: end_request: I/O error, dev 03:40 (hdb), sector 0
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 13 15:54:31 Usagi kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
Aug 13 15:54:31 Usagi kernel: end_request: I/O error, dev 03:40 (hdb), sector 0
Aug 13 15:54:31 Usagi kernel: unable to read partition table

Like the other poor fellow, I cannot afford to lose the information on this harddrive. There are things like my novel and several video editing projects stuck on that drive.

EDIT: Oh yeah, since you guys like this: I'm reading just about everything I can that I can find on google. Seems like a fairly common error, unfortunately, even after running Linux since 1998... this stuff is going way over my head.

bandwidth_pig
08-14-2003, 07:26 PM
Just for grins, modify your /etc/fstab with the appropriate device name like so:

/dev/hdXX /mountpoint ext2 defaults

Of course, /dev/hdXX...XX being whatever device name and /mountpoint being wherever you want to mount it after you have made that directory. I had a similar problem once. Turns out I was just passing the wrong options to mount. But this worked for me.

Kionon
08-14-2003, 07:28 PM
All right, I'll see what I can do. My current fstab looks like this:

root@Usagi:/# more /etc/fstab
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda1 / ext2 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
# partitions found by Knoppix
#/dev/hda1 /mnt/hda1 ext2 noauto,users,exec 0 0
#/dev/hda3 /mnt/hda3 ext3 noauto,users,exec 0 0
#/dev/hda6 /mnt/hda6 ext3 noauto,users,exec 0 0
#/dev/hdb /mnt/hdb auto noauto,users,exec 0 0

EDIT: Okay, that doesn't seem to be working. And I don't have the necessary information anyway. There are several partitions on that harddrive, and frankly, I don't have any idea which is which.

Kionon
08-19-2003, 12:53 AM
Okay, folks. I normally use knoppix, now, I tried to run the RH install just to see if it could pull up a partition table. It couldn't. In fact it told me that in order to put any data on that disk I'd have to initialize it, which meant that it would destroy all data.

Is my harddrive dead and the data lost? (My God, how do I deal with that much loss of information... It would be devastating)

And if it isn't just completely lost, what are my chances of having a professional recover the data?

JesterDev
08-19-2003, 05:29 PM
I am no hardware wizard but if your drive is no good, I can tell you that I had a simular problem about a year ago. I sent my hard drive in, and they where able to recover the data. It was a western digital and luckily it was still under warranty. Even it its no longer covered they will do it, but for a fee.

Have you tried installing Linux on another drive and then try to mount it from there?

I would say that when a drive is fried it wouldnt even boot. At least that's what's happened to me. So I "think" your data is safe. But like I suggested you should try and mount it from another install if possible.

Sorry if I miss understood your problem. Just trying to help like the others helped me. :)

JesterDev

Kionon
08-20-2003, 02:03 PM
I was actually planning to take it to a place to recover it anyway. And linux is on the other harddrive. It mounts it as /mnt/hdb. However, I cannot access any of the information on the drive. I'm pretty sure there's something seriously wrong, I'll just have the data recovered to be safe, and then I'll reformat the drive.