windows and raid 1 corrupted
Posted: 24 Jul 2017, 11:04
Hi there - first of all thank you so much for all the work you do for all of us - hugely appreciated.
I've been struggling for over a week to try to resolve my main PC corrupted boot and file system. The long story is here:
https://www.tenforums.com/bsod-crashes- ... 5-2.html
but the short story is some sort of power/DIMM failure left me in a loop of windows 'your device needs repair error 0xc0000225' and absolutely NO windows based recovery tools will boot. Anything Linux based boots and runs happily for hours. (I have weeded out any suspect DIMMs by the way and run memtest successfully on the current configuration for the required 8 passes).
The log from Ubuntu Boot Rescue Disk ma ... /25161338/
The most useful tool has been Test Disk (thank you again )
it throws quite a lot of repeat errors on boot are these significant? Examples: ata1(or 2 or 3): soft reset failed (device not ready), ldm_parse_tocblock(): cannot find TOCBLOCK database may be corrupt, and "blk_update_request: I/O error, dev sr0, sector 559704" (139926 and 139927 also occur). Buffer I/O error on dev sr0, logical block 69963, async page read.
The other thing to mention is that my USB keyboard and mouse don't seem to load drivers correctly on about 50% of occasions of running test disk. Makes me start to question my motherboard/usb controller but the fact that keyboard works 100% of time in BIOS and when selecting keyboard map for Test Disk makes me think it is an issue with this Debian setup? Symptoms are: mouse cursor in middle of screen and frozen, keyboard unresponsive numlock on. Just tried it again and numlock became unresponsive about 5 seconds before X loaded on screen.
System details:
Windows 10 (from windows 7 original DVD upgraded online) was running on SDB / C: (Crucial M550 128Gb SSD) with 2 data HDD SDA and SDC in Windows controlled RAID 1
status:
cannot boot, have been able to copy some of the data from c: to an external drive. would settle for being able to install fresh from win7 dvd as long as I can still recover data from the other 2 HDD that were in Windows controlled RAID 1 mirror array? Whenever I've been brave enough to select 'write' in testdisk the next time I run it, it appears the partitions are still marked D; the only permanent change I seem to have achieved is in the boot record (actually I think this is my misunderstanding as there is a partition marked boot in the first screen below). I have tried to take screenshots throughout but unfortunately all the terminal ones have come out graphically garbled (I assume there's a trick concerning my radeon graphics device driver for me to learn)
testdisk analyse
Current partition structure:
1* HPFS - NTFS 0 1 1 15565 254 63 250067727
quick search:
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
The hardisk seems too small!
The following partition can't be recovered:
HPFS - NTFS 15565 254 63 31131 252 61 250067663
Continue:
D HPFS - NTFS 0 1 1 15565 254 63 250067727 (P = Can't open filesystem - seems damaged)
D HPFS - NTFS 0 2 2 15565 254 63 250067663 (P lists all directories and files but "can't be recovered"?)
If I mark the latter as boot (structure ok) and select deeper search:
It seemed to find 3 partitions briefly but then screen quickly returned to this:
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
The hardisk seems too small!
The following partition can't be recovered:
HPFS - NTFS 15565 254 63 31131 252 61 250067663
Selecting 'continue':
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
D HPFS - NTFS 0 1 1 15565 254 63 250067727
D HPFS - NTFS 0 2 2 15565 254 63 250067663
D HPFS - NTFS 15451 54 28 15508 147 63 921600 (P lists files - Windows Recovery winre.wim, boot.sdi etc and chkdisk log)
it looks to me like windows recovery has overwritten the middle useful partition which has all my c: structure and data in it - is there anything I can do? what would you do next please?
thank you again
Nick
I've been struggling for over a week to try to resolve my main PC corrupted boot and file system. The long story is here:
https://www.tenforums.com/bsod-crashes- ... 5-2.html
but the short story is some sort of power/DIMM failure left me in a loop of windows 'your device needs repair error 0xc0000225' and absolutely NO windows based recovery tools will boot. Anything Linux based boots and runs happily for hours. (I have weeded out any suspect DIMMs by the way and run memtest successfully on the current configuration for the required 8 passes).
The log from Ubuntu Boot Rescue Disk ma ... /25161338/
The most useful tool has been Test Disk (thank you again )
it throws quite a lot of repeat errors on boot are these significant? Examples: ata1(or 2 or 3): soft reset failed (device not ready), ldm_parse_tocblock(): cannot find TOCBLOCK database may be corrupt, and "blk_update_request: I/O error, dev sr0, sector 559704" (139926 and 139927 also occur). Buffer I/O error on dev sr0, logical block 69963, async page read.
The other thing to mention is that my USB keyboard and mouse don't seem to load drivers correctly on about 50% of occasions of running test disk. Makes me start to question my motherboard/usb controller but the fact that keyboard works 100% of time in BIOS and when selecting keyboard map for Test Disk makes me think it is an issue with this Debian setup? Symptoms are: mouse cursor in middle of screen and frozen, keyboard unresponsive numlock on. Just tried it again and numlock became unresponsive about 5 seconds before X loaded on screen.
System details:
Windows 10 (from windows 7 original DVD upgraded online) was running on SDB / C: (Crucial M550 128Gb SSD) with 2 data HDD SDA and SDC in Windows controlled RAID 1
status:
cannot boot, have been able to copy some of the data from c: to an external drive. would settle for being able to install fresh from win7 dvd as long as I can still recover data from the other 2 HDD that were in Windows controlled RAID 1 mirror array? Whenever I've been brave enough to select 'write' in testdisk the next time I run it, it appears the partitions are still marked D; the only permanent change I seem to have achieved is in the boot record (actually I think this is my misunderstanding as there is a partition marked boot in the first screen below). I have tried to take screenshots throughout but unfortunately all the terminal ones have come out graphically garbled (I assume there's a trick concerning my radeon graphics device driver for me to learn)
testdisk analyse
Current partition structure:
1* HPFS - NTFS 0 1 1 15565 254 63 250067727
quick search:
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
The hardisk seems too small!
The following partition can't be recovered:
HPFS - NTFS 15565 254 63 31131 252 61 250067663
Continue:
D HPFS - NTFS 0 1 1 15565 254 63 250067727 (P = Can't open filesystem - seems damaged)
D HPFS - NTFS 0 2 2 15565 254 63 250067663 (P lists all directories and files but "can't be recovered"?)
If I mark the latter as boot (structure ok) and select deeper search:
It seemed to find 3 partitions briefly but then screen quickly returned to this:
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
The hardisk seems too small!
The following partition can't be recovered:
HPFS - NTFS 15565 254 63 31131 252 61 250067663
Selecting 'continue':
Disk /dev/sdb - 128GB / 119 GiB - CHS 15566 255 63
D HPFS - NTFS 0 1 1 15565 254 63 250067727
D HPFS - NTFS 0 2 2 15565 254 63 250067663
D HPFS - NTFS 15451 54 28 15508 147 63 921600 (P lists files - Windows Recovery winre.wim, boot.sdi etc and chkdisk log)
it looks to me like windows recovery has overwritten the middle useful partition which has all my c: structure and data in it - is there anything I can do? what would you do next please?
thank you again
Nick