2 Hard Drives

[Rangerover]

I have a 250 GB Maxtor (master) as well as a 35 GB Seagate (slave). FC4's Hardware browser sees both drives but my question is How do I access the Seagate?? Can't see it in the file manager.

THX!

[ben s]

You need to partition it and lay a filesystem down before you can mount it. Something like (as root)...

"fdisk /dev/hdx" where x is the letter assigned to the drive (probably b). In fdisk, create one or more partitions (on such a small drive, you'll probably only want one).

"mkfs -t zzz /dev/hdxy" where zzz is the format type (probably ext3) and y is the partition number (probably 1). This will format the partition.

"mount /dev/hdxy qqqqq" where qqqqq is the mount point you want to assign to the drive. All drives in the UNIX filesystem paradigm are mounted somewhere under / (root). So, for example, if you wanted to put your home directories on the Seagate drive, you might say "mount /dev/hdb1 /home".

If you want the partition to be automatically mounted when you boot, you'll have to alter /etc/fstab. You can find out more about that by "man fstab". Come to think of it, "man fdisk", "man mkfs" and "man mount" might come in handy too!

[SlowJet]

What is on the 35 GB drive?

you need to mount file system (ext3, fat32) or LV on a LVM VG.

SJ

[SlowJet]

If it is empty then use LVM.

see link for FC4 LVM gui tool

http://forums.fedoraforum.org/showthread.php?t=67247

SJ

[Rangerover]

What is on the 35 GB drive?

you need to mount file system (ext3, fat32) or LV on a LVM VG.

SJ
The 35 GB drive is formatted Ext3.... with a lot of files. I used it with Mandrake 10.2 no problem. I just want to mount it read/write.

Thanks for your help!!!

[ben s]

The 35 GB drive is formatted Ext3.... with a lot of files. I used it with Mandrake 10.2 no problem. I just want to mount it read/write.

Thanks for your help!!!

Ok, assuming you want to mount it at /mnt/seagate and assuming it's /dev/hdb1:

mount -t ext3 /dev/hdb1 /mnt/seagate

Voila!

[Rangerover]

Thanks Ben.... when I try that I get an error message Not in fstab or mtab.

[tomcat]

Is the drive detected correctly by Fedora? And take a look at the jumpers.

[Rangerover]

Thanks for responding....Hardware Browser sees it correctly and the jumpers are set to cable select. I think if it were properly set up in fstab and mtab, I could mount it.

[tomcat]

Try editing your /etc/fstab adding the following line:
/dev/hdbX /mnt ext3 defaults 1 2
X= partition of the drive you want to access
Now reboot the system and see if it gets mounted or if you get error messages/timeouts

[Rangerover]

OK.....Whoops, "An error occurred during the file system check dropping you to a shell." It then asks me for root password and then goes to a prompt called "System Recovery #". From that prompt, I cannot edit fstab since it's read only?????

HELP!!!!

[Rangerover]

There's also a message about "bad magic number in superblock of hdb"

[tomcat]

Read only? For root? Please type at the command prompt "ls -l /etc/fstab" and verify this. If this is the case, use the chmod comand to make it writeable again. (chmod 664 /etc/fstab) Then edit fstab with e.g nano and uncomment the line you just added and reboot.

[Rangerover]

When I "ls -l /etc/fstab" I get "-rw-r--r-- 1 root root 854" and when I try to chmod that file it doesn't work. I think the prompt I'm getting is really not a truie root prompt and is very limited.

[bunsen]

as what did you log in at the prompt? root?

[Rangerover]

I was asked for a root password but the resulting prompt was titled "System Recovery #:"

[ben s]

OK. What's happened here is that you modified your fstab then tried to boot with an fstab entry that won't work for some reason. During boot, Fedora tries to run fsck on all the filesystems, but there's something wrong with with the drive or the fstab entry. Based on the error message "bad magic number in superblock of hdb", I'd say you made a mistake in your fstab entry and left out the partition number, or possibly specified a partition on hdb that doesn't exist.

Boot your machine from the first disc of your Fedora set and type "linux rescue" at the boot: prompt. When Anaconda asks if you want to detect your Fedora system, say yes. When it drops you to a prompt, you can edit the offending line out of your fstab file which should be at /mnt/sysimage/etc/fstab, then reboot and your system should come up normally.

Assuming you tried my mount command exactly as I specified it, "mount -t ext3 /dev/hdb1 /mnt/seagate", the error message you got shouldn't have occurred if the /mnt/seagate directory exists (if it doesn't, create it with the command "mkdir /mnt/seagate", then try the mount command again). When you specify a partition device node and a mount point, mount doesn't need an entry if fstab. Make sure the mount works correctly *before* you put it in fstab, then make sure it works from the fstab ("mount /mnt/seagate" -- mount will figure out the rest from the fstab entry) *before* you reboot!

[Iram Hernandez]

Make sure that that the partition with your information is actually /dev/hdb1. Depending on which ide channel you connected the drive to and how your disk partitions are laid out, it chould be different. Verify your parition info by running the command (as root):

/sbin/fdisk -l

This will list all the disks, partitions, and partition types.

[Rangerover]

OK, here's fdisk -l

[root@localhost /]# /sbin/fdisk -l

Disk /dev/hda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3187 25599546 83 Linux
/dev/hda2 3188 3952 6144862+ 83 Linux
/dev/hda3 3953 30515 213367297+ 83 Linux

Disk /dev/hdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 8923 71673966 83 Linux


I've tried to mount hdb1 numerous ways:

[root@localhost /]# mount -t ext3 /mnt/hdb1 /mnt/seagate
mount: special device /mnt/hdb1 does not exist
[root@localhost /]# mount -t ext3 /dev/hdb1 /mnt/seagate
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

[root@localhost /]# dmesg | tail
input: USB HID v1.11 Keyboard [Chicony USB Gaming Keyboard Pro] on usb-0000:00:02.2-2.1
input,hiddev96: USB HID v1.11 Device [Chicony USB Gaming Keyboard Pro] on usb-0000:00:02.2-2.1
input: USB HID v1.11 Gamepad [Chicony USB Gaming Keyboard Pro] on usb-0000:00:02.2-2.1
usb 2-2.2: new low speed USB device using ohci_hcd and address 25
input: USB HID v1.00 Mouse [0461:4d09] on usb-0000:00:02.2-2.2
usb 2-2.3: new low speed USB device using ohci_hcd and address 26
input: USB HID v1.10 Keyboard [No brand HA2 1.0] on usb-0000:00:02.2-2.3
drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint
usbhid: probe of 2-2.3:1.1 failed with error -5
VFS: Can't find ext3 filesystem on dev hdb1.


I think the issue boils down to this..... hdb1 is an LVM drive......but how do you access???

[ben s]

[root@localhost /]# mount -t ext3 /mnt/hdb1 /mnt/seagate
mount: special device /mnt/hdb1 does not exist

That won't work because /mnt/hdb1 is a mountpoint, not a device node. Mount requires you to specify one (and only one) device node and one (and only one) mount point. Read the mount man page for more info.

[root@localhost /]# mount -t ext3 /dev/hdb1 /mnt/seagate
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,

This means exactly what it says -- there's no ext3 filesystem on /dev/hdb1. That probably means it's not formatted.


I think the issue boils down to this..... hdb1 is an LVM drive......but how do you access???

There's no such thing per se as an "LVM drive". See the LVM HOWTO (http://www.tldp.org/HOWTO/LVM-HOWTO/) for more information on LVM.

To check to see if FC thinks that /dev/hdb1 is indeed part of an LVM volume group, issue (as root) "pvscan". It will give you info on any partitions marked as LVM physical volumes. You can then use vgscan to scan for volume groups and lvscan to scan for logical volumes. Logical volumes are the ones you mount.

[Rangerover]

We're getting closer:

root@localhost /]# pvscan
PV /dev/hdb1 lvm2 [68.35 GB]
Total: 1 [68.35 GB] / in use: 0 [0 ] / in no VG: 1 [68.35 GB]
[root@localhost /]# vgscan
Reading all physical volumes. This may take a while...
[root@localhost /]# lvscan
[root@localhost /]#

[ben s]

Sorry, your data is most likely toast. As I said in my earlier post, logical volumes are the ones you mount, hence the ones that have file systems. You have no logical volumes, hence no filesystems, hence, no data.