|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
Thread Tools |
09-13-2007, 07:27 PM | #1 |
Cooling Neophyte
Join Date: Sep 2007
Location: us
Posts: 3
|
Got 4100 UP but fatal error
I got the SNAP 4100 going. The processor fan has failed and the unit appears to have overheated. I have another fan on it now and have got it to boot up. It tries to check the status of the disk, it made it to 85%, then gave an error.
Here is a cut from the log: E File System Check : FSCK fatal error = 39 Disk 60000 9/13/2007 10:18:00 PM E File System Check : Bad state 7 for inode I=6235992 Disk 60000 9/13/2007 10:18:00 PM W File System Check : Summary information bad (Salvaged) Disk 60000 9/13/2007 10:16:55 PM W File System Check : Blk(s) missing in bit maps (Salvaged) Disk 60000 9/13/2007 10:16:55 PM W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 60000 9/13/2007 10:16:55 PM I File System Check : ** Phase 5 - Check cylinder groups Disk 60000 9/13/2007 10:16:43 PM I File System Check : ** Phase 4b - Check backlinks Disk 60000 9/13/2007 10:16:31 PM I File System Check : ** Phase 4 - Check reference counts Disk 60000 9/13/2007 10:16:12 PM I File System Check : ** Phase 3 - Check connectivity Disk 60000 9/13/2007 10:16:12 PM I File System Check : ** Phase 2 - Check pathnames Disk 60000 9/13/2007 10:15:57 PM I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 60000 9/13/2007 10:15:57 PM I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 9/13/2007 10:09:51 PM W File System Check : partition is NOT clean. Disk 60000 9/13/2007 10:09:51 PM I File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal Disk 60000 9/13/2007 10:09:50 PM Any ideas? |
09-13-2007, 09:10 PM | #2 |
Cooling Neophyte
Join Date: Sep 2007
Location: us
Posts: 3
|
Re: Got 4100 UP but fatal error
Nevermind, I got all the data except for a few directories which are not accesible and a few files (maybe 10 to 20 files) that have 1 kb size and are garbage. Overall, it was a sucess.
I removed the power and IDE cable from drive 4, booted the unit and let it check the disk. It finally came back that the volume had failed and was in a degraded state, however, the data was then accessible via normal means. I have several hours into this job (over 6 hours counting the original imaging of the drives, etc..), however, my customer was being quoted over $10,000.00 for data recovery. My bill will closer to $1,000.00! cheers. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|