Go Back   Pro/Forums > ProCooling Technical Discussions > Snap Server / NAS / Storage Technical Goodies
Password
Register FAQ Members List Calendar Chat

Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides

Reply
Thread Tools
Unread 07-15-2007, 05:24 PM   #1
umerkhan
Cooling Neophyte
 
Join Date: Jul 2007
Location: Irvine, CA
Posts: 4
Default SNAP 1100 drive failure - need help!

I can't access the drive at all and I have a ton of data on it without any backups :-( Please help. What can I do to recover data from this drive? If there is a bad sector, is there any way to mark it bad but recover the rest of the data?

07/15/2007 15:56:07 Command: in lo t

Requested: Log=Temporary, Boot=N/A Direction=Fwd Types=All Source=All

07/15/2007 15:35:43 31 S SYS | System Initialization : Server v3.4.772
Build Date: Feb 28 2002 20:25:06
Boot Count: 31
07/15/2007 15:35:43 31 D SYS | Executable built by KEVIN
07/15/2007 15:35:43 31 D SYS | Hardware platform:3.1.2 Model:1 (32 MBytes) S/N:122992
07/15/2007 15:35:43 31 D SYS | DISK: Initial ARBs: 63 Memory: 10332
07/15/2007 15:35:43 31 D SYS | Disk cache flush enabled
07/15/2007 15:35:51 31 D SYS | Intf: 0, dev: 0: Model: QUANTUM FIREBALLlct15 30
07/15/2007 15:35:51 31 D SYS | Firmware Rev: A01.0F00 Serial #: 614030329892
07/15/2007 15:35:51 31 D SYS | ETH: Reset- Eaddr set to 00 C0 B6 01 E0 70
07/15/2007 15:35:51 31 D SYS | Update IP...
07/15/2007 15:35:51 31 I NET | INIT: Setting IP address to 192.168.1.4
07/15/2007 15:35:51 31 D SYS | Update IP...
07/15/2007 15:35:51 31 D SYS | Initial file system BIO cache size is 3354816 bytes, 404 buffers
07/15/2007 15:35:51 31 D SYS | DISK: Additional ARBs: 341 (Mem: 55924) Total Arbs: 404 (Mem: 66256)
07/15/2007 15:35:51 31 D SYS | Code Page set to 437
07/15/2007 15:35:51 31 D SYS | QDL System is DISABLED
07/15/2007 15:35:51 31 I L00 | File System Check : Executing fsck /dev/ride0g /fix /fixfatal
07/15/2007 15:35:51 31 I L00 | File System Check : partition is clean.
07/15/2007 15:35:52 31 D SYS | SNMP agent disabled.
07/15/2007 15:35:52 31 D SYS | AFP: not started
07/15/2007 15:35:52 31 D SYS | 'FTPD' started.
07/15/2007 15:35:52 31 D SYS | Update WorkGroup...
07/15/2007 15:35:52 31 D SYS | Update FDB 0x10006...
07/15/2007 15:35:52 31 I L00 | File System : Opened FDB for device 0x10006
07/15/2007 15:35:52 31 D SYS | Scheduled ACL Set and Propagate at /priv/os_private for FDB_ID_12
07/15/2007 15:35:52 31 I L01 | File System Check : Executing fsck /dev/ride0a /fix
07/15/2007 15:35:52 31 D SYS | Propagate on /priv/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
07/15/2007 15:35:52 31 W L01 | File System Check : partition is NOT clean.
07/15/2007 15:35:52 31 D SYS | Fsck - Using primary superblock
07/15/2007 15:35:52 31 D SYS | 11526320 bytes pre-allocated
07/15/2007 15:35:52 31 D SYS | Memory allocation for i-node cache: 90% of free RAM
07/15/2007 15:35:52 31 D L01 | File System Check : Failed to allocate 10914820 bytes for rcd_backlinks!!!
07/15/2007 15:35:52 31 D SYS | -- Swap-based Fsck --
07/15/2007 15:35:52 31 D SYS | 2304 i-node cache blocks, cache hash table: 1021 entries
07/15/2007 15:35:52 31 D SYS | 256 i-nodes per generic cache block
07/15/2007 15:35:52 31 D SYS | 170 i-nodes per directory cache block
07/15/2007 15:35:52 31 I L01 | File System Check : ** Phase 1 - Check blocks and sizes
07/15/2007 15:39:07 31 D NET | INET: sendit: send err 39
07/15/2007 15:39:07 31 D NET | INET: sendit: send err 39
07/15/2007 15:39:09 31 D SYS | Previous msg repeating... Occurs 5 times!
07/15/2007 15:39:09 31 D NET | sonewconn: backlog too large
07/15/2007 15:39:09 31 D NET | INET: sendit: send err 39
07/15/2007 15:39:09 31 D NET | sonewconn: backlog too large
07/15/2007 15:39:09 31 D NET | sonewconn: backlog too large
07/15/2007 15:53:43 31 D SYS | Previous msg repeating... Occurs 16 times!
07/15/2007 15:53:43 31 D SYS | DISK: req=0x7E814 dev=0xC0000 fn=1 blk=0x37C4260 sts=20
07/15/2007 15:53:44 31 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 15:53:46 31 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 15:54:06 31 D SYS | DISK: req=0x7E814 dev=0xC0000 fn=1 blk=0x37C4260 sts=7
07/15/2007 15:54:07 31 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 15:54:08 31 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 15:54:08 31 D SYS | DISK: req=0x7E814 dev=0x80000 fn=1 blk=0x37C4260 sts=7
07/15/2007 15:54:08 31 E D[80070000] | Disk Driver : Cannot Read Device 80070000 Block 58043344
07/15/2007 15:54:08 31 E L01 | File System Check : Cannot Read: Blk 58043344
07/15/2007 15:54:08 31 E L01 | File System Check : FSCK fatal error = 4
07/15/2007 15:54:08 31 D SYS | Fsck cache statistics:
07/15/2007 15:54:08 31 D SYS | total memory used for cache: 9846872 bytes
07/15/2007 15:54:08 31 D SYS | total number of directories: 2546
07/15/2007 15:54:08 31 D SYS | maximum depth of recursion in sorting: 0
07/15/2007 15:54:08 31 D SYS | number of swaps in sorting phase: 0
07/15/2007 15:54:08 31 D SYS | ----- generic i-node cache -----
07/15/2007 15:54:08 31 D SYS | cache entries: 3067
07/15/2007 15:54:08 31 D SYS | cache hits: 2057443 (99%)
07/15/2007 15:54:08 31 D SYS | cache misses: 7693 (0%)
07/15/2007 15:54:08 31 D SYS | reused cache entries: 5394
07/15/2007 15:54:08 31 D SYS | total reads from swap device: 0
07/15/2007 15:54:08 31 D SYS | total writes to swap device: 5394
07/15/2007 15:54:08 31 D SYS | total writes skipped (clean blocks): 0
07/15/2007 15:54:08 31 D SYS | average successful cache lookup: 1.00 iterations
07/15/2007 15:54:08 31 D SYS | maximum successful cache lookup: 1 iterations
07/15/2007 15:54:08 31 D SYS | average unsuccessful cache lookup: 1.00 iterations
07/15/2007 15:54:08 31 D SYS | maximum unsuccessful cache lookup: 1 iterations
07/15/2007 15:54:08 31 D SYS | ----- directory i-node cache -----
07/15/2007 15:54:08 31 D SYS | cache entries: 1541
07/15/2007 15:54:08 31 D SYS | cache hits: 2546 (100%)
07/15/2007 15:54:08 31 D SYS | cache misses: 0 (0%)
07/15/2007 15:54:08 31 D SYS | reused cache entries: 10
07/15/2007 15:54:08 31 D SYS | total reads from swap device: 0
07/15/2007 15:54:08 31 D SYS | total writes to swap device: 10
07/15/2007 15:54:08 31 D SYS | total writes skipped (clean blocks): 0
07/15/2007 15:54:08 31 D SYS | average successful cache lookup: 1.00 iterations
07/15/2007 15:54:08 31 D SYS | maximum successful cache lookup: 1 iterations
07/15/2007 15:54:08 31 D SYS | average unsuccessful cache lookup: 0.00 iterations
07/15/2007 15:54:08 31 D SYS | maximum unsuccessful cache lookup: 0 iterations
07/15/2007 15:54:08 31 D SYS | NFS: The hash table has been initialized.
07/15/2007 15:54:08 31 D SYS | NFS: the NFSID <--->FDBID cache has been initialised.
07/15/2007 15:54:08 31 D SYS | NFS Server started.
07/15/2007 15:54:08 31 D SYS | suspend_factor = 2AF77
07/15/2007 15:54:08 31 D SYS | DISK: Additional ARBs: 2443 (Mem: 400652) Total Arbs: 2847 (Mem: 466908)
07/15/2007 15:54:08 31 I SYS | System Initialization : Initialization Complete! Memory to be released: 20286672 bytes.
07/15/2007 15:54:09 31 D SYS | Restarted process timing

eventLogGetRecord() printed 90 records at 07/15/2007 15:56:07
umerkhan is offline   Reply With Quote
Unread 07-15-2007, 05:38 PM   #2
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: SNAP 1100 drive failure - need help!

On bad sectors you have 2 options.

If your not going to use a recovery service (1) Give SpinRite (2) a try, it has workEd for some users.

DO NOT TRY TO MOUNT WITH ANY FILE SYSTEM (window or Linux). Unless you want to loose every thing. Spinrite works at the controller data and does not try to inturpit data, so it's save.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote
Unread 07-15-2007, 05:44 PM   #3
umerkhan
Cooling Neophyte
 
Join Date: Jul 2007
Location: Irvine, CA
Posts: 4
Default Re: SNAP 1100 drive failure - need help!

Quote:
Originally Posted by blue68f100
On bad sectors you have 2 options.
Thank you so much for your help. Given the logs, does it seem like a bad sector problem?
umerkhan is offline   Reply With Quote
Unread 07-16-2007, 02:23 PM   #4
umerkhan
Cooling Neophyte
 
Join Date: Jul 2007
Location: Irvine, CA
Posts: 4
Default Re: SNAP 1100 drive failure - need help!

Wow. I have been able to SAVE my data somehow. I restarted the Snap a couple of more times, without success, getting logs like the one below:

07/15/2007 16:34:21 Command: in lo t

Requested: Log=Temporary, Boot=N/A Direction=Fwd Types=All Source=All

07/15/2007 16:25:52 32 S SYS | System Initialization : Server v3.4.772
Build Date: Feb 28 2002 20:25:06
Boot Count: 32
07/15/2007 16:25:52 32 D SYS | Executable built by KEVIN
07/15/2007 16:25:52 32 D SYS | Hardware platform:3.1.2 Model:1 (32 MBytes) S/N:122992
07/15/2007 16:25:52 32 D SYS | DISK: Initial ARBs: 63 Memory: 10332
07/15/2007 16:25:52 32 D SYS | Disk cache flush enabled
07/15/2007 16:25:59 32 D SYS | Intf: 0, dev: 0: Model: QUANTUM FIREBALLlct15 30
07/15/2007 16:25:59 32 D SYS | Firmware Rev: A01.0F00 Serial #: 614030329892
07/15/2007 16:25:59 32 D SYS | ETH: Reset- Eaddr set to 00 C0 B6 01 E0 70
07/15/2007 16:25:59 32 D SYS | Update IP...
07/15/2007 16:25:59 32 I NET | INIT: Setting IP address to 192.168.1.4
07/15/2007 16:25:59 32 D SYS | Update IP...
07/15/2007 16:25:59 32 D SYS | Initial file system BIO cache size is 3354816 bytes, 404 buffers
07/15/2007 16:25:59 32 D SYS | DISK: Additional ARBs: 341 (Mem: 55924) Total Arbs: 404 (Mem: 66256)
07/15/2007 16:25:59 32 D SYS | Code Page set to 437
07/15/2007 16:26:00 32 D SYS | QDL System is DISABLED
07/15/2007 16:26:00 32 I L00 | File System Check : Executing fsck /dev/ride0g /fix /fixfatal
07/15/2007 16:26:00 32 I L00 | File System Check : partition is clean.
07/15/2007 16:26:00 32 D SYS | SNMP agent disabled.
07/15/2007 16:26:00 32 D SYS | AFP: not started
07/15/2007 16:26:00 32 D SYS | 'FTPD' started.
07/15/2007 16:26:00 32 D SYS | Update WorkGroup...
07/15/2007 16:26:00 32 D SYS | Update FDB 0x10006...
07/15/2007 16:26:00 32 I L00 | File System : Opened FDB for device 0x10006
07/15/2007 16:26:00 32 D SYS | Scheduled ACL Set and Propagate at /priv/os_private for FDB_ID_12
07/15/2007 16:26:00 32 I L01 | File System Check : Executing fsck /dev/ride0a /force /fix
07/15/2007 16:26:00 32 D SYS | Propagate on /priv/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
07/15/2007 16:26:00 32 W L01 | File System Check : partition is NOT clean.
07/15/2007 16:26:00 32 D SYS | Fsck - Using primary superblock
07/15/2007 16:26:00 32 D SYS | 11526320 bytes pre-allocated
07/15/2007 16:26:00 32 D SYS | Memory allocation for i-node cache: 90% of free RAM
07/15/2007 16:26:00 32 D L01 | File System Check : Failed to allocate 10914820 bytes for rcd_backlinks!!!
07/15/2007 16:26:00 32 D SYS | -- Swap-based Fsck --
07/15/2007 16:26:00 32 D SYS | 2304 i-node cache blocks, cache hash table: 1021 entries
07/15/2007 16:26:00 32 D SYS | 256 i-nodes per generic cache block
07/15/2007 16:26:00 32 D SYS | 170 i-nodes per directory cache block
07/15/2007 16:26:00 32 I L01 | File System Check : ** Phase 1 - Check blocks and sizes
07/15/2007 16:32:56 32 D SYS | DISK: req=0x7F54C dev=0xC0000 fn=1 blk=0x14397D0 sts=20
07/15/2007 16:32:58 32 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 16:32:59 32 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 16:33:32 32 D SYS | DISK: req=0x7F54C dev=0xC0000 fn=1 blk=0x14397D0 sts=7
07/15/2007 16:33:34 32 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 16:33:35 32 D SYS | DISK: req=0x38B08 dev=0xC0001 fn=3 blk=0xC0000 sts=5
07/15/2007 16:33:35 32 D SYS | DISK: req=0x7F54C dev=0x80000 fn=1 blk=0x14397D0 sts=7
07/15/2007 16:33:35 32 E D[80070000] | Disk Driver : Cannot Read Device 80070000 Block 20775232
07/15/2007 16:33:35 32 E L01 | File System Check : Cannot Read: Blk 20775232
07/15/2007 16:33:35 32 E L01 | File System Check : FSCK fatal error = 4
07/15/2007 16:33:35 32 D SYS | Fsck cache statistics:
07/15/2007 16:33:35 32 D SYS | total memory used for cache: 9846872 bytes
07/15/2007 16:33:35 32 D SYS | total number of directories: 1268
07/15/2007 16:33:35 32 D SYS | maximum depth of recursion in sorting: 0
07/15/2007 16:33:35 32 D SYS | number of swaps in sorting phase: 0
07/15/2007 16:33:35 32 D SYS | ----- generic i-node cache -----
07/15/2007 16:33:35 32 D SYS | cache entries: 3066
07/15/2007 16:33:35 32 D SYS | cache hits: 1013824 (99%)
07/15/2007 16:33:35 32 D SYS | cache misses: 3804 (0%)
07/15/2007 16:33:35 32 D SYS | reused cache entries: 1506
07/15/2007 16:33:35 32 D SYS | total reads from swap device: 0
07/15/2007 16:33:35 32 D SYS | total writes to swap device: 1506
07/15/2007 16:33:35 32 D SYS | total writes skipped (clean blocks): 0
07/15/2007 16:33:35 32 D SYS | average successful cache lookup: 1.00 iterations
07/15/2007 16:33:35 32 D SYS | maximum successful cache lookup: 1 iterations
07/15/2007 16:33:35 32 D SYS | average unsuccessful cache lookup: 1.00 iterations
07/15/2007 16:33:35 32 D SYS | maximum unsuccessful cache lookup: 1 iterations
07/15/2007 16:33:35 32 D SYS | ----- directory i-node cache -----
07/15/2007 16:33:35 32 D SYS | cache entries: 1542
07/15/2007 16:33:35 32 D SYS | cache hits: 1268 (100%)
07/15/2007 16:33:35 32 D SYS | cache misses: 0 (0%)
07/15/2007 16:33:35 32 D SYS | reused cache entries: 2
07/15/2007 16:33:35 32 D SYS | total reads from swap device: 0
07/15/2007 16:33:35 32 D SYS | total writes to swap device: 2
07/15/2007 16:33:35 32 D SYS | total writes skipped (clean blocks): 0
07/15/2007 16:33:35 32 D SYS | average successful cache lookup: 1.00 iterations
07/15/2007 16:33:35 32 D SYS | maximum successful cache lookup: 1 iterations
07/15/2007 16:33:35 32 D SYS | average unsuccessful cache lookup: 0.00 iterations
07/15/2007 16:33:35 32 D SYS | maximum unsuccessful cache lookup: 0 iterations
07/15/2007 16:33:35 32 D SYS | NFS: The hash table has been initialized.
07/15/2007 16:33:35 32 D SYS | NFS: the NFSID <--->FDBID cache has been initialised.
07/15/2007 16:33:35 32 D SYS | NFS Server started.
07/15/2007 16:33:35 32 D SYS | suspend_factor = 2AF77
07/15/2007 16:33:35 32 D SYS | DISK: Additional ARBs: 2445 (Mem: 400980) Total Arbs: 2849 (Mem: 467236)
07/15/2007 16:33:35 32 I SYS | System Initialization : Initialization Complete! Memory to be released: 20303280 bytes.
07/15/2007 16:33:35 32 D SYS | Restarted process timing

eventLogGetRecord() printed 82 records at 07/15/2007 16:34:22

------------
Command executed without error.


Very similar to the one I got earlier, except pointing to a different block! So I had full intention to run SpinRite to see if I could recover the drive. But had to run off somewhere, so powered off the Snap, and returned home after a few years. I thought I might as well give it one more shot before I tried SpinRite, or putting the drive in the fridge or anything like that. It took an AWFULLY long time to go through fsck, but somehow made it through 5 phases and did some repairs. After bootup, I was able to see my data! I quickly started copying my files off. After a while, it crapped out again, and needed another rebooted. I copied some more files. Then another reboot. And then the final set of files were retrieved. SOMEHOW, I was able to salvage 100% of my data, which is amazing. So I didn't have to go down the http://www.dtidata.com/snap_server_recovery.htm route. Phew!
umerkhan is offline   Reply With Quote
Unread 07-16-2007, 02:40 PM   #5
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: SNAP 1100 drive failure - need help!

You need to use Digital Dolly and copy the Boot Trackes FIRST. You will need 30meg of the first trackes to load on a new drive. Make sure you do this first or you will be hunting for the image files. The instructions on replace the drive is in the FAQ's. And DD instructions are in the WIKI section of the forum.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote
Unread 07-16-2007, 11:04 PM   #6
umerkhan
Cooling Neophyte
 
Join Date: Jul 2007
Location: Irvine, CA
Posts: 4
Default Re: SNAP 1100 drive failure - need help!

Thanks, but after retrieving my files, I basically threw out the drive and the whole unit. I've had it for 7 years, and now it is just too slow anyway. Need to upgrade to something faster :-)
umerkhan is offline   Reply With Quote
Unread 07-17-2007, 08:18 AM   #7
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: SNAP 1100 drive failure - need help!

Most of us have moved up to Snap4500 units. These are smoking machines, but still use the IDE interface. The newer models are SATA.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 04:44 PM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com
If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk...
Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...