![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Filesystems, Disks and Memory Discuss NAS, SAN, RAID, Robotic Libraries, backup devices, RAM, DRAM, SCSI, IDE, EIDE topics here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| HP-UX Disk crash? | hoff | Filesystems, Disks and Memory | 7 | 09-07-2007 08:09 AM |
| how to handle system which become crash automatically | amitpansuria | UNIX for Dummies Questions & Answers | 0 | 09-02-2007 02:54 AM |
| HP-UX system crash help please!!! | efrenba | HP-UX | 1 | 05-19-2005 05:11 PM |
| Tru64 system crash | Ivo | UNIX for Dummies Questions & Answers | 2 | 07-25-2002 04:02 PM |
| Disk Crash | Kgatliffe | UNIX for Dummies Questions & Answers | 1 | 11-21-2001 06:08 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
System crash and Disk erasure !!!
I need some expert help, and would appreciate any feedback on the following problem:
After power outage the machine didn't allow the login. When we checked it , it looked like both disks were completely empty. Luckily, we have a backup machine, and we can restore the disks. Has anybody seen anything like this before ? What could cause such a dramatic outcome, and what can be done to prevent further problems ? I have no clue where I can start looking for explanation. So maybe somebody could help me which files I could take a look at and what are the best steps to perform in my situation ? Thanks in advance, Regards Dennis |
|
||||
|
This won't be much help. But the only thing I can think of that would cause your disks to appear erased like that is if the filesystems were damaged badly when the power spike hit your system. There is a tiny chance if you can somehow boot into maintenance mode (maybe booting off of CD or whatever) you could run fsck against your disks and repair them. But I've never seen damage that bad be fixable before.
The other possibility is that some damage was done to the cables or hardware of the disk itself. Or you were using a non-default device path and the boot prom got wiped out so now it can't find the boot disk. Stuff like that could also cause a problem like you describe I suppose. If you have backups that is probably easier than trying to fix it. . . . |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|