Re: FileSystem Corruptions? Very important Files at stake.
On Sat, 8 Oct 2005, Justin Wong wrote: Hi, I was wondering if you could help me. After searches on the internet turned up nothing, I found your site about your love for OpenBSD. My problem is that when I boot, I get an error /dev/rwd0a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE. Then, on the same 13 gig drive, the error, /dev/rwd0a UNEXPECTED INCONSISTENCY RUN fsck_ffs MANUALLY . Later on, I also get an error from my other HardDRive which is a 200 gig Seagate. This drive is also getting many errors. I did not realise it, but I guess I had formatted it in NTFS. This HardDrive contains many files of which are very important (3 years worth of files and a few thousand family photos). If the contents of the drive are really, really important to you and you are willing to spend (lots of) money to retrieve it, send it to Ibas. Don't do anything more, just shut down the computer, disconnect the drives, and give them a call, to them as best you can what has happened, and they will give you directions as to what to do. www.ibas.com is the place to visit now, or call their 24/7 international emergency hotline at +47 62 81 01 00. Oh, and always keep a backup. Cheers, Christer
FileSystem Corruptions? Very important Files at stake.
Hi, I was wondering if you could help me. After searches on the internet turned up nothing, I found your site about your love for OpenBSD. My problem is that when I boot, I get an error /dev/rwd0a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE. Then, on the same 13 gig drive, the error, /dev/rwd0a UNEXPECTED INCONSISTENCY RUN fsck_ffs MANUALLY . Later on, I also get an error from my other HardDRive which is a 200 gig Seagate. This drive is also getting many errors. I did not realise it, but I guess I had formatted it in NTFS. This HardDrive contains many files of which are very important (3 years worth of files and a few thousand family photos). The only thing I can remember that might be related to the error is that the computer would not shut down the previous night. I am relatively new to OpenBSD so I shurgged it off as I held the power button down. I made sure the HDD activity light was off. I am using OpenBSD 3.7. When I type login I get a #sh not found error and it seems to continue. From there I get thousands of errors where the computer tells me to fsck. From my view, it looks like both filesystems became corrupted. I really need these files. A liveCD of Ubuntu doesn't seem to be working as it can't read the 200 gig drive. The 13 gig drive comes up with a nod error every couple or so nodes with fsck. Ubuntu won't even read the 200 gig drive. Can you please help me at least to recover hte files? Any suggestions would help. THe computer is a 500Mhz K6 with the 13 gig drive run as master and the 200 gig drive as slave. Some of these files are photographs of my now deceased grandfather and are very important. Thank you for your time. Justin Wong. -- $ cat food in tin cans cat: cannot open food in tin cans
Re: FileSystem Corruptions? Very important Files at stake.
Justin Wong wrote: Hi, I was wondering if you could help me. ... Some of these files are photographs of my now deceased grandfather and are very important. After some disasters here, although in my/our case caused by human errors, I have written two programs that scans a file of choice for 1) avi files and 2) jpeg files It can scan any file, be it a image file, disk image, or the disk device itself (e.g. /dev/rwd0c). The script will only be able to restore images and movies that are located sequentially (non-fragmented) on disk, and may therefore miss some images/movies, as well as find invalid ones. I have successfully tested the script on two occations, but that was on msdos (and possibly ntfs) file systems. I have not tested it on an ffs file system. So, if you can get another installation of openbsd running, and manage to get the disk device (e.g. /dev/rwd1c), or ripped disk image, readable by any means, then I can probably help you retrieve many, if not most, but probably not all, jpg's and avi's. Be aware that all images, including previously deleted but not yet overwritten ones, may be retrieved. :-) The file names are obviously not restored either, so some sorting is to be done afterwards. I have a script that can help you with some of that too, if you need it. :) Good luck! /Alexander
Re: FileSystem Corruptions? Very important Files at stake.
The first thing to do is to copy the drive with the photos to fresh disk space before further damage is done to the originals. Expect recovery to be long and painful even with some tools to make it easier. There are people here that know a lot more about this than I, but the first thing is to get lots of accessible disk space in which to put: 1) the raw image of the original disk 2) the raw images of the disk partitions (dos partitions, that is) 3) the raw images of the disk partitions (obsd partitions, that is) 4) space in which to attemp reconstructions of what was supposed to be there. If you really know what you are doing, you can probably get away with omitting some of the above. Make accurate notes of what is where in what order etc. Good luck. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Justin Wong Sent: Saturday, October 08, 2005 4:46 PM To: misc@openbsd.org Subject: FileSystem Corruptions? Very important Files at stake. Hi, I was wondering if you could help me. After searches on the internet turned up nothing, I found your site about your love for OpenBSD. My problem is that when I boot, I get an error /dev/rwd0a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE. Then, on the same 13 gig drive, the error, /dev/rwd0a UNEXPECTED INCONSISTENCY RUN fsck_ffs MANUALLY . Later on, I also get an error from my other HardDRive which is a 200 gig Seagate. This drive is also getting many errors. I did not realise it, but I guess I had formatted it in NTFS. This HardDrive contains many files of which are very important (3 years worth of files and a few thousand family photos). The only thing I can remember that might be related to the error is that the computer would not shut down the previous night. I am relatively new to OpenBSD so I shurgged it off as I held the power button down. I made sure the HDD activity light was off. I am using OpenBSD 3.7. When I type login I get a #sh not found error and it seems to continue. From there I get thousands of errors where the computer tells me to fsck. From my view, it looks like both filesystems became corrupted. I really need these files. A liveCD of Ubuntu doesn't seem to be working as it can't read the 200 gig drive. The 13 gig drive comes up with a nod error every couple or so nodes with fsck. Ubuntu won't even read the 200 gig drive. Can you please help me at least to recover hte files? Any suggestions would help. THe computer is a 500Mhz K6 with the 13 gig drive run as master and the 200 gig drive as slave. Some of these files are photographs of my now deceased grandfather and are very important. Thank you for your time. Justin Wong. -- $ cat food in tin cans cat: cannot open food in tin cans
Re: FileSystem Corruptions? Very important Files at stake.
STOP -- DON'T DO ANYTHING ELSE w/o expert help at your side. Justin Wong wrote: Hi, I was wondering if you could help me. After searches on the internet turned up nothing, I found your site about your love for OpenBSD. My problem is that when I boot, I get an error /dev/rwd0a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE. Then, on the same 13 gig drive, the error, /dev/rwd0a UNEXPECTED INCONSISTENCY RUN fsck_ffs MANUALLY . Later on, I also get an error from my other HardDRive which is a 200 gig Seagate. This drive is also getting many errors. I did not realise it, but I guess I had formatted it in NTFS. How can you format a disk and not realize it? Do you mean you formatted a disk already containing data? ... do you mean you formatted the disk and then transferred the data to it? Are you set up for dual booting of Windows and OBSD? Otherwise how did NTFS get involved. You need to describe your environment and the sequence of steps preceding your catastrophe. This HardDrive contains many files of which are very important (3 years worth of files and a few thousand family photos). Data is only important if it is treated as though it is important. If it's important, then it's backed up. The only thing I can remember that might be related to the error is that the computer would not shut down the previous night. I am relatively new to OpenBSD so I shurgged it off as I held the power button down. I made sure the HDD activity light was off. When you typed the shutdown or halt command, what happened? I am using OpenBSD 3.7. When I type login I get a #sh not found error and it seems to continue. From there I get thousands of errors where the computer tells me to fsck. From my view, it looks like both filesystems became corrupted. I really need these files. You are probably correct in thinking both filesystems are corrupted. A liveCD of Ubuntu doesn't seem to be working as it can't read the 200 gig drive. The Ubintu CD is working just fine. You are asking the programs on it to perform a task they cannot do. The 13 gig drive comes up with a nod error every couple or so nodes with fsck. Ubuntu won't even read the 200 gig drive. Can you please help me at least to recover hte files? Any suggestions would help. THe computer is a 500Mhz K6 with the 13 gig drive run as master and the 200 gig drive as slave. I don't mean to be unkind during your distress, but this is entirely the result of you own actions. Trying to run fsck on an NTFS filesystem is likely to make any recovery impossible. Some of these files are photographs of my now deceased grandfather and are very important. I'm sorry to say this, but your files may be irretrievably gone. The best advice I can give at this point is to find somebody who has expert knowledge of whichever file system is involved (BSD or NTFS) and let them take over. Maybe there is a data disk recovery shop near you. The good ones are expensive. Thank you for your time. Da nada, Sorry to be the bearer of bad news. All the best, Ray
