multible partitions?
Hello, I've got a debian box with kernel 2.4.27 acting as a video disk recorder. There are precompiled modules for hfsplus and hfs. When I try to mount my external firewire disk (3 partitions, 160 GB) mount /dev/sda1 -t hfsplus /hfs I get various error messages - depending whether a USB stick was attached/removed before. The USB stick formatted as hfsplus mounts easily, so I got the idea that the partitions make the problem. I dont know how I can adress various partitions... - or are multible partition disks not yet supported? - All partitions are HFS+. Any advice would be appreciated! Thanks and greetings, Wolf -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Re: multible partitions?
I've got a debian box with kernel 2.4.27 acting as a video disk recorder. There are precompiled modules for hfsplus and hfs. When I try to mount my external firewire disk (3 partitions, 160 GB) mount /dev/sda1 -t hfsplus /hfs I get various error messages - depending whether a USB stick was attached/removed before. The USB stick formatted as hfsplus mounts easily, so I got the idea that the partitions make the problem. I dont know how I can adress various partitions... - or are multible partition disks not yet supported? - All partitions are HFS+. Any advice would be appreciated! Thanks and greetings, Wolf I know personally that I use multiple partitions on my internal HD so I'd imagine they are supported, as to what that issue is, I don't know, but I can tell you with 99 percent certainty it is not because of multiple partitions. Hello, thanks for that hint. Can You let me know: * How do You find out which devices (/dev/) You can mount? * Which commands do You use to adress the various partitions? Thanks and greetings, Wolf -- +++++++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
subscribe
-- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Re: multible partitions?
On Friday 03 June 2005 18:34, Wolf Drechsel wrote: I get various error messages - depending whether a USB stick was attached/removed before. The USB stick formatted as hfsplus mounts easily, so I got the idea that the partitions make the problem. Including these error messages would be a good place to start. Ok, here we go: When I just attach the disk, the IEEE 1394 modules are loaded. Doing a mount /dev/sda1 -t hfsplus /hfs leads to: mount: /dev/sda1 is not a valid block device. Attaching, mounting, demounting and deattaching a USB stick - and then trying to mount the HDD again leads to a more complex result, like this: mount /dev/sda1 -t hfsplus /hfs sda: Unit not ready, sense: Info fld=0xa00 (nonstd), Current ... Raw sense data: . sda: READ CAPACITY failed ... ... ... sda: block assumed to be 512 bytes, disk size 1GB sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 sda: I/O error: dev 08:00, sector 2097144 sda: I/O error: dev 08:00, sector 2097144 sda: I/O error: dev 08:00, sector 0 sda: I/O error: dev 08:00, sector 0 unable to read the partition table mount: /dev/sda1 is not a valid block device. "." meant more output, as a mount /dev/sda1 -t hfsplus /hfs >& /tmp/hfsmountoutput didnt make a reasonable file (how do I do that correctly?), I had to copy all from the screen and left out the less important looking. I hope these are enough data - if it is required more detailed, please give me a hint how I can get the whole output of "mount" into a file". Thanks and greetings, Wolf PS.: Kernel 2.4.27, i386-platform -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Re: multible partitions?
Hi Wolf, On Sat, Jun 04, 2005 at 01:18:03PM +0200, Wolf Drechsel wrote: "." meant more output, as a mount /dev/sda1 -t hfsplus /hfs >& /tmp/hfsmountoutput didnt make a reasonable file (how do I do that correctly?), I had to copy all from the screen and left out the less important looking. Probably these messages are emitted by the kernel and not by the mount program, so redirecting the mount output won't catch them. Try "dmesg" instead. This will show you all the kernel messages. Thanks for Your hint - I'll try that. For now (without a previously mounted USB stick) I just get: mount: /dev(sda1 is not a valid block device. BUT: I'm not sure I'm mounting the right device at all. There at least 14 slices on the disk - how can I use just "sda1". Below I add the information give by the Mac OS X disk utility - how do I find out how to mount correctly? Greetings, Wolf Name : 1394 to ide Typ : Medium Medien-Identifikation : disk2 Medienname :HDS72251 6VLAT20 Media Medientyp : Generic Verbindungs-Bus : FireWire Verbindungs-ID :460695372038243 IO-Inhalt : Apple_partition_scheme Gerätebaum :pci1/pci1106,[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/@0:0 Beschreibbar : Ja Auswerfbar :Nein Mac OS 9 Treiber installiert : Ja Ort : Extern Gesamtkapazität : 153,4 GB (164.696.555.520 Byte) Mediennummer : 2 Partitionsnummer : 0 Name : WD-HFS+ext2-8G Typ : Volume Medien-Identifikation : disk2s10 Mount-Point : /Volumes/WD-HFS+ext2-8G Dateisystem : Mac OS Extended (Journaled) Verbindungs-Bus : FireWire IO-Inhalt : Apple_HFS Gerätebaum :pci1/pci1106,[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/@0:10 Beschreibbar : Ja Kapazität : 7,9 GB (8.455.716.864 Byte) Freier Speicherplatz : 3,2 GB (3.432.030.208 Byte) Belegt :4,7 GB (5.022.900.224 Byte) Anzahl der Dateien :115.388 Anzahl der Ordner : 28.417 Zugriffsrechte aktiviert : Ja Zugriffsrechte ausschaltbar : Ja Zugriffsrechte reparierbar :Ja Überprüfbar : Ja Reparierbar : Ja Formatierbar : Ja Startfähig :Ja Journaling wird unterstützt : Ja Journaling :Ja Mediennummer : 2 Partitionsnummer : 10 Name : WD-HFS+ext1-8GB Typ : Volume Medien-Identifikation : disk2s12 Mount-Point : /Volumes/WD-HFS+ext1-8GB Dateisystem : Mac OS Extended Verbindungs-Bus : FireWire IO-Inhalt : Apple_HFS Gerätebaum :pci1/pci1106,[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/@0:12 Beschreibbar : Ja Kapazität : 7,9 GB (8.455.716.864 Byte) Freier Speicherplatz : 3,8 GB (4.040.282.112 Byte) Belegt :4,1 GB (4.415.434.752 Byte) Anzahl der Dateien :111.819 Anzahl der Ordner : 27.830 Zugriffsrechte aktiviert : Nein Zugriffsrechte ausschaltbar : Ja Formatierbar : Ja Startfähig :Ja Journaling wird unterstützt : Ja Journaling :Nein Mediennummer : 2 Partitionsnummer : 12 Name : WD_HFS-132G Typ : Volume Medien-Identifikation : disk2s14 Mount-Point : /Volumes/WD_HFS-132G Dateisystem : Mac OS Extended Verbindungs-Bus : FireWire IO-Inhalt : Apple_HFS Gerätebaum :pci1/pci1106,[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/@0:14 Beschreibbar : Ja Kapazität : 137,3 GB (147.381.526.528 Byte) Freier Speicherplatz : 136,8 GB (146.848.219.136 Byte) Belegt :496,8 MB (520.945.664 Byte) Anzahl der Dateien :3.041 Anzahl der Ordner : 334 Zugriffsrechte aktiviert : Nein Zugriffsrechte ausschaltbar : Ja Formatierbar : Ja Startfähig :Ja Journaling wird unterstützt : Ja Journaling :Nein Mediennummer : 2 Partitionsnummer : 14 -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Fwd: Re: multible partitions?
hi wolf i just want to warn you: i recently trashed a 160gb lacie d2 firewire harddrive with linux (see: http://lists.debian.org/debian-powerpc/2005/05/msg00464.html). if you wan't to mount hfsplus on linux do it read-only for now... Thanks for Your hint - are You a "single case" - or are there more such issues? now to your problem: mount /dev/sda1 -t hfsplus /hfs you don't specify the right partition. you can read the partition-number from the output of macos disk utility below, from the "Medien-Identifikation" label: e.g. "disk2s10" means partition 10 on disk 2, which could map to /dev/sda10 on linux. alternatively you can run "fdisk -l /dev/sda" in linux which prints the partition table of /dev/sda. Unluckily there is no output just running the command. Inserting my USB stick, than removing it leads to results - but they are not so friendly. Here comes dmesg stuff - a left the lines related to usb and FireWire, maybe this is of some use. The external disk issue is at the very ending: ohci1394: $Rev: 1045 $ Ben Collins <[EMAIL PROTECTED]> ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[e4104000-e41047ff] Max Packet=[2048] ieee1394: unsolicited response packet received - no tlabel match ieee1394: Node added: ID:BUS[0-00:1023] GUID[0001a363] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0001b700ac7d] usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.275 $ time 19:27:41 Oct 15 2004 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: USB UHCI at I/O 0x6000, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.275:USB Universal Host Controller Interface driver sbp2: $Rev: 1074 $ Ben Collins <[EMAIL PROTECTED]> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices blk: queue c11b0974, I/O limit 4095Mb (mask 0x) ieee1394: sbp2: Logged into SBP-2 device ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] ... ... ... ... ... Plugging USB stick in ... hub.c: new USB device 00:07.2-1, assigned address 2 usb.c: USB device 2 (vend/prod 0x58f/0x9380) is not claimed by any active driver. Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage usb-uhci.c: interrupt, status 2, frame# 1377 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Generic Model: Flash DiskRev: 7.77 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 SCSI device sda: 128000 512-byte hdwr sectors (66 MB) sda: Write Protect is off sda: sda1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. ### ... and out: usb.c: USB disconnect on device 00:07.2-1 address 2 ... ... ... ... HERE IT COMES: fdisk -l /dev/sda sda: Unit Not Ready, sense: Info fld=0xa00 (nonstd), Current 00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 Info fld=0xa00 (nonstd), Current sd00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table Greetings, Wolf -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Re: multible partitions?
Unluckily there is no output just running the command. Inserting my USB stick, than removing it leads to results - but they are not so friendly. Here comes dmesg stuff - a left the lines related to usb and FireWire, maybe this is of some use. The external disk issue is at the very ending: possibly you still don't specify the right disk/partition. the device node files are constructed like this: /dev/sdXY, where X is a disk character and Y is the partition number. if the usb-driver mounts a drive on /dev/sda it's possible that your firewire drive is in /dev/sdb. Hm. I'm sure I tried nearly every reasonable combination. What makes me wonder: When I just plug in the FireWire disk, nothing happens, even not fdisk -l /dev/sda fdisk -l /dev/sdb fdisk -l /dev/sdc Only plugging and unplugging a USB stick makes it providing error messages. Does the USB environment provide something the FireWire needs? I'll try to attach the disk now on the USB port. Unluckily I cannot find my USB cable at the moment. Greetings, Wolf ohci1394: $Rev: 1045 $ Ben Collins <[EMAIL PROTECTED]> ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[e4104000-e41047ff] Max Packet=[2048] ieee1394: unsolicited response packet received - no tlabel match ieee1394: Node added: ID:BUS[0-00:1023] GUID[0001a363] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0001b700ac7d] usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.275 $ time 19:27:41 Oct 15 2004 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: USB UHCI at I/O 0x6000, IRQ 11 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.275:USB Universal Host Controller Interface driver sbp2: $Rev: 1074 $ Ben Collins <[EMAIL PROTECTED]> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices blk: queue c11b0974, I/O limit 4095Mb (mask 0x) ieee1394: sbp2: Logged into SBP-2 device ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] ... ... ... ... ... Plugging USB stick in ... hub.c: new USB device 00:07.2-1, assigned address 2 usb.c: USB device 2 (vend/prod 0x58f/0x9380) is not claimed by any active driver. Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage usb-uhci.c: interrupt, status 2, frame# 1377 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Generic Model: Flash DiskRev: 7.77 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 SCSI device sda: 128000 512-byte hdwr sectors (66 MB) sda: Write Protect is off sda: sda1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. ### ... and out: usb.c: USB disconnect on device 00:07.2-1 address 2 ... ... ... ... HERE IT COMES: fdisk -l /dev/sda sda: Unit Not Ready, sense: Info fld=0xa00 (nonstd), Current 00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 Info fld=0xa00 (nonstd), Current sd00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table Greetings, Wolf -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++ -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
Fwd: Re: Fwd: Re: multible partitions?
Here's where the firewire core code loads the SCSI transport driver to present firewire disks as SCSI disks: sbp2: $Rev: 1074 $ Ben Collins <[EMAIL PROTECTED]> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices blk: queue c11b0974, I/O limit 4095Mb (mask 0x) and attaches one firewire disk to the SCSI transport: ieee1394: sbp2: Logged into SBP-2 device ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] What's missing here is crucial: there should be a SCSI device registered here, usually sda. Not having anything SCSI related here is odd. What happens in the kernel log when you try a mac-fdisk -l /dev/sda at this stage? Unluckily I just have cfdisk, fdisk and sfdisk, but not the mac-fdisk. The first mentioned ones do not produce any output. Did you unplug or power down the firewire disk in between? Yes, I tried "resetting" by unplugging, replugging and powering down several times. >Vendor: Generic Model: Flash DiskRev: 7.77 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 SCSI device sda: 128000 512-byte hdwr sectors (66 MB) sda: Write Protect is off sda: sda1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. and found the first 'SCSI' device ever in the system. Which is odd, because the firewire sbp2 driver ought to have located your firewire disk before, making this one sdb. I checked USB stick and FW drive at the same time. When the stick is attached and mounted: fdisk -l /dev/sda shows the usb stick, fdisk -l /dev/sdb gives no output So the FW disk seems to be ignored completely. > ### ... and out: > > usb.c: USB disconnect on device 00:07.2-1 address 2 Might be interesting to see what usb-storage has to tell here - deregistering the sda1 disk perhaps. Or maybe it got automatically mounted and not hasn't been unmounted yet (check the output of 'mount' before unplugging it). Yes - here I unplugged the USB stick. > > HERE IT COMES: > > fdisk -l /dev/sda > sda: Unit Not Ready, sense: Info fld=0xa00 (nonstd), Current 00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 08 host=0 says it's looking on the firewire bus - though it doesn't say which SCSI ID was used. The READ CAPACITY command means the disk was detected as such before (in the section you omitted), just never tried to mount. Unit Not Ready means the disk might not be spun up (though the kernel usually figures that out and sends a START UNIT command) or not powered on yet. For the sbp2 logon to work, it might be sufficient to have the firewire interface on the disk box up and running. The rest is some bad guesses assuming the disk is up anyway, followed by read errors because it isn't. What's a bit odd here is how sda is used for both the USB and the firewire device - please double check the kernel doesn't keep the USB stick mounted or the partition data present after you unplugged it (check /proc/partitions for that before and after unplugging the stick)- Info fld=0xa00 (nonstd), Current sd00:00: sns = 70 2 Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00 sda : block size assumed to be 512 bytes, disk size 1GB. sda: test WP failed, assume Write Enabled sda: I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 2097144 I/O error: dev 08:00, sector 0 I/O error: dev 08:00, sector 0 unable to read partition table What kernel version does this happen on? Any difference if you plug in the firewire disk _after_ the kernel has booted up? The kernel is 2.4.27. I noticed no diffenence whether I plug before or after the system boot process. I've had occasional trouble with the firewire disk not detected on boot, but IIRC there never was a sbp2 logon either. Another strange thing: I read cat /proc/partitions: with the FW disk and USB stick attached - and then removed the USB stick. There was no change in output at cat /proc/partitions - exactly the same values, which IMHO are correct for the stick and not for the disk: cat /proc/partitions major minor #blocks name 8 0 64000 sda 8 1 63996 sda1 3 06336225 hda 3 16249253 hda1 3 2 80325 hda2 Meanwhile I suspect having a not really fully compatible ieee1394 chipset on my FW disk. - I'll try the USB port as soon as I can get hold of a USB cable. Thanks a lot for Your help up to now - it feels good not to be left alone in this
mounting...
Hello, I got a cable to mount my external disk on the USB-connector. This is bad style... - but works better than the FireWire thing: But now: After doing a mount -t hfsplus /dev/sda10/hfs or mount -o rw -t hfsplus /dev/sda10/hfs I get: HFS+-fs-warning: Filesystem was not cleanly unmounted, running fsck.hfsplus is recommended. mounting read-only I can read from this disk - but not write. How can I obtain fsck.hfsplus for a i386 debian (kernel 2.4.27) ? - It's not on my machine. Or is there another way of resolving this - mount -o rw,remount /dev/sda14 leaves the filesystem unmounted. Thanks and greetings, Wolf -- +++ + Wolf Drechsel + Köhnstr. 54 + D-90478 Nürnberg + Tel.: 0911/4 71 98 49 +++
