LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Can't mount to external firewire drive (https://www.linuxquestions.org/questions/linux-hardware-18/cant-mount-to-external-firewire-drive-534546/)

jonthelam 03-04-2007 03:44 PM

Can't mount to external firewire drive
 
I was able to mount this drive (2 partitions) for a couple of years until recently. I get the following error when I try to mount to the first partition of the drive "mount: /dev/sda1 is not a valid block device" as well as "mount: /dev/sda2 is not a valid block device" for the second partition.

/var/log/message:

Quote:

Mar 4 12:49:13 computer kernel: ieee1394: sbp2: Logged out of SBP-2 device
Mar 4 12:51:01 computer kernel: ieee1394: Node 0-01:1023 has non-standard ROM format (0 quads), cannot parse
Mar 4 12:51:02 computer kernel: ieee1394: Node 0-00:1023 has non-standard ROM format (0 quads), cannot parse
Mar 4 12:51:10 computer kernel: ieee1394: sbp2: Logged into SBP-2 device
/var/log/syslog:

Quote:

Mar 4 12:51:10 ghost kernel: ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
dmesg:

Quote:

ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node removed: ID:BUS[0-00:1023] GUID[0030e0f4e020f904]
ieee1394: sbp2: Logged out of SBP-2 device
ieee1394: Node 0-01:1023 has non-standard ROM format (0 quads), cannot parse
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node 0-00:1023 has non-standard ROM format (0 quads), cannot parse
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e0f4e020f904]
I've already tried to restart the system and reset the firewire cable and no dice. I'm running Slackware 10.0 with kernel 2.4.26. Could it be the firewire cable?

jonthelam 03-04-2007 04:39 PM

I fixed it!
 
Running a script to rescan scsi bus fixed it after a reboot.

You can Google for rescan-scsi-bus.sh to get a copy of the script.


All times are GMT -5. The time now is 11:10 PM.