Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › HELPP need to restore raid5 using Knoppix
New Posts  All Forums:Forum Nav:

HELPP need to restore raid5 using Knoppix - Page 4

post #31 of 39
Thread Starter 
Quote:
[root@localhost liveuser]# tune2fs -O has_journal -J device=/dev/md1 /dev/md0
tune2fs 1.41.12 (17-May-2010)
tune2fs: Bad magic number in super-block
while trying to open journal on /dev/md1
It allowed me to install the extundelete but this command won't work and the extundelete gives me a "journal not found " error
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
post #32 of 39
Quote:
Originally Posted by da tick 07 View Post
It allowed me to install the extundelete but this command won't work and the extundelete gives me a "journal not found " error
OK, well that either wasn't the journal, or it was the journal and is too corrupted to be readable. Based on the info you provided earlier, if anything else on the array contained the journal, then the journal is unrecoverable, as there weren't any other arrays that had 3 or more (of the 4) usable partitions.

So we're at the last resort: photorec. This is a powerful but rather complex tool. Again, there is no way to recover in-place; you will need a temporary hard drive to recover files into. This should already be on the Live CD; if it isn't, you can install it with:

Code:
yum install testdisk
I assume that the temporary hard drive comes up as /dev/sde and contains one partition, /dev/sde1 (your drive may vary) and that you will mount a temporary drive at /recovery for the code examples given though you can put it somewhere else if you desire.

Code:
mkdir /recovery
mount /dev/sde1 /recovery

photorec /d /recovery /cmd /dev/md0 partition_none,options,mode_ext2,fileopt,everything,enable,search
This last will preset photorec's options to attempt to recover everything possible from the array. It may take several hours. Once this is done, your temporary drive will be stuffed full of files, many of which may end up being old binaries, includes, or just random garbage that you thought you deleted months ago. Some files may even be incomplete. The really hard part will be going through all of it.
Edited by error10 - 5/9/11 at 7:26pm
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
post #33 of 39
Thread Starter 
Quote:
Originally Posted by error10 View Post
OK, well that either wasn't the journal, or it was the journal and is too corrupted to be readable. Based on the info you provided earlier, if anything else on the array contained the journal, then the journal is unrecoverable, as there weren't any other arrays that had 3 or more (of the 4) usable partitions.

So we're at the last resort: photorec. This is a powerful but rather complex tool. Again, there is no way to recover in-place; you will need a temporary hard drive to recover files into. This should already be on the Live CD; if it isn't, you can install it with:

Code:
yum install testdisk
I assume that the temporary hard drive comes up as /dev/sde and contains one partition, /dev/sde1 (your drive may vary) and that you will mount a temporary drive at /recovery for the code examples given though you can put it somewhere else if you desire.

Code:
mkdir /recovery
mount /dev/sde1 /recovery

photorec /d /recovery /cmd /dev/md0 partition_none,options,mode_ext2,fileopt,everything,enable,search
This last will preset photorec's options to attempt to recover everything possible from the array. It may take several hours. Once this is done, your temporary drive will be stuffed full of files, many of which may end up being old binaries, includes, or just random garbage that you thought you deleted months ago. Some files may even be incomplete. The really hard part will be going through all of it.
This command worked but it got to 33 files and then went to the blue start up screen with the fedora logo in the middle. The recovery drive is still spinning a lot so it seems like it is still working. Is this normal?
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
post #34 of 39
Quote:
Originally Posted by da tick 07 View Post
This command worked but it got to 33 files and then went to the blue start up screen with the fedora logo in the middle. The recovery drive is still spinning a lot so it seems like it is still working. Is this normal?
You mean the screensaver kicked in? Or the GUI died? The latter doesn't seem likely but I suppose it's possible. Though if this had happened, I'd expect photorec to have died. But if it still seems to be running, i.e. accessing your array and writing to the recovery disk, then by all means let it run. If not, I'd start it over.
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
post #35 of 39
Thread Starter 
Well all the drives are spinning except for the "dead" drive so I assume that they are being accessed
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
post #36 of 39
Quote:
Originally Posted by da tick 07 View Post
Well all the drives are spinning except for the "dead" drive so I assume that they are being accessed
If the lights are blinking, you're probably good. If they're all just solid on, then the computer probably locked up.
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
post #37 of 39
Thread Starter 
The network lights are blinking so I'll let it run
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
post #38 of 39
Thread Starter 
I reran the command and it continues to crash. It will get 33 files and will not go any further. Sometimes it crashes the terminal and then goes to the blue fedora screen and others is goes straight to that screen.

I can see some files on the hard drive using a command that gives me root access to the folder and lets me view hidden files but it still says that I don't have permission to open them
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
Mitx Love
(13 items)
 
  
CPUMotherboardRAMHard Drive
Pentium G6950 Zotac H55 ITX 2x2GB Kingston 500GB Hitachi 
OSPowerMouseMouse Pad
Windows Server 2008 R2 Lite-on 300w Logitech Wireless Laser ULTRA wrist rest 
  hide details  
Reply
post #39 of 39
Quote:
Originally Posted by da tick 07 View Post
I reran the command and it continues to crash. It will get 33 files and will not go any further. Sometimes it crashes the terminal and then goes to the blue fedora screen and others is goes straight to that screen.
That makes me suspect that one of the three remaining drives is also going bad (which I think I might have already mentioned).

What I think I would do at this point is to run Spinrite on each of the three drives (at level 5) to see if it can repair anything and then try the photorec procedure again. But I have a copy of Spinrite; you might not, and you would have to obtain one.
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
Underground
(14 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 C0 ASUS P6T6 WS Revolution GTX 460 TR3X6G1600C8D 
Hard DriveOptical DriveCoolingOS
WD1001FALS SAMSUNG SH-S223F 22X DVD MULTI Corsair H50 Fedora 16 KDE x86_64 
MonitorKeyboardPowerCase
HP w19b Microsoft Comfort Curve Corsair CX600 Thermaltake Armor VA8003BWS 
MouseMouse Pad
Razer DeathAdder Black 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › HELPP need to restore raid5 using Knoppix