FireWire/Hard Drive Suse 8.1

[kimbermatic]

Here are my details and issues I am having with Suse 8.1 and firewire:

Dell 8100
Pentium 4
1.3 mhz
256 Meg Memory
Dual Boot
60 Gig Hard Drive - Linux Only
20 Gig Hard Drive - Windows
CD-R Plextor
CD
Firewire with 100Gig Hard drive attached with 3 partitions Fat32
CF Card Reader USB
Zaurus USB


I did a fresh install with 8.1. Everything seems to be working. The one thing
for now that I am trying to do is access my Fat32 partitions via firewire. I can
see the drives as sdc5-7. However when I try to mount them I recieve the
following error:

"Called: mount/dev/sdc5 mount:/dev/sdc5 is not a valid block device"

In looking at my boot.msg log and other warning logs I see errors in regards to
Modprobe "modprobe: modprobe: Can't locate module block-major-8" followed by the message above "mount: /dev/sdc5 is not a valid block device"

I searched the database at Suse and only found reference to a modprobe with
sound card issue.

Any help would be appreciated

[mdwatts]

I found the following with a quick G4L search for 'mount firewire drive"


firewire external disk
I have a script /sbin/fireup, that is:

insmod ieee1394
insmod raw1394
insmod ohci1394
# insmod sbp2
mount -t ext2 /dev/sda1 /mnt/fire

There is /mnt/fire directory, where the fire-wire disk is mounted. Watch out for insmod sbp2. That was required for kernel 2.4.7-10 (Redhat 7.2). On the other hand, on 2.4.18-3 (Redhat 7.3), it has made the system freeze so I removed it. I am not sure what is going on... My 80 Gbytes and 120 Gbytes external hard disks are working perfectly.


Plenty more hits from those search results.

[kimbermatic]

Thanks for your assistance, thought I would let you know how it was fixed.

Well my Speedzter firewire drive is finally working, but I am confused. Let me start from the beginning.

Followed all the helpful directions from everyone, but I could not get by "Not Valid Block Device" error. Then I did something that all my years of Admin training tells you not to do. I booted my machine without turning on my firewire drive prior to booting. Once I was logged on as a non-root user I turned my firewire drive on. Then just clicked on my shortcut to the drive and bingo bango there it was and accessible. :D

But I am really confused is this normal in the linux world? Is it I still have some issues, but by waiting till I am logged on I have circumvented the issue? I have re-created this in root mode and user mode.

Bottom line the drive is working, very, very happy... just lost as to why... nothing new there.