Trouble with LaCie Big Disk?

I saw on an archived topic that some others had problems with this 500g LaCie Big Disk. I was curious if there was anyone out there who was having the same problems I am.
The Drive will just periodically shut off for no reason whatever. It's not in use, or anything, it's just sitting there being on, and I get the warning that I've disconnected the drive and don't ever do that, etc.
I informed LaCie about this. I was out of warranty, and they just sent me a new one and it just did the same thing.
Anyone else having problems like this???
If so, was it resolved??
Power Mac G4 Dual 1.25 Mac OS X (10.4.8)
Mac OS X (10.4.8)

Hey Thomas...
Thanks so much for the reply -- a good thought - the drive actually can be connected firewire 800, fw400, or usb, and I'm getting the same symptoms when connected with any of them

Similar Messages

Warning - itunes 7 and lacie Big Disk

At poresent I am attempting to re build my Lacie 500Gb hard drive because itunes 7 has crashed it, please be careful if you have wav files on a lacie big disk
Disk utility does not work to repair the drive, tech tools has recommended using file recovery, what a wonderful way to spend a Friday evening, not listening to music but finding it
Oh and if anyone from the itunes team is reading this and I certainly hope there is, please be aware that if I lose my 500+ strong CD collection from my Big Disk, I will be asking them to send the person responsible for saying this product was safe for public consumption to come to Australia and sit in front of my mini and re rip every single CD one after another. Then they can rebuild the playiists that I so anally created, then they should be made to go and apologise to every single person in the world that their shoddy decision has effected
What a fantastic start to the weekend, thanks itunes, next time wait until it's ready
DjDs
Mac Mini 1.25Ghz PowerPC G4 Mac OS X (10.4.7) 1GB DDR SD DRAM, Migli Mini TV, Lacie Big Disk

I have recently "upgraded" to iTunes 7 myself. I use my old PB 17" as a music server (since work bought me a new 15" MacBook Pro), and . . . uh oh . . . I have my iTunes library on a LaCie Bigger Disk Extreme.
Perusing through the forums, it would seem that a lot of folks have trouble with the new iTunes and external drives, not just LaCie.
iTunes 7 corrupted the directory of the LaCie disk to the point at which I couldn't even mount the disk, and Disk Utility couldn't help me. It was really strange. The first time I ran iTunes 7, it did that whole gapless-playback scan (whatever the heck that is) and then could find none of the songs (it asked me on each song if I'd like to locate the original?). Then, I quit iTunes and couldn't open the LaCie drive icon on the desktop. So, I rebooted, and the LaCie drive wouldn't even mount.
The latest version of DiskWarrior (3.0.3), however, recognized the drive and rebuilt the directory and, I am happy to report, with the rebuilt directory ALL my music works and iTunes 7 seems to work like a charm.
It's a little frustrating that Apple released such a problematic product, BUT, I guess they can't try every possible hardware combination. iTunes and an external hard drive, though, would seem to be pretty common.
Talltexan, have you got the latest DiskWarrior?
Stuart

LaCie Big Disk Extreme+ Triple 2TB

I am thinking of getting a LaCie Big Disk Extreme+ Triple 2TB for use with Final Cut Express. This drive is actually 2 1-TB disks. Is there any problem using such a drive in capturing video (or anything else having to do with video editing/production)? Thanks in advance.

Do you use them for capturing and editing video?
Yes I do.

LaCie Big Disk Warning signs... Should I ditch?

Hi all,
First, want to quickly apologize for not doing a thorough read of all the posts regarding LaCie drives - the problem is that there are so many of them. People apparently are having all kinds of LaCie nightmares, and it would take me forever to read through everything. So here's my issue.
I have 3 LaCie Big Disk Extremes (d2), in three flavors. One 500 G, one 600 G, and 1 TB, each daisy-chained via FW 800 to the FW800 port on my G5 (Dual 2.5 GHz). All three have - until now - been acting just fine, but I just captured a few full HDV tapes to the 1 TB and I have had playback issues that just don't seem to go away. I'll play a few seconds, even at random points of the video, and it will freeze with the spinning beach ball of death.
At first I thought it was software issue, so I reinstalled QT, trashed preferences in FCP, but it all kept coming back to the same problem.
Now, here's the weird thing - when I copy the same video from my 1 TB to one of my other LaCies (which are actually further down the daisychain), the video plays fine, with no stuttering or freezing.
Now reading all of the LaCie posts is freaking me out a tad - is this some kind of warning sign that my 1 TB drive is heading down a dark path?
Is there some way I can fix it by either wiping it or attempting to see about fixing hardware?
And finally, is daisychaining all of these drives on the same FW 800 bus recommended, or is there a better solution (that won't break the bank)?
Any suggestions would be most appreciated. Thanks guys!
Dan
(P.S. Any suggestions on other drive brands? A client just bought a Western Digital MyBook 1 TB, and it seems to be working great, but I'm open to suggestions).

Yes it is true that people report lods of problems with Lacie drives and there are many reasons for that.
Even the power supply is considered dangerousely unreliable.
Another thing is that drives can fail indeed at some point. If you can play the footage from some of your other drives then the 1TB might have some issues (power supply or other is difficult to say). Best would be backing up your media and if you can then run Disk Warrior http://www.alsoft.com/DiskWarrior/
Good and not massively expensive drives, should you want new ones, are G-tech and Caldigit (links below). You could RAID a few drives (RAID 0 for example for quicker workflow), however, choice depends on several factors: what format you will be working on in the future, if you want to upgrade to eSATA at some stage, etc. Use the search tool of the forum or google for hints:
http://discussions.apple.com/thread.jspa?messageID=5068643
Personally I would NOT go for WD. Not really designed for editing.
http://www.caldigit.com/
http://www.g-technology.com/

Trouble with LaCie disk and time machine

HI everyone,
I've been having trouble with using time machine to back-up to my 1 TB LaCie drive (purchased 5/12, unfornuately I was dumb and didn't register the drive and no longer have the box with the serial number and there is no serial number on my drive. The only problem I had up until the end of August was that every so often the LaCie drive (using my FW 800 port) would unmount after waking up from sleep.
The end of August the drive unmounted for no reason while I was on the computer doing a task. Could not get the LaCie drive remounted (rebooting, etc. etc.) To make a long story short, ended up calling apple care who took me through resetting my SMC and PRAM to no avail. Was booted to higher level of support who walked me through trying to repair my drive using the disk utiltiy. When that didn't work, she walked me through erasing and reformatting the LaCie drive and starting a new time machine back-up. Every thing ok until about ten days ago.
Last week, when I woke my iMac up from sleep, I got an error saying that the disk was not ejected properly and I could not mount the drive. Restarting did nothing, the disk did not mount. Shutting down and rebooting seemed to solve the problem and the disk was mounted. Every so often I've had the problem with the disk unmounting after waking up from sleep before. So, I changed my energy sleep preferences. At the end of the day when I am done, I'd unmount the LaCie drive before putting the Mac to sleep using the apple menu.
Today I came in to start my day, plugged the drive in and it would not mount. Tried rebooting nothing. Went into the disk utility, at first the LaCie drive passed the disk verify (6:26:25 and 6:26:38). Then I went into repair disk on the indented drive at 6:27:13, I wasn't sure what it is was doing, thinking that it had hung, I stopped the repair at 6:27:24. Exited disk utility, and the LaCie drive mounted. But I was getting a read only error when I tried to back-up using time machine. So, I went back into disk utility at 6:27:35, when I verified the disk (indented disk), I got an error saying the disk need to be repaired. After several minutes the disk could not be repaired. So, I erased and reformatted the drive. Ran a time machine back-up and it seemed to back-up everything on my hard drive. Just ran another verify disk and it passed.
Is the drive failing? Have some other back-ups of my documents, my address book, iCal and am going to make a backup of some of my pref files and important e-mail files and am going to do some more back-ups after I am done.
Have reached out to the women at apple care whom I talked to last August, but don't expect to hear back from her for at least 24 hours.
Here is my disk utility log
2013-11-07 06:26:25 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:25 -0500: Starting verification tool:
2013-11-07 06:26:25 -0500: Checking prerequisites
2013-11-07 06:26:25 -0500: Checking the partition list
2013-11-07 06:26:25 -0500: Checking for an EFI system partition
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:25 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:25 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:25 -0500: The partition map appears to be OK
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:38 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:38 -0500: Starting verification tool:
2013-11-07 06:26:38 -0500: Checking prerequisites
2013-11-07 06:26:38 -0500: Checking the partition list
2013-11-07 06:26:38 -0500: Checking for an EFI system partition
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:38 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:38 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:38 -0500: The partition map appears to be OK
2013-11-07 06:26:38 -0500:
2013-11-07 06:26:38 -0500:
2013-11-07 06:27:13 -0500: Disk Utility started.
2013-11-07 06:27:21 -0500: Verifying and repairing partition map for “LaCie”
2013-11-07 06:27:21 -0500: Starting repair tool:
2013-11-07 06:27:21 -0500: Checking prerequisites
2013-11-07 06:27:21 -0500: Checking the partition list
2013-11-07 06:27:21 -0500: Checking for an EFI system partition
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s size
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s file system
2013-11-07 06:27:23 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:27:24 -0500: Reviewing boot support loaders
2013-11-07 06:27:24 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:27:24 -0500: Updating Windows boot.ini files as required
2013-11-07 06:27:24 -0500: The partition map appears to be OK
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:35 -0500: Verifying volume “LaCie”
2013-11-07 06:27:35 -0500: Starting verification tool:
2013-11-07 06:27:35 -0500: Checking file system2013-11-07 06:27:35 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:27:35 -0500:
2013-11-07 06:27:35 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:28:05 -0500:
2013-11-07 06:28:13 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:28:13 -0500: Starting repair tool:
2013-11-07 06:28:13 -0500: Checking file system2013-11-07 06:28:13 -0500: Volume repair complete.2013-11-07 06:28:13 -0500: Updating boot support partitions for the volume as required.2013-11-07 06:35:05 -0500: Stopped by user
2013-11-07 06:44:56 -0500: Disk Utility started.
2013-11-07 06:45:20 -0500: Verifying volume “LaCie”
2013-11-07 06:45:20 -0500: Starting verification tool:
2013-11-07 06:45:20 -0500: Checking file system2013-11-07 06:45:20 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:45:20 -0500: Checking extents overflow file.
2013-11-07 06:45:20 -0500: Checking catalog file.
2013-11-07 06:45:59 -0500: Missing thread record (id = 5057741)
2013-11-07 06:46:06 -0500: Checking multi-linked files.
2013-11-07 06:46:19 -0500: Checking catalog hierarchy.
2013-11-07 06:46:38 -0500: Invalid directory item count
2013-11-07 06:46:38 -0500: (It should be 0 instead of 4)
2013-11-07 06:46:38 -0500: Invalid volume directory count
2013-11-07 06:46:38 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:46:38 -0500: Checking extended attributes file.
2013-11-07 06:47:05 -0500: Checking multi-linked directories.
2013-11-07 06:48:10 -0500: Checking volume bitmap.
2013-11-07 06:48:12 -0500: Checking volume information.
2013-11-07 06:48:12 -0500: The volume LaCie was found corrupt and needs to be repaired.
2013-11-07 06:48:12 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:48:12 -0500:
2013-11-07 06:48:12 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:48:12 -0500:
2013-11-07 06:50:02 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:50:02 -0500: Starting repair tool:
2013-11-07 06:50:02 -0500: Checking file system2013-11-07 06:50:02 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:50:02 -0500: Checking extents overflow file.
2013-11-07 06:50:02 -0500: Checking catalog file.
2013-11-07 06:50:41 -0500: Missing thread record (id = 5057741)
2013-11-07 06:50:48 -0500: Checking multi-linked files.
2013-11-07 06:51:02 -0500: Checking catalog hierarchy.
2013-11-07 06:51:20 -0500: Invalid directory item count
2013-11-07 06:51:20 -0500: (It should be 0 instead of 4)
2013-11-07 06:51:20 -0500: Invalid volume directory count
2013-11-07 06:51:20 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:51:20 -0500: Checking extended attributes file.
2013-11-07 06:51:47 -0500: Checking multi-linked directories.
2013-11-07 06:52:55 -0500: Checking volume bitmap.
2013-11-07 06:52:56 -0500: Checking volume information.
2013-11-07 06:52:56 -0500: Repairing volume.
2013-11-07 06:52:56 -0500: Missing directory record (id = 5057741)
2013-11-07 06:52:56 -0500: Look for missing items in lost+found directory.
2013-11-07 06:53:10 -0500: Rechecking volume.
2013-11-07 06:53:10 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:53:10 -0500: Checking extents overflow file.
2013-11-07 06:53:10 -0500: Checking catalog file.
2013-11-07 06:53:16 -0500: Incorrect number of thread records
2013-11-07 06:53:22 -0500: Checking multi-linked files.
2013-11-07 06:53:35 -0500: Checking catalog hierarchy.
2013-11-07 06:53:53 -0500: Invalid directory item count
2013-11-07 06:53:54 -0500: (It should be 5 instead of 6)
2013-11-07 06:53:54 -0500: Invalid volume directory count
2013-11-07 06:53:54 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:53:54 -0500: Invalid volume file count
2013-11-07 06:53:54 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:53:54 -0500: Checking extended attributes file.
2013-11-07 06:54:20 -0500: Checking multi-linked directories.
2013-11-07 06:55:25 -0500: Checking volume bitmap.
2013-11-07 06:55:26 -0500: Checking volume information.
2013-11-07 06:55:26 -0500: Repairing volume.
2013-11-07 06:58:06 -0500: Rechecking volume.
2013-11-07 06:58:06 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:58:06 -0500: Checking extents overflow file.
2013-11-07 06:58:07 -0500: Checking catalog file.
2013-11-07 06:58:12 -0500: Incorrect number of thread records
2013-11-07 06:58:18 -0500: Checking multi-linked files.
2013-11-07 06:58:31 -0500: Checking catalog hierarchy.
2013-11-07 06:58:50 -0500: Invalid volume directory count
2013-11-07 06:58:50 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:58:50 -0500: Invalid volume file count
2013-11-07 06:58:50 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:58:50 -0500: Checking extended attributes file.
2013-11-07 06:59:17 -0500: Checking multi-linked directories.
2013-11-07 07:00:22 -0500: Checking volume bitmap.
2013-11-07 07:00:24 -0500: Checking volume information.
2013-11-07 07:00:24 -0500: Repairing volume.
2013-11-07 07:03:03 -0500: Rechecking volume.
2013-11-07 07:03:03 -0500: Checking Journaled HFS Plus volume.
2013-11-07 07:03:03 -0500: Checking extents overflow file.
2013-11-07 07:03:04 -0500: Checking catalog file.
2013-11-07 07:03:09 -0500: Incorrect number of thread records
2013-11-07 07:03:15 -0500: Checking multi-linked files.
2013-11-07 07:03:29 -0500: Checking catalog hierarchy.
2013-11-07 07:03:47 -0500: Invalid volume directory count
2013-11-07 07:03:47 -0500: (It should be 166844 instead of 166842)
2013-11-07 07:03:47 -0500: Invalid volume file count
2013-11-07 07:03:47 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 07:03:47 -0500: Checking extended attributes file.
2013-11-07 07:04:14 -0500: Checking multi-linked directories.
2013-11-07 07:05:19 -0500: Checking volume bitmap.
2013-11-07 07:05:20 -0500: Checking volume information.
2013-11-07 07:05:20 -0500: The volume LaCie could not be repaired after 3 attempts.
2013-11-07 07:05:21 -0500: Volume repair complete.2013-11-07 07:05:21 -0500: Updating boot support partitions for the volume as required.2013-11-07 07:05:21 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 07:05:21 -0500:
2013-11-07 07:05:21 -0500: Disk Utility stopped repairing “LaCie”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2013-11-07 07:05:21 -0500:
2013-11-07 07:09:45 -0500: Disk Utility started.
2013-11-07 07:11:45 -0500: Preparing to erase : “LaCie”
2013-11-07 07:11:45 -0500:     Partition Scheme: GUID Partition Table
2013-11-07 07:11:45 -0500:     1 volume will be erased
2013-11-07 07:11:45 -0500:         Name        : “LaCie”
2013-11-07 07:11:45 -0500:         Size        : 999.86 GB
2013-11-07 07:11:45 -0500:         File system    : Mac OS Extended (Journaled)
2013-11-07 07:11:45 -0500: Unmounting disk
2013-11-07 07:11:45 -0500: Erasing
2013-11-07 07:11:54 -0500: Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume with a 81920k journal
2013-11-07 07:11:54 -0500: Mounting disk
2013-11-07 07:11:54 -0500: Erase complete.
2013-11-07 07:11:54 -0500:
2013-11-07 10:38:00 -0500: Disk Utility started.
2013-11-07 10:38:12 -0500: Verifying volume “LaCie”
2013-11-07 10:38:12 -0500: Starting verification tool:
2013-11-07 10:38:14 -0500: Checking file system2013-11-07 10:38:14 -0500: Checking Journaled HFS Plus volume.
2013-11-07 10:38:14 -0500: Checking extents overflow file.
2013-11-07 10:38:14 -0500: Checking catalog file.
2013-11-07 10:38:29 -0500: Checking multi-linked files.
2013-11-07 10:38:29 -0500: Checking catalog hierarchy.
2013-11-07 10:38:41 -0500: Checking extended attributes file.
2013-11-07 10:39:04 -0500: Checking multi-linked directories.
2013-11-07 10:39:31 -0500: Checking volume bitmap.
2013-11-07 10:39:32 -0500: Checking volume information.
2013-11-07 10:39:32 -0500: The volume LaCie appears to be OK.
2013-11-07 10:39:32 -0500: Repair tool completed:
2013-11-07 10:39:32 -0500:
2013-11-07 10:39:32 -0500:

I just got a call back from the upper level support person at apple care who had been advising me on my trouble with time machine and my LaCie 1 TB FWD. I had sent her much of the same verbiage as I posted here. As some of you have probably figured out, the verdict is that the drive is probably failing. She says this because I have had to do two erase and reformats. She thought that the intermitant problem that I have had with the drive unmounting when my iMac wakes from sleep could be related to the drive failing.
In the meantime I have a secondary back-up (not using time machine) and the LaCie 1 TB FWD is working for the moment.
Thanks to all who read all my verbiage.
And in the meantime, I've learned something. I marked this question as solved. But I'm open to other things to try.
Message was edited by: njtreehugger minor edits and update

Icon and use of LaCie Big Disk+ no longer

I purchased a LaCie 1 TB big disk+ external drive. Worked great out of the box. Large enough that I unloaded all of my other external drives onto it. Now, it (the icon) no longer appears on the desktop, allowing me access. The profiler states that it's recognized. I'm using my firewire 800 port which works fine with other drives, so that's not the problem. I also tried connecting it using the firewire 400 port. No luck. I've rebooted numerous times, with and without the drive plugged in. I've turned it on and off, disconnected the power temporarily, disconnected and reconnected, tried reloading the drivers, but get the message they're up to date and fine. Help!

Often LaCie drives will have power supply brick issues that are difficult to troubleshoot as the blue light comes on and the disk spins but nobody is home.
If the drive is under warranty LaCie will replace the brick no charge.
As an aside, you still need to backup the data that is on this drive otherwise you stand a chance of losing all of your data should the drive fail.
Luck-
-DP

Need help with Lacie Big Extreme that won't mount

OK Guys,
My buddy's Lacie 1TB Big Extreme won't mount to any computer we try. The blue light is flashing. We have tried different cables on different computers. After a web search for similar problems we found out several people had success just plugging in a new power supply. So, we ordered one. Didn't work.
I can hear the drive spinning up. Oh, I guess I should mention this unit is out of warranty.
Here's my question. After some research, I found out this drive has 2 hard drives inside and set up as Raid 0. This is the way Lacie sets these up for use right out of the box. So if I take the Lacie enclosure apart and try to mount the drives separately in another generic enclosure what will I see in terms of the files written on a single drive (assuming it mounts) since I am dealing with an initial Raid 0 set-up? My intention is to save the files. Please help.

Same problem with an external LaCie Little Big Disk = does not mount, but shows up under FireWire in System Profiler. I assume it's a OS X issue, because I ran a software "Data Rescue II" and this software has recognized the disk.
Has probably something to do with one of the latest OS X updates, because I've used this disk with Time Machine now more than a year and never had a problem.
I recommend not to experiment with partitioning/reformatting (if you care about the data on the disk) and push Apple for a solution. It assume it's some kind of an access problem.

Scsi tran_err with lacie firewire disks

Hello,
I have been trying to setup a zpool with two 2TB Lacie Bigger Disk Extremes. They work fine individually but as soon as I attach one as a mirror to the other I immediately get errors like the following:
Oct 4 16:33:53 safety scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci10de,370@6/pci108e,534d@6/unit@00d04b76060a72ba/disk@0,0 (sd1):
Oct 4 16:33:53 safety SCSI transport failed: reason 'reset': retrying command
Oct 4 16:33:53 safety scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci10de,370@6/pci108e,534d@6/unit@00d04b76060a72ba/disk@0,0 (sd1):
Oct 4 16:33:53 safety SCSI transport failed: reason 'tran_err': retrying command
I have 3 of these disks, one of which has important data on it (and lots of it), so I have tried mirroring in 3 different ways, i.e. suppose disk A is the one with data on it and disk B and C are free for experimentation. I have already a zpool with disk A, so I attach disk B to disk A and get the errors, so I detach disk B and arrach instead disk C, but still I have errors. I try with only disk B and C instead, creating a zpool with disk B then attaching disk C, or creating first the zpool with disk C then attaching B, but all combinations produce the same error. I have also tried with two different firewire lacie disks (old 80GB ones) but they function without any problem, so I am totally stumped as to what the problem could be. I thought perhaps some bios setting would help, but I could find no settings to help.
I am running Solaris 10 on a Sun Ultra 20 Workstation. If anyone has any ideas I would be extremeley grateful.
Thanks in advance,
Matt

Libby,
Backup is unable to make a restorable by Disk Utility backup. You can restore pieces of the software as outlined in my FAQ about backing up user data:
http://www.macmaps.com/backup.html
But to be able to restore a backup with Disk Utility, you need a cloning utility to have made the backup.
I suggest starting a new thread here, where someone else could help you out better:
http://discussions.apple.com/forum.jspa?forumID=752&start=0
First off, you'll get a wider audience who may be able to solve your problem. Secondly, responses to you won't confuse the original poster with solutions that don't apply to them. And thirdly, you'll know for certain whether or not a response applies to you.

LaCie Big Disk Extreme

I own a 500GB Lacie Drive (Big Disk Extreme) that is behaving very poorly. Without elaborating on its behavior I wanted to ask if there are any good companies I can use to replace the drive itself inside the enclosure from LaCie? I've emailed them about this but have yet to hear back & wanted to start a search in case they will not do it.
Thanks,
Harris

Hi
When I was looking into getting an external drive for my Mac, I found a number of posts which seemed to suggest the power supply and cooling used in the LaCie enclosures containing the higher capacity drives weren't as good as they could have been and may lead to premature drive failure.
As far as I'm aware, all external drives are just normal internal drives mounted in an external USB or FireWire enclosure. You can certainly buy the drives and enclosures separately and build your own.
Equally I can't see why you couldn't just buy a drive and replace the existing one in an existing enclosure, or buy an enclosure and replace the existing one containing an existing drive. I guess the only difficulty would be if the LaCie enclosure is sealed or the internal data and power cables are soldered into the back of the drive. Having done a quick search in Google, it doesn't seem too difficult to remove the drive from the enclosure and replace one or the other yourself. I'd imagine this would almost certainly invalidate any warrranty though.
I hope this helps.

Trouble with Lacie 1TB external hard disk

Recently got a Lacie 1TB external hard disk. Need to get as close to 1TB actual capacity as I can.
Used cfdisk to create a single Linux partition, and thought I tried to "maximize" the size.
Used mkfs -t ext3 /dev/sdb1 to create the file system.
Tried to mount the disk. The first go around apparently failed (dmesg said there was no journal).
I repeated all of the above and the second time it mounted, but "df -h" reports:
/dev/sdb1 925G 200M 878G 1% /mnt/external_1
What the hell happened?
Can someone please advise on how to fix this, and actually maximize the real available space? Please include the exact utilities and flags you would recommend.
thanks much.

lucke,
i know disks always have less capacity than the nominal size. but a 1TB disk should have more than 900 MB available. possibly as much as 980 MB. that would be commensurate with my past experience using other external drives. over 200 GB used off the bat is ridiculous, and i've never seen anything like that before.
as a revised question to people out there, which fs would you recommend to get the most out of this disk. it's going to have 900+ GB of files, each almost exactly 170 MB, and will be processed via the USB2 interface.

LaCie Big Disk 500GB Crashes OSX 10.4.7 when booted??? Help?! I've lost it!

I had this problem once before with kernel panic, but at the time the drive was NTFS formatted for the PC I was switching from. I networked, manipulated the data around, and transferred the data over the network then reformatted the LaCie as a Mac drive and re-uploaded all the files to it via the Mac G5.
Now, after I upgraded to 10.4.7 it seems, every time I try to boot the computer with it connected, it causes a crash/kernel panic forced hard reboot shortly after completely booting up.
I AM REALLY DISAPPOINTED IN APPLE. I switched back from the PC, hoping for an improvement for my thousands of dollars, but nooooo. Aperture? HA! Mail? corrupted, can't find stuff from 6 months ago anymore... Jesus Apple, get your $#!^ together! /rant
Can anyone help me get this Lacie back online? I'm completely hosed now b/c it won't mount on the PC either now that it's been 'Mac'ed' - which I am starting to look at as a technical equivalent of 'pimp-slapped'...
Thanks in advance for any assistance.
Hey Apple, looks like it's time for 10.4.8?
G5 Dual 2.3 Mac OS X (10.4.7) 4GB RAM

Ok, I'm going to jump in here now.
I have a Lacie 320GB drive, that I borrowed from a friend, that has an NT filesystem. I'm running a bone stock 2.3Ghz dual G5 (5 months old) and 10.4.7.
If I plug the drive into either the front panel FW400 port -or- the rear FW800 port the machine will crash in about 5 seconds. The screen goes gray from the top to the bottom kind of like a shade being pulled down. Then I get the message in a small window that says to hold down the power button to reboot my computer.
Funny thing is, I also have a 1.67GHz G4 15" Powerbook, also running 10.4.7, and the drive works in both the FW800 and FW400 ports on that. I also plugged it into my (very old) 350Mhz G3 running 10.3.9 and it works fine there too.
Now onto my second, but related issue. I have a 250GB Lacie FW800/FW400/USB 2.0 drive also. Been using it for almost a year and always worked perfectly (Mac FS on it). Before I tried the other external drive (talked about above) I plugged this 250GB drive in and ....nothing.... It doesn't appear visible to the Mac in any way since updating to 10.4.7. Used it two weeks ago when running 10.4.6 and it worked fine. Now this drive is NOT visible on ANY machine that I have. I've tried all three ports on the drive (FW800, FW400, USB-2) with different cables and different computers. The drive is NOT visible on any of them. Disk utitility doesn't see it, the system profiler doesn't see anything on any of the ports. Funny thing is that as soon as you plug the drive into a port it fires up (light turns on) and you can hear it doing its thing internally just like it always has.
Now this could just be a coincidence that it went missing after installing 10.4.7 but I'm starting to think that 10.4.7 did something with the drive.
Remember, I have 2.3Ghz dual G5 which is ABSOLUTELY in stock condition as it came directly from Apple about 5 months ago. No extras, nothing special. Looking at your signature I see that we have pretty much the same machine.
I can only conclude that there is some problem with 10.4.7 software and my machine's hardware. You are seeing the same behavior and don't have an NT filesystem on your external drive so it doesn't appear to be related to that.

Trouble w/LaCie, SuperDuper, Disk Util, & strange lockups

Hi - I have a very perplexing problem that even Dave at SuperDuper (ShirtPocket Software) can't help with.
Our 5-month old LaCie external backup drive (firewire) worked great all up til today. I had been backing up my Powerbook to a volume on the drive with SuperDuper, doing a SmartBackup each time. I also had 2 other volumes that i did drag-and-drop with files from my husband's Powerbook and our iBook, which we use only for digital photography maintenance/storage.
When I tried to do a full bootable backup with my husband's Powerbook (identical to mine in config), using his named volume, SuperDuper would freeze up on the Verifying Permissions.
Then it would not let me unmount the LaCie. Then DiskUtility crashed when I tried to erase and re-partition, then his computer would NOT shut down. I had to force shut down (ouch).
so i thought I'd erase and reformat the LaCie. I plugged in my computer which up til now worked great, and - same thing. Disk Utility would not erase or partition ("could not mount disk"). During SuperDuper, mine hung up midway on the volume writing, having a fit over first "Parent Directory/Users/Shared/SC Info does not exist" and then on the volume with ".Spotlight-V100.
It also would not unmount the laCie, and would not shut down/restart. I also got a wierd message about Mirror Agent not shutting down and to force-quit it.
Ack! Now i have no backups, and our computers are buggered. I've had NO problems with our dear Macs before this. We are both running Tiger (love it).
ANY suggestions folks? MOST annoying loss of a day's productivity.
Roseann

Hi - thanks for weighing in. I solved it, after much monkeying around. Figured out that LaCie firmware needed to be updated, but some messed up permissions files kept that from happening until i downloaded the software/driver in safe mode. I tried to run SuperDuper in safe, but it would not. But by the time i logged in and out, it worked fine and i got 2 perfect backups first try in full Tiger.
Thanks!

Trouble with Fantom drive / Disk Utility won't erase it

Until a few days ago, i had no problems with my Fantom 160 GB titanium drive. Then when i connected it to a freind's Mac, it started out OK fora few minutes, when my brother was playing around with creating an air network between the friend's computer, to which my fantom drive was attached, and my laptop. When i tried to activate the network, the Mac semi froze for a few minutes and just didn't do anything. when it started to move again, the fantom drive was showing 0 files in the finder window, and wouldn't eject.
So i turned it off and back on, which was probably a mistake; then the drive gave a message that it was unreadable.
Since i wouldn't lose too much data, i had no problem reinitializing the drive, but Disk Utility kept telling me that the erase failed.
When i try to verify the drive in Disk Utility, i get the error -9972: "Error: The underlying task reported failure on exit (-9972)"
This is the same text i get when i try to erase the drive, but without the error number.
I see at http://docs.info.apple.com/article.html?artnum=302411 that this message this is bad, as Disk Utility cannot fix it.
Currently, the drive does not show up on the desktop, but it does show up in Disk Utilities. It stopped telling me the drive is unreadable.
Is this drive beyond help?

Dale,
that post is helpful, but I'm not sure how much it applies to me. My ibook shows no problems when not connected to the firewire drive, while the firewire drive started acting up when connected to another computer. i have also not been able to get the firewire drive to work on two other macs. The Fantom drive showed up as unreadable on all three, and Disk Utilities on all 3 computers failed to erase the firewire drive. By brother's had Disk Warrior & it wasn't able to do anything for the fantom drive, either.

Lacie Big Disk BIG ERROR (-9972)

Below is the definition for the issue I'm having on my G4. I've used disk Utility, Drive Genius and Disk Warrior. None of them could fix the issue. The solution below states that I should "back Up" the disk and start fresh. Here's the problem: How I access files on a drive won't allow me to see what's on it?
Any help will do.
Much Thanks.
~MF
Symptoms
In rare circumstances, Disk Utility may display the following message when you try to verify or repair a disk:
"The underlying task reported failure"
The Disk Utility log will also display a -9972 error code. This indicates that your disk volume has issues that Disk Utility cannot fix.
Products Affected
Disk Utility, Adobe Photoshop CS2, Adobe Illustrator CS2
Resolution
What can I do?
If you experience this rare occurrence, you should attempt to resolve the issue as soon as possible.
Try using fsck in single user mode, or start up your computer from a different volume before verifying or repairing.
Back up as much of your important data and files as you can, then try using a third-party disk utility to repair the drive. Be sure that you use one that works with your version of Mac OS X.
Back up as much of your important data and files as you can, then perform an Erase and Install installation of Mac OS X on the affected volume.
Important: This option completely erases the destination volume and then installs a new copy of Mac OS X. You should always backup important files on the target volume before performing an Erase and Install installation. You can then restore your backed up files afterwards.

Hi, ~MF -
It is good practice to cite the source of quoted material; if possible, give the link to the aarticle. In this case, it would appear that you quoted a portion of this Apple KBase article -
http://support.apple.com/kb/TS1901
If you have tried to do what you can using Disk Utility (while booted to a CD) and Disk Warrior, try using a data retrieval program to capture your data from the drive before re-initializing it, such as -
Data Rescue
Virtual Lab
Both of those have trial versions available for download; either may have restrictions re what versions of OSX they support.

LaCie Big Disk 640GB Worked then stopped

I know Raid isn't supported by AE(n), but the strange thing is it worked the first day, then I started copying stuff on it and it stopped working. Is it because it started to use both disks?
Is there a way to upgrade the Lacie firmware to disable the Raid?
Any idea? Anyone?
Micha

Have you restarted the Airport remotely by say, changing any settings in the AirPort Utility?
That causes my USB-attached drive to disconnect from the wireless network every time. To get it to reappear, I simply unplug & replug it into the USB connection after the AirPort restart is complete. Worth a try if you haven't done that yet...

Trouble with LaCie Big Disk?

Similar Messages

Maybe you are looking for