my devices with known imperfections or suspected issues

Moderators: jhartley, MSR734, nola

Context

Post by grahamperrin » Sun Mar 24, 2013 1:31 pm

Re viewtopic.php?p=4300#p4300

I wouldn't wish readers to waste time with this particular topic. For the 1 TB LaCie Big Disk Extreme (300797EK), my approach is the same as for the 500 GB LaCie Big Disk Extreme (300794EK) –

> I treat all data on these disks – two in the one enclosure – as disposable.

Yes, an ordinary user should discard the drive, its power supply, and its cable but for ZEVO test purposes I continue to use drives such as these – with disposable data – half-expecting a significant event, or set of events, that I might relate to some other user's troubleshooting.

The Chris Nelson stuff is great, but no substitute for finding things that key be specific to ZEVO …

Recent events with the 1 TB LaCie Big Disk Extreme (300797EK)

2013-03-19, Tuesday


– don't pay too much attention to the detail. In a nutshell:

  • following the I/O errors, the OS automatically tried but failed to repair the dirty HFS Plus file system at the .sparsebundle level
  • an unreadable disk message (yellow alert) was followed almost immediately by an irreparable disk message (red alert).

2013-03-20, Wednesday

  1. kernel panic around 06:06, maybe fifteen minutes after beginning a zpool scrub with ZEVO Community Edition 1.1.1
  2. OS X 10.8.3 kernel panics with ZEVO Community Edition 1.1.1 every time a failing hard disk is connected

– again, don't pay too much attention to the detail.

Of interest now: we have a disk, admittedly not good, that causes the Mac to panic within seconds of connection. Critically (but without complaint):

  • the dynamic import that's integral to ZEVO Community Edition 1.1.1 does not allow the Mac to run with the disk without import

– so we can't use zdb, and so on. Time for a gentle bump to disable automatic zpool import.

Yes I should discard the disk but I'm fairly sure that the string of panics on the Wednesday will be comparable to some other user's troubleshooting topic that is without a satisfactory conclusion:


– familiarly, the collegeitdept case …
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

LaCie product confusion (sanity check)

Post by grahamperrin » Fri Mar 29, 2013 12:11 pm

Not for the first time, the LaCie web site is troublesome. After clearing all cookies for the domain and shift-reloading pages, the support page for my three LaCie hard disk drives takes me to a wristwatch for all three:

screenshot 2013-03-29 at 16.14.29.png
screenshot 2013-03-29 at 16.14.29.png (233.2 KiB) Viewed 46 times


Mistakes such as those :evil: probably explain why I have spent the last few years mistakenly describing a 1 TB Big Disk Extreme as a Little Big Disk :!:

So today I ploughed through all relevant posts in this forum. Most mistakes are edited out, but in this post for example it's appropriate to leave the original (wrong) name against disk7s2.

For my own sanity and for the record, here's a shortlist of LaCie hard disk drives currently with me at home.

Side note: Internet Archive Wayback Machine URLs show the same pid (product ID?) used for different items/products over the years :roll:

Item 301033EK
  • 160GB d2 Hard Drive Extreme with Triple Interface
  • LaCie d2 Extreme LUN 0, 0x0 in System Information
  • circa 2005-11
  • relatively small enclosure

Item 300794EK
  • 500GB Big Disk Extreme with Triple Interface
  • BigDisk Extreme, 0x0525 in System Information
  • circa 2006
  • relatively large enclosure, slightly battered.

Item 300797EK
  • 1 TB Big Disk Extreme with Triple Interface
  • BigDisk Extreme, 0x0525 in System Information
  • circa 2007
  • relatively large enclosure, visually identical to the 300794EK but not battered.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Some success with USB 2.0 instead of FireWire 800

Post by grahamperrin » Fri Mar 29, 2013 12:53 pm

grahamperrin wrote:… a disk, admittedly not good, that causes the Mac to panic within seconds of connection. …


At viewtopic.php?p=4365#p4365

… I have a hunch that if I connect the disk to a ZFS enabled system without ZEVO, and stop the scrub, then I'll be able to connect the disk to a ZEVO-enabled system – not for production use, but enough to use things such as zdb (although with this hardware, I wouldn't expect all uses of zdb to run to completion without a kernel panic). …


As it turns out, in this case, no need to avoid ZEVO  :)

On a hunch, recalling something from a few months ago (probably unrelated to ZFS), I made a USB connection between the drive and the MacBookPro5,2.

Success – with USB 2.0, without the FireWire 800 connection, no panic.

I took the opportunity to stop the scrub that began on 2013-03-20 then got a verbose status and exported the pool:

Code: Select all
macbookpro08-centrim:68f896193f gjp22$ zpool status
  pool: gjp22
 state: ONLINE
 scan: scrub repaired 0 in 20h27m with 0 errors on Mon Mar 25 18:52:26 2013
config:

   NAME                                         STATE     READ WRITE CKSUM
   gjp22                                        ONLINE       0     0     0
     GPTE_71B8BDA2-3EBA-4B91-9E1C-2AE2B1DAAD06  ONLINE       0     0     0  at disk8s2
   cache
     GPTE_2605CCB0-67B7-4C93-A4B1-83EF764CE617  ONLINE       0     0     0  at disk2s2

errors: No known data errors

  pool: twoz
 state: ONLINE
status: One or more devices has experienced an error resulting in data
   corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
   entire pool from backup.
 scan: scrub in progress since Wed Mar 20 05:50:22 2013
    371Gi scanned out of 375Gi at 576Ki/s, 1h43m to go
    22.1Mi repaired, 99.09% done
config:

   NAME                                         STATE     READ WRITE CKSUM
   twoz                                         ONLINE       1     0    14
     GPTE_34E7E852-7E88-4FAD-B162-2AEF6D300D42  ONLINE       1     0   168  at disk3s4  (repairing)

errors: 68 data errors, use '-v' for a list
macbookpro08-centrim:68f896193f gjp22$ zpool scrub -s twoz
macbookpro08-centrim:68f896193f gjp22$ zpool status
  pool: gjp22
 state: ONLINE
 scan: scrub repaired 0 in 20h27m with 0 errors on Mon Mar 25 18:52:26 2013
config:

   NAME                                         STATE     READ WRITE CKSUM
   gjp22                                        ONLINE       0     0     0
     GPTE_71B8BDA2-3EBA-4B91-9E1C-2AE2B1DAAD06  ONLINE       0     0     0  at disk8s2
   cache
     GPTE_2605CCB0-67B7-4C93-A4B1-83EF764CE617  ONLINE       0     0     0  at disk2s2

errors: No known data errors

  pool: twoz
 state: ONLINE
status: One or more devices has experienced an error resulting in data
   corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
   entire pool from backup.
 scan: scrub canceled on Fri Mar 29 14:29:11 2013
config:

   NAME                                         STATE     READ WRITE CKSUM
   twoz                                         ONLINE       2     0    17
     GPTE_34E7E852-7E88-4FAD-B162-2AEF6D300D42  ONLINE       2     0   239  at disk3s4

errors: 65 data errors, use '-v' for a list
macbookpro08-centrim:68f896193f gjp22$ clear





macbookpro08-centrim:68f896193f gjp22$ cd
macbookpro08-centrim:~ gjp22$ sudo zpool status -v twoz
Password:
  pool: twoz
 state: ONLINE
status: One or more devices has experienced an error resulting in data
   corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
   entire pool from backup.
 scan: scrub canceled on Fri Mar 29 14:29:11 2013
config:

   NAME                                         STATE     READ WRITE CKSUM
   twoz                                         ONLINE       2     0    17
     GPTE_34E7E852-7E88-4FAD-B162-2AEF6D300D42  ONLINE       2     0   239  at disk3s4

errors: Permanent errors have been detected in the following files:

        twoz:/macbookpro08-centrim.sparsebundle/bands/43f
        twoz:/macbookpro08-centrim.sparsebundle/bands/29d8
        twoz:/macbookpro08-centrim.sparsebundle/bands/29da
        twoz:/macbookpro08-centrim.sparsebundle/bands/2eaf
        twoz:/macbookpro08-centrim.sparsebundle/bands/81a
        twoz:/macbookpro08-centrim.sparsebundle/bands/2396
        twoz:/macbookpro08-centrim.sparsebundle/bands/2098
        twoz:/macbookpro08-centrim.sparsebundle/bands/144b
        twoz:/macbookpro08-centrim.sparsebundle/bands/3cfa
        twoz:/macbookpro08-centrim.sparsebundle/bands/1ef9
        twoz:/macbookpro08-centrim.sparsebundle/bands/1fe7
        twoz:/macbookpro08-centrim.sparsebundle/bands/58f
        twoz:/macbookpro08-centrim.sparsebundle/bands/2c7b
        twoz:/macbookpro08-centrim.sparsebundle/bands/590
        twoz:/macbookpro08-centrim.sparsebundle/bands/19
        twoz:/macbookpro08-centrim.sparsebundle/bands/2783
        twoz:/macbookpro08-centrim.sparsebundle/bands/2f23
        twoz:/macbookpro08-centrim.sparsebundle/bands/1883
        twoz:/macbookpro08-centrim.sparsebundle/bands/2588
        twoz:/macbookpro08-centrim.sparsebundle/bands/5fa1
        twoz:/macbookpro08-centrim.sparsebundle/bands/2585
        twoz:/macbookpro08-centrim.sparsebundle/bands/3f35
        twoz:/macbookpro08-centrim.sparsebundle/bands/285f
        twoz:/macbookpro08-centrim.sparsebundle/bands/6be
        twoz:/macbookpro08-centrim.sparsebundle/bands/2fcf
        twoz:/macbookpro08-centrim.sparsebundle/bands/6ceb
        twoz:/macbookpro08-centrim.sparsebundle/bands/11f3
        twoz:/macbookpro08-centrim.sparsebundle/bands/3e7c
        twoz:/macbookpro08-centrim.sparsebundle/bands/2e01
        twoz:/macbookpro08-centrim.sparsebundle/bands/112a
        twoz:/macbookpro08-centrim.sparsebundle/bands/1f6d
        twoz:/macbookpro08-centrim.sparsebundle/bands/2e7f
        twoz:/macbookpro08-centrim.sparsebundle/bands/2dc9
        twoz:/macbookpro08-centrim.sparsebundle/bands/1a0e
        twoz:/macbookpro08-centrim.sparsebundle/bands/2f2d
        twoz:/macbookpro08-centrim.sparsebundle/bands/28e7
        twoz:/macbookpro08-centrim.sparsebundle/bands/2bb2
        twoz:/macbookpro08-centrim.sparsebundle/bands/7210
        twoz@2013-03-17-131109:/macbookpro08-centrim.sparsebundle/bands/7244
        twoz@2013-01-02-231021:/macbookpro08-centrim.sparsebundle/bands/3252
        twoz@2013-01-02-231021:/macbookpro08-centrim.sparsebundle/bands/4aca
macbookpro08-centrim:~ gjp22$ clear





macbookpro08-centrim:~ gjp22$ zpool export twoz
macbookpro08-centrim:~ gjp22$ diskutil unmount /Volumes/LaCie\ Little\ Big\ Disk
Volume LaCie Little Big Disk on disk3s2 unmounted
macbookpro08-centrim:~ gjp22$


No surprise, many errors.

Now let's see whether – since the scrub is stopped – I can make other types of connection to this drive … yes:


I changed the pool from from failmode=continue to failmode=wait and have set aside the troublesome disk – avoid beginning another scrub of its pool. I might dust it off, out of curiosity, after something greater than ZEVO 1.1.1 is made available for OS X.

For a verbose history of the pool, sudo zdb -hvvvvv twoz.txt at http://www.wuala.com/grahamperrin/publi ... 03/29/d/b/
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

LaCie 301033EK gone bad

Post by grahamperrin » Tue Apr 02, 2013 1:07 am

Just for the record, another for the list:

LaCie 301033EK (160GB d2 Hard Drive Extreme with Triple Interface)

I knew that this disk was defective long, long ago; I set it aside. More recently I purchased Drive Genius 3, and over the long weekend I ran some scans. As expected, a significant number of blocks were spared (ninety-two during the first complete non-extended scan; I can't easily tell how many were silently spared in the past).

This drive will be dusted off and used only rarely. As with the other devices, I treat all data as disposable.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Previous

Return to General Discussion

Who is online

Users browsing this forum: ilovezfs and 0 guests

cron