External drive cant be seen in Finder or Disk Utility but in System Info

andymoonshine · 02-17-2013, 02:29 AM

Hi

I'm having trouble trying to mount a drive
It doesn't show up in Disk Utitlity but does in System Information

In System Information I can see it as so

Code:

LaCie Desktop Hard Drive:

  Capacity:	500.11 GB (500,107,862,016 bytes)
  Removable Media:	Yes
  Detachable Drive:	Yes
  BSD Name:	disk1
  Product ID:	0x1019
  Vendor ID:	0x059f  (LaCie)
  Version:	 0.01
  Serial Number:	00E000FF29BC5
  Speed:	Up to 480 Mb/sec
  Manufacturer:	LaCie
  Location ID:	0xfd120000 / 8
  Current Available (mA):	500
  Current Required (mA):	2
  Partition Map Type:	MBR (Master Boot Record)
  S.M.A.R.T. status:	Not Supported
  Volumes:
    Backup:
      Capacity:	500.11 GB (500,107,829,760 bytes)
      File System:	Journaled HFS+
      BSD Name:	disk1s1
      Content:	Apple_HFS
      Volume UUID:	780E7DE4-8C1B-3BB3-BE5A-F2A8D2FBA8F5

If I do the following I can see it in the list, but can't mount it

Code:

$ diskutil list
/dev/disk0
   #:			TYPE NAME			SIZE		IDENTIFIER
   0:			GUID_partition_scheme		*500.1 GB	disk0
   1:			EFI				209.7 MB	disk0s1
   2:			Apple_HFS Macintosh HD		499.2 GB	disk0s2
   3:			Apple_Boot Recovery HD		650.0 MB	disk0s3
/dev/disk1
   #:			TYPE NAME			SIZE		IDENTIFIER
   0:			FDisk_partition_scheme		*500.1 GB	disk1
   1:			Apple_HFS Backup		500.1 GB	disk1s1
/dev/disk2
   #:			TYPE NAME			SIZE		IDENTIFIER
   0:			GUID_partition_scheme		*2.0 TB		disk2
   1:			EFI				209.7 MB	disk2s1
   2:			Apple_HFS Big Fella		2.0 TB		disk2s2
/dev/disk3
   #:			TYPE NAME			SIZE		IDENTIFIER
   0:			Apple_partition_scheme		*500.1 GB	disk3
   1:			Apple_partition_map		32.3 KB		disk3s1
   2:			Apple_Driver43			65.5 KB		disk3s2
   3:			Apple_Driver_ATA		65.5 KB		disk3s3
   4:			Apple_FWDriver			114.7 KB	disk3s4
   5:			Apple_HFS External HD		500.0 GB	disk3s6
$ diskutil list disk1
/dev/disk1
   #:			TYPE NAME			SIZE		IDENTIFIER
   0:			FDisk_partition_scheme		*500.1 GB	disk1
   1:			Apple_HFS Backup		500.1 GB	disk1s1
$ mkdir /Volumes/EFI
$ sudo mount -t hfs /dev/disk1 /Volumes/EFI
GetMasterBlock: Error 5 from read; amount=-1, wanted=512
GetMasterBlock: Error 5 from read; amount=-1, wanted=512
mount_hfs: Input/output error

Once I have done this I can then see the drive in Disk Utility, but if I try to erase it it just hangs on "Unmounting Disk" & I get the following error

Code:

Disk Erase failed
Disk Erase failed with the error:

Unable to write to the last block of the device.

If I refresh the drive list window it has now disappeared & I have to restart the drive for it to appear

Does anybody have any advice or is it a dead drive?

Cheers
Andy

ganbustein · 02-17-2013, 11:45 PM

Since you're willing to erase, why not try re-partitioning it. I notice it's using FDisk_partition_scheme, which isn't one that I know of OS X supporting. (So far as I know, OS X only supports GUID, APM, and MBR.) Try changing it to GUID.

andymoonshine · 02-20-2013, 02:49 AM

Thanks for the reply

I have tried to partition the device, but it just sits on "unmouting disk" & I get the following error

Code:

Partition failed
Partition failed with the error:

Couldn’t open device.

Or sometimes

Code:

Partition failed
Partition failed with the error:

Unable to write to the last block of the device.

It's almost like it goes to sleep after about 20 seconds
It used to be just formatted normally & was my time machine backup drive

I have another drive "External HD" which is exactly the same Lacie drive & when that hasn't been used for a while & you go into it & it boots backup
I have tried using a LaunchAgent to keep it awake but that doesnt help

Cheers
Andy

BWilliams · 02-22-2013, 08:44 PM

Check your /var/log/system.log file and look for a string like:

kernel[0] <hostname goes here> I/O error diskXsY

That's from the top of my head and obviously isn't exact (X,Y) would be numbers, <hostname goes here> would be your hostname.

I remember reading that the very first and last allocation regions of a drive are critical. In the early region I think they have indexing and catalog info, drivers, etc. and at the tail end I they have something else that's important (alternate boot paths??? I don't remember). These are "critical" regions of the drive.

It sounds to me like you've got bad sectors in those regions. If its true you likely need to replace the drive.

bsd5tu1 · 02-24-2013, 11:28 PM

What's the OS you're using? Are the LaCie's exactly identical, or is one newer than the other?

The reason I ask is that some external drives apparently go to sleep in the middle of reads and writes with Mountain Lion, but I thought the problem was limited to Seagate drives.

Also, the tail end of a volume stores the alternate volume header:

Quote:


	Every HFS Plus volume must have a volume header. The volume header contains sundry information about the volume, such as the date and time of the volume's creation and the number of files on the volume, as well as the location of the other key structures on the volume. The volume header is always located at 1024 bytes from the start of the volume. A copy of the volume header, known as the alternate volume header, is stored starting at 1024 bytes before the end of the volume. The first 1024 bytes of volume (before the volume header), and the last 512 bytes of the volume (after the alternate volume header) are reserved. All of the allocation blocks containing the volume header, alternate volume header, or the reserved areas before the volume header or after the alternate volume header, are marked as used in the allocation file. The actual number of allocation blocks marked this way depends on the allocation block size.

Reference link:

http://dubeiko.com/development/FileS...#HFSPlusBasics

Possibly you have bad sectors at the very beginning and/or end of the drive that are rendering it useless.

Additionally, the system seems to think the drive is using a DOS/Windows format for the drive, but in that is an HFS volume. That's enough to daze and confuse me! Unless you used some unusual formatting scheme to try and set that up, it would appear to me that the drive is being misread (it's reading bad sectors and misinterpreting the data).

If you're not to adverse to an experiment and you have a spare drive laying around, you could open the LaCei up and swap out the drive to determine whether or not the enclosure's interface circuitry is sound. If you're using ML, before doing anything, I'd do a search and make sure there aren't some compatibility problems.

macsolver · 02-25-2013, 10:44 AM

Hi,

Check to see if a firmware update is available for your model of hard disk:

http://www.lacie.com/support/index.htm?rid=10033

There are known issues with the Oxford chip set and later versions of OSX.

Regards,

Nick

andymoonshine · 02-27-2013, 03:33 AM

Yeh both the Lacies are exactly the same
This is what I get when I try to partition it

Code:

Feb 27 09:18:01 Andys-Home-iMac kernel[0]: jnl: disk4s1: update_fs_block: failed to update block 4504600 (ret 5)
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: jnl: disk4s1: journal_open: Error replaying the journal!
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: hfs: early jnl init: failed to open/create the journal (retval 0).
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: hfs_mountfs: hfs_early_journal_init failed, setting to FSK 
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: disk4: I/O error.
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: disk4s1: I/O error.
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: 
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: hfs_mountfs: hfs_early_journal_init failed, erroring out 
Feb 27 09:18:01 Andys-Home-iMac kernel[0]: hfs_mount: hfs_mountfs returned 22
Feb 27 09:18:53 Andys-Home-iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x10f8da000): p=91864[MRT] clearing CS_VALID
Feb 27 09:18:53 Andys-Home-iMac kernel[0]: Resetting IOCatalogue.
Feb 27 09:19:15 Andys-Home-iMac kernel[0]: USBF:	1120888.228	AppleUSBEHCI[0xffffff801005f000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 8, EP: 2)
Feb 27 09:19:46 Andys-Home-iMac kernel[0]: USBF:	1120919.236	AppleUSBEHCI[0xffffff801005f000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 8, EP: 2)
Feb 27 09:20:17 Andys-Home-iMac kernel[0]: USBF:	1120950.245	AppleUSBEHCI[0xffffff801005f000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 8, EP: 2)
Feb 27 09:20:22 Andys-Home-iMac kernel[0]: disk4: device/channel is not attached.
Feb 27 09:20:22 Andys-Home-iMac kernel[0]: disk4: media is not present.
Feb 27 09:20:22 Andys-Home-iMac kernel[0]: jmPeripheralDeviceType00[0xffffff8010e64a00]: stop
Feb 27 09:20:22 Andys-Home-iMac kernel[0]: USBF:	1120956.187	[0xffffff801036a000] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 2 of Hub at 0xfd100000)
Feb 27 09:20:25 Andys-Home-iMac kernel[0]: USBF:	1120959.188	[0xffffff801036a000] The IOUSBFamily was not able to enumerate a device.

I had a look at that link but couldnt see any updates for my drive

So looks like a duff drive

Thanks for all your help

Cheers
Andy

DeltaMac · 02-27-2013, 07:07 AM

I would try swapping the hard drives between the cases.
If the problem continues with the same case (different hard drive), then you have a bad case.
If the problem travels to the OTHER case (and you still can't format that same hard drive in a different case), then the hard drive has certainly failed.

02-20-2013, 02:49 AM	#3
andymoonshine Prospect Join Date: Feb 2013 Posts: 3	Thanks for the reply I have tried to partition the device, but it just sits on "unmouting disk" & I get the following error Code: Partition failed Partition failed with the error: Couldn’t open device. Or sometimes Code: Partition failed Partition failed with the error: Unable to write to the last block of the device. It's almost like it goes to sleep after about 20 seconds It used to be just formatted normally & was my time machine backup drive I have another drive "External HD" which is exactly the same Lacie drive & when that hasn't been used for a while & you go into it & it boots backup I have tried using a LaunchAgent to keep it awake but that doesnt help Cheers Andy

02-25-2013, 10:44 AM	#6
macsolver Major Leaguer Join Date: Jan 2003 Location: Redhill, Surrey, England Posts: 479	Firmware ? Hi, Check to see if a firmware update is available for your model of hard disk: http://www.lacie.com/support/index.htm?rid=10033 There are known issues with the Oxford chip set and later versions of OSX. Regards, Nick

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

02-17-2013, 11:45 PM	#2
ganbustein MVP Join Date: Apr 2008 Location: Berkeley CA USA Posts: 1,016	Since you're willing to erase, why not try re-partitioning it. I notice it's using FDisk_partition_scheme, which isn't one that I know of OS X supporting. (So far as I know, OS X only supports GUID, APM, and MBR.) Try changing it to GUID.

02-22-2013, 08:44 PM	#4
BWilliams Prospect Join Date: Feb 2013 Posts: 4	Check your /var/log/system.log file and look for a string like: kernel[0] <hostname goes here> I/O error diskXsY That's from the top of my head and obviously isn't exact (X,Y) would be numbers, <hostname goes here> would be your hostname. I remember reading that the very first and last allocation regions of a drive are critical. In the early region I think they have indexing and catalog info, drivers, etc. and at the tail end I they have something else that's important (alternate boot paths??? I don't remember). These are "critical" regions of the drive. It sounds to me like you've got bad sectors in those regions. If its true you likely need to replace the drive.

02-27-2013, 07:07 AM	#8
DeltaMac League Commissioner Join Date: Jan 2002 Posts: 7,996	I would try swapping the hard drives between the cases. If the problem continues with the same case (different hard drive), then you have a bad case. If the problem travels to the OTHER case (and you still can't format that same hard drive in a different case), then the hard drive has certainly failed.