HFS-mounting stumper
OK, I've got a tricky question. I have a plain-old-vanilla hfs partition on one of my drives. For the last year, it's mounted *just fine* under SuSE. I've never been able to give anybody other than root write permissions to it, but since all I really use it for is storing mp3's (and the occasional Linux-MacOS file transfer), all anybody needs is read permissions. About a week ago, I had a whopper of a system crash, for reasons that I still haven't figured out. I was forced to do a hard-reboot. Since then, nobody except for root has been able to access my hfs partition. Anybody else gets a "permission denied" message. I've tried fiddling with /etc/fstab, I've tried chgrp and chown and chmod (both on the mount-point-directory and directly on the /dev/ object), nothing works. I'm practically tearing my beard out in frustration... it's probably something really obvious that's right in front of my face... any ideas? -SB -- "As an adolescent I aspired to lasting fame, I craved factual certainty, and I thirsted for a meaningful vision of human life -- so I became a scientist. This is like becoming an archbishop so you can meet girls." -- Matt Cartmill
Hi, I am having a problem with a SuSE 7.3 PPC server crashing when there is heavy IO on a specific drive (/dev/hdb1). This error happens when the drive is being used as the target while rsync'ing with another filesystem to mirror it once a night. Unfortunately the only data I have at this moment is some errors in the /var/log/boot.msg. The drive does mount the ext3 filesystem just fine after a reboot. Fsck comes up clean. Here is the error in boot.msg: <4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 <4>hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>hdb: drive not ready for command <4>hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 <4>hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>hdb: drive not ready for command <4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 <4>hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>hdb: drive not ready for command <4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 <4>hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>hdb: drive not ready for command Does anyone have a clue if this means this drive is bad (which I suspect) or is this another problem. Any other suggestions? Thanks Benjamin
Am Sam, 2002-11-16 um 23.25 schrieb Benjamin Bacon:
Hi,
I am having a problem with a SuSE 7.3 PPC server crashing when there is heavy IO on a specific drive (/dev/hdb1). This error happens when the drive is being used as the target while rsync'ing with another filesystem to mirror it once a night. Unfortunately the only data I have at this moment is some errors in the /var/log/boot.msg. The drive does mount the ext3 filesystem just fine after a reboot. Fsck comes up clean.
Here is the error in boot.msg:
<4>hdb: timeout waiting for DMA <4>ide_dmaproc: chipset supported ide_dma_timeout func only: 14 <4>hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>hdb: drive not ready for command <4>hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
disable DMA access for your hdb. On the other hand, I have had the same error, well the hard disk had hard errors.... -- Uwe Kiewel <UKiewel@t-online.de>
participants (3)
-
Benjamin Bacon -
Steven Bedrick -
Uwe Kiewel