Re: ZFS pool data recovery
On 18.02.2013 16:06, Jonni Nakari wrote: I started zpool import -nfFX vault but it seems to take quite long. Some more information about my system: zpool vault consists of 5 block devices: whole disks: ada1, ada2, ada3 cache: ada0s1e log: ada0s1d The system boots from a UFS filesystem ada0s1a. The command root@:/root # zpool import -nfFX vault returned after few hours: Would be able to return vault to its state as of Sun Feb 17 03:07:36 2013. Would discard approximately 20 minutes of transactions. So I ran root@:/root # zpool import -fFX vault and few hours later returned: Pool vault returned to its state as of Sun Feb 17 03:07:36 2013. Discarded approximately 20 minutes of transactions. After that I could import the pool in the memstick environment. I unmounted all ZFS file systems and exported the zpool and rebooted. However when the system boots from the UFS root it fails to mount root from ZFS: Trying to mount root from zfs:vault/root []... Mounting from zfs:vault/root failed with error 2. To get the system booting from ZFS root I tried several things including: - recreating the /boot/zfs/zpool.cache, - cloning the vault/root file system to vault/new_root, - setting the mountpoint of the root file system to / and legacy, - removed the cache and log devices from the zpool. I finally gave up and copied the contents of the vault/root file system to a UFS file system at ada0s1d and changed the system to mount root from there. /tmp, /usr and /var are mounted fine from the ZFS. I really would like to back using the ZFS root file system. I documented the commands I used in the memstick environment and dmesgs of the failing ZFS boots and made them available here: http://upload.egarden.fi/ultra40_zfs_fail Maybe someone can figure out what I'm doing wrong? Before the suspend to RAM incident the system booted up just fine. I used the following trick to get the dmesgs: when the system booted up and failed to mount the ZFS root I entered ufs:da0 to the mountroot prompt to get in to the memstick environment. -- Jonni Nakari jo...@egarden.fi +358 50 4411 784 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS pool data recovery
On 02/18/2013 08:06 AM, Jonni Nakari wrote: It seems, that while testing suspend to RAM on my machine by running acpiconf -s 3 I managed to break a RaidZ zpool. The machine went to sleep fine, but after waking up commands (e.g. reboot) reported I/O error. When booting after a hard reset the machine fails to mount the root filesystem: Trying to mount root from zfs:/vault/root []... Mounting from zfs:/vault/root failed with error 5. I booted the system from FreeBSD-9.1-RELEASE-amd64-memstick.img and tried to import the zpool in the shell: # zpool import -f vault cannot import 'vault': I/O error Destroy and re-create the pool from a backup source. Command zpool import -nfF vault from the memstick system gives no output. (I thought it should always give some output?) What should I try next to repair the zpool or recover the data? I started zpool import -nfFX vault but it seems to take quite long. Some more information about my system: zpool vault consists of 5 block devices: whole disks: ada1, ada2, ada3 cache: ada0s1e log: ada0s1d The system boots from a UFS filesystem ada0s1a. The zpool and rest of the system was created with FreeBSD 9.1-RELEASE. Does dmesg or syslog show anything with regards to the supposed I/O errors? Do the disks pass a read-only scan or 'long' SMART test? While unlikely, it is possible that one of the devices picked that precise moment to fail. It's also possible a disk did not appreciate being put to sleep; I've had several SSDs that simply stopped responding under such conditions, prompting warranty replacement. -- Fuzzy love, -CyberLeo Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ZFS pool data recovery
It seems, that while testing suspend to RAM on my machine by running acpiconf -s 3 I managed to break a RaidZ zpool. The machine went to sleep fine, but after waking up commands (e.g. reboot) reported I/O error. When booting after a hard reset the machine fails to mount the root filesystem: Trying to mount root from zfs:/vault/root []... Mounting from zfs:/vault/root failed with error 5. I booted the system from FreeBSD-9.1-RELEASE-amd64-memstick.img and tried to import the zpool in the shell: # zpool import -f vault cannot import 'vault': I/O error Destroy and re-create the pool from a backup source. Command zpool import -nfF vault from the memstick system gives no output. (I thought it should always give some output?) What should I try next to repair the zpool or recover the data? I started zpool import -nfFX vault but it seems to take quite long. Some more information about my system: zpool vault consists of 5 block devices: whole disks: ada1, ada2, ada3 cache: ada0s1e log: ada0s1d The system boots from a UFS filesystem ada0s1a. The zpool and rest of the system was created with FreeBSD 9.1-RELEASE. -- Jonni Nakari jo...@egarden.fi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
NTFS data recovery
Hi All, I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. No joy Windows insists that the partition is RAW and I need to format it. I can however mount it under FreeBSD without any problems, the directory structure appears to be intact but there are no files in the places I would expect to find them under the Users directory, I am guessing that these have somehow been deleted or perhaps the victim of a partial OEM recovery process. Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
On Mon, 9 Jul 2012 16:01:56 +, Graeme Dargie wrote: Hi All, I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. Bad idea. You cannot fully make sure that the disk's content isn't altered. There's no mount -o ro in Windows. Even worse, it might lead to more corruption during attempts to repair it. No joy Windows insists that the partition is RAW and I need to format it. Don't format it, it will massively decrease your chances for data recovery. Work with what you have, touch it as few as possible, use the proper tools. You won't find them on Windows. I can however mount it under FreeBSD without any problems, the directory structure appears to be intact but there are no files in the places I would expect to find them under the Users directory, I am guessing that these have somehow been deleted or perhaps the victim of a partial OEM recovery process. That's quite possible. Check df vs. du output and see if it magically fits, e. g. that the data is somewhere. Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. Because it's about NTFS recovery, things are a bit complicated, but not impossible. I'd suggest to first make a copy of the disk using dd, then work with that copy. Do _NOT_ fiddle with the original disks! If dd doesn't work, try ddrescue and dd_rescue. There are programs in the sysutils/ntfsprogs port will be surely useful to dealing with the NTFS content. Then of course you'll find The Sleuth Kit very helpful. It's programs fls, dls and ils might be what you're searching for. Sadly the documentation has been moved into a web page. :-( Additionally, you may try magicrescue, recoverjpeg and foremost, maybe fatback (but I doubt it). Those are acting outside of the FS. For missing files, maybe you can find a differing MFT to check? I know there was something related in the documentation of the older versions of TSK, but as I said, that situation has disimproved. :-( Note that data recovery is a dirty job, it takes time and is therefore quite expensive if delegated to a company. In your case it means you'll have to invest MUCH TIME into getting the data back. I hope the files are worth it. The absence of a backup seems to imply the opposite. :-) Anyway, good luck! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
On Mon, 9 Jul 2012 18:54:37 +0200 Polytropon articulated: On Mon, 9 Jul 2012 16:01:56 +, Graeme Dargie wrote: Hi All, I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. Bad idea. You cannot fully make sure that the disk's content isn't altered. There's no mount -o ro in Windows. Even worse, it might lead to more corruption during attempts to repair it. I have seen this work, but not on Windows 7. (based on Windows 2003 SP2) 1) switch off automount using the mountvol.exe command 2) present disk to Windows 2003 SP2 3) do not mount the disk 4) launch diskpart 5) do a list disk and list volume 6) note down the correct volume number 7) in diskpart do a select volume X (where X is the correct volume number) 8) then in diskpart doa att vol set readonly 9) then in diskpart do a detail vol and ensure the readonly bit is set 10) then you can mount the volume, the volume will be readonly Interestingly enough, only a few months ago, I used SpinRite 6 to recover an 80 Gb disk that was supposedly fried. If the HD can be seen by the system hardware, SpinRite has a fighting chance of recovering it. It took a week but it got all of the data back. I did take the HD out of the original PC and put it into a backup unit since I could not tie that PC up for an extended time. SpinRite does not need a super high speed machine to work off of. Good luck, you'll need it. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ This is supposed to be a happy occasion. Let's not BICKER and ARGUE over who killed who! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
Graeme Dargie arab at tangerine-army.co.uk writes: ... Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. testdisk http://www.freebsd.org/cgi/url.cgi?ports/sysutils/testdisk/pkg-descr I would suggest you compile it before use (otherwise grab a package). jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
jb jb.1234abcd at gmail.com writes: ... ntfs utilities http://www.freebsd.org/cgi/url.cgi?ports/sysutils/ntfsprogs/pkg-descr I would suggest you compile it before use (otherwise grab a package). jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. No joy Windows insists that the partition is RAW and I need to format it. I can however mount it under FreeBSD without any problems, the directory structure appears to be intact but there are no files in the places I would expect to find them under the Users directory, I am guessing that these have somehow been deleted or perhaps the victim of a partial OEM recovery process. Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. get other disk or just use free space on large filesystem and do dd if=/dev/baddisk of=file bs=64k conv=noerror,sync then - after having backup, try to salvage things ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Data recovery
Hi all, I'm throwing this out to this list because our SNAP drive has a *nix kernel- One of the folders mysteriously lost a large portion of its data today, I immediately powered down the unit as to prevent further writing to the disks (raid 5)- Is there any tool or utlity you can recommend to try to get this data back? If memory server *nix does not erase the data , it merely marks as empty space that can be written to , I think I remember that from school Any and all help is GREATLY appreciated thanks jp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data recovery
Jean-Paul Natola wrote: Hi all, I'm throwing this out to this list because our SNAP drive has a *nix kernel- One of the folders mysteriously lost a large portion of its data today, I immediately powered down the unit as to prevent further writing to the disks (raid 5)- Is there any tool or utlity you can recommend to try to get this data back? If memory server *nix does not erase the data , it merely marks as empty space that can be written to , I think I remember that from school Any and all help is GREATLY appreciated thanks jp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] fsdb might be what your looking for, though I can't be certain as this has never happened to me. ~Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data recovery
On Tue, Jul 01, 2008 at 05:27:41PM -0400, Jean-Paul Natola wrote: Hi all, I'm throwing this out to this list because our SNAP drive has a *nix kernel- One of the folders mysteriously lost a large portion of its data today, Oops. Am I correct in assuming that you have a NetApp appliance that is managed with SnapDrive? Are there any indications of hardware failure? I immediately powered down the unit as to prevent further writing to the disks (raid 5)- That is probably wise. Is there any tool or utlity you can recommend to try to get this data back? It would probably be best to use the tools that come with the SnapDrive software. According to the manufacturer's website it can e.g. do automated backups and restores. First check if the storage appliance is working as it should, and have it repaired if necessary. If it is a NetApp appliance, you'll have to talk to the NetApp people, because they use a heavily modified FreeBSD. If the hardware is OK, restore the data from backup. You do have backups, right? If memory server *nix does not erase the data , it merely marks as empty space that can be written to , I think I remember that from school Yes. But that doesn't necessarily make piecing the data back together easy! Restoring from backup is easier. If that isn't an option, use dd(1) to make an exact copy of the partition, save that to another machine and start piecing your data back together. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp7OOnBdVY3d.pgp Description: PGP signature
Re: Data Recovery
On Thu, Nov 30, 2006 at 03:29:39AM -0800, Rachel Florentine wrote: Is there a data recovery utility anywhere available? Not one that loads into Windoze, but straight into FBSD. maybe ports/sysutils/sleuthkit is what you need? -- Best regards, Kirill Spitsin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Data Recovery
Hi; Is there a data recovery utility anywhere available? Not one that loads into Windoze, but straight into FBSD. I tried the following command to back up my working HD to my new 1/2 teraflop HD: cp -R /* /ad2 and I managed to crash the system (recovered easily) and fry some important files on ad2. TIA, Rachel Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
cp is not efficient for your need, use RSYNC. this way, the second time you backup, you only copy newer files and don´t crash your box... ;) regards, Rachel Florentine wrote: Hi; Is there a data recovery utility anywhere available? Not one that loads into Windoze, but straight into FBSD. I tried the following command to back up my working HD to my new 1/2 teraflop HD: cp -R /* /ad2 and I managed to crash the system (recovered easily) and fry some important files on ad2. TIA, Rachel Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Marcelo Maraboli Rosselott Jefe Area de Redes y Comunicaciones (Network UNIX Systems Engineer) Ingeniero Civil Electronico, CISSP (Electronic Engineer, CISSP) Direccion Central de Servicios Computacionales (DCSC) Universidad Tecnica Federico Santa Mariaphone: +56 32 2654071 Chile. http://www.usm.cl http://elqui.dcsc.utfsm.cl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
I don't think that rsync can cope with hardlinks. Best way to do a backup like this is: tar -clf - / | ( cd /ad2 ; tar -xf - ) The -l flag will stay on the specified filesystem. If you forget this option tar (and any other command, even cp and rsync with their respective option) will copy /ad2 into itself, e.g. /ad2/ad2, which might lead to a kind of recursion. BTW: No, there isn't any tool that might recover from a desaster like the one you specified. Either the files you describe as being fried have either been overwritten with some other content, or changed in any other way. You need a backup to recover from this. ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
Christian Walther wrote: I don't think that rsync can cope with hardlinks. yes it can. From the man page: -H, --hard-linkspreserve hard links Slower, but it copes. Best way to do a backup like this is: tar -clf - / | ( cd /ad2 ; tar -xf - ) Only if you want to copy every shred of data regardless of whether it changed or not, as was previously noted. --Alex PS Backup gets used to mean at least two different things: 1) A single, separate copy of the data for which rsync is great. Read the manpage as it has lots of configuration potential. 2) Effectively a partial transaction history for the data where you can recover a file as it was, say, a week ago, for which dump and restore are your friends. There's also a tool in the ports which does something similar with rsync and separate trees named, I think, by date, which is great if you have lots of disk space. Or you can use snapshots, and again there is a tool in the ports whose name eludes me. cd /usr/ports make search name=rsync make search name=snapshot if you care. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
On Thu, Nov 30, 2006 at 03:29:39AM -0800, Rachel Florentine wrote: Hi; Is there a data recovery utility anywhere available? Not one that loads into Windoze, but straight into FBSD. I tried the following command to back up my working HD to my new 1/2 teraflop HD: cp -R /* /ad2 and I managed to crash the system (recovered easily) and fry some important files on ad2. That won't really get what you want anyway. It doesn't handle hard links the way you want and I don't really think it will get other file systems mounted in root (/), though I haven't tried that. Also, I think you would need a trailing '/' on ad2 in your command to come even close. How about using dump(8) and restore(8). They handle everything correctly. You can either leave everything in the dump file[s] on your big disk just in case you need it [them] in the event of a failure on you main working disk or build file systems on the big disk and restore everything in to them so the file systems are mountable from the big disk. The first choice probably makes most sense as a backup/recovery method. This is not a ghost type sector-by-sector backup (which is mostly useless) but a file-by-file backup (including all directory structures and links). So, you need to run dump for each filesystem you want to back up. First, create one large slice on ad2 using fdisk. Then create at least one partition in that slice using bsdlabel. Then create filesystems in the partitions using newfs. Then you can write to that disk with regular commands such as cp, tar or dump. Then, presuming one slice (1) and one partition (a), mount that big partition as something - lets say '/stash' eg mkdir /stash mount /dev/ad2s1a /stash Now use dump dump 0af /stash/rootdump / dump 0af /stash/usrdump /usr etc If you create separate file systems to make mountable images of each file system, then mount them as something sensible - say /bakroot and /bakusr Then to use dump/restore, do: cd /bakroot dump 0af - / | restore -r - cd /bakusr dump 0af - /usr | restore -r - This will get you working copies of those two file systems including links - which will still point to the real locations, not the copies, of course. Anyway, regardless of what you do, you must fully create at least one file system on the big disk and them mount it to write to it. You cannot write directly to the unprepared device as ad2. Of course, you could create that partition as above doing fdisk, bsdlabel and newfs and then create a mount point called /ad2 and mount it as such. But, I would shy away from that, just because it can create confusion. I would recommend using mount point names that represent what is to be written there as I have done above. jerry TIA, Rachel __ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
On Thu, Nov 30, 2006 at 03:47:53PM +0100, Christian Walther wrote: I don't think that rsync can cope with hardlinks. Best way to do a backup like this is: tar -clf - / | ( cd /ad2 ; tar -xf - ) The -l flag will stay on the specified filesystem. If you forget this option tar (and any other command, even cp and rsync with their respective option) will copy /ad2 into itself, e.g. /ad2/ad2, which might lead to a kind of recursion. No. Tar isn't good enough. Use dump/restore. It is made for that. jerry BTW: No, there isn't any tool that might recover from a desaster like the one you specified. Either the files you describe as being fried have either been overwritten with some other content, or changed in any other way. You need a backup to recover from this. ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Overburned DVD data recovery
[EMAIL PROTECTED] wrote: I have a cron job that backs up a FreeBSD server's files to DVD+RW media each evening using growisofs from the dvd+rw-tools port. There are some files that I need to recover, but the problem is, the last 2 weeks of backups were a few hundred megabytes too large, and overburned. AFAIK you can't overburn DVDs. Is there any way to recover data from these overburned DVDs? I tried mounting them from FreeBSD, Windows and Mac systems without success. I also tried running cat /dev/acd0 | gzip data.iso.gz in an attempt to grab the raw bits of the disk, but that only resulted in an input/output error. You could try readcd and isoinfo (/usr/ports/sysutils/cdrtools-devel) but those few hundred megabytes at the end will still be lost. Fabian -- http://www.fabiankeil.de/ pgpiY6QfD2GpX.pgp Description: PGP signature
Re: Overburned DVD data recovery
On 10/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have a cron job that backs up a FreeBSD server's files to DVD+RW media each evening using growisofs from the dvd+rw-tools port. There are some files that I need to recover, but the problem is, the last 2 weeks of backups were a few hundred megabytes too large, and overburned. Is there any way to recover data from these overburned DVDs? I tried mounting them from FreeBSD, Windows and Mac systems without success. I also tried running cat /dev/acd0 | gzip data.iso.gz in an attempt to grab the raw bits of the disk, but that only resulted in an input/output error. Restoring a 2-week-old backup is an option, but any ideas on how I might read data off of these overburned disks would be greatly appreciated. Thanks, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I'd start with trying to dd the DVD to an ordinary file (dd if=/dev/dvd-device of=/usr/recov.iso bs=2048) and then trying to mount that file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Overburned DVD data recovery
Hi, I have a cron job that backs up a FreeBSD server's files to DVD+RW media each evening using growisofs from the dvd+rw-tools port. There are some files that I need to recover, but the problem is, the last 2 weeks of backups were a few hundred megabytes too large, and overburned. Is there any way to recover data from these overburned DVDs? I tried mounting them from FreeBSD, Windows and Mac systems without success. I also tried running cat /dev/acd0 | gzip data.iso.gz in an attempt to grab the raw bits of the disk, but that only resulted in an input/output error. Restoring a 2-week-old backup is an option, but any ideas on how I might read data off of these overburned disks would be greatly appreciated. Thanks, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
data recovery
Hi i just removed /home/mylib/UNIX with rm -rf /home/mylib/UNIX this dir is my important directory. now i`m trying to recover all data in this dir. there is no such file UNIX in /home/mylib bcos i removed it but in my locate database , it shown me the following # locate UNIX /usr/home/mylib/UNIX /usr/home/mylib/UNIX/#bandwidthmonitoring /usr/home/mylib/UNIX/#ipfstat /usr/home/mylib/UNIX/#loaderror /usr/home/mylib/UNIX/ANNOUNCEMENT /usr/home/mylib/UNIX/FreeBSD5x.html /usr/home/mylib/UNIX/HARDWARE /usr/home/mylib/UNIX/IP_DUMMYNET.htm /usr/home/mylib/UNIX/IP_DUMMYNET_files /usr/home/mylib/UNIX/IP_DUMMYNET_files/dummynet.gif /usr/home/mylib/UNIX/IP_DUMMYNET_files/power_ale.gif /usr/home/mylib/UNIX/John.Wiley.Sons.Unix.For.Dummies.eBook-LiB.chm /usr/home/mylib/UNIX/PACKAGES /usr/home/mylib/UNIX/PORTS /usr/home/mylib/UNIX/README /usr/home/mylib/UNIX/Teach.Yourself.Unix.in.24.Hours.pdf /usr/home/mylib/UNIX/aaa /usr/home/mylib/UNIX/drweb-432a-unix-en-pdf.zip /usr/home/mylib/UNIX/etc /usr/home/mylib/UNIX/etc/login.conf /usr/home/mylib/UNIX/fbsd5.3.html /usr/home/mylib/UNIX/ftplist /usr/home/mylib/UNIX/moduleslaptop.html /usr/home/mylib/UNIX/my new OS /usr/home/mylib/UNIX/my new OS/#fdisk /usr/home/mylib/UNIX/myfreebsd.html /usr/home/mylib/UNIX/natd /usr/home/mylib/UNIX/natd.html /usr/home/mylib/UNIX/natd.html~ /usr/home/mylib/UNIX/natdconfig /usr/home/mylib/UNIX/network-natd.html /usr/home/mylib/UNIX/network-routing.html /usr/home/mylib/UNIX/obsd-faq.pdf /usr/home/mylib/UNIX/obsd-faq.txt /usr/home/mylib/UNIX/obsd-faq32.pdf /usr/home/mylib/UNIX/obsd-faq32.txt /usr/home/mylib/UNIX/obsd-faq33.pdf /usr/home/mylib/UNIX/obsd-faq33.txt /usr/home/mylib/UNIX/pf-faq.pdf /usr/home/mylib/UNIX/pf-faq.txt /usr/home/mylib/UNIX/pf-faq33.pdf /usr/home/mylib/UNIX/pf-faq33.txt /usr/home/mylib/UNIX/scanner.html /usr/home/mylib/UNIX/unixsa.pdf /usr/local/lib/perl5/5.8.7/IO/Socket/UNIX.pm /usr/local/lib/perl5/5.8.7/perl/man/man3/IO::Socket::UNIX.3.gz /usr/local/share/doc/samba/htmldocs/UNIX_INSTALL.html /usr/local/share/doc/samba/textdocs/UNIX-SMB.txt /usr/local/share/doc/samba/textdocs/UNIX_SECURITY.txt /usr/local/share/swat/help/UNIX_INSTALL.html /usr/ports/editors/manedit/files/patch-Makefile.install.UNIX /usr/ports/games/powerpak/files/patch-Makefile.UNIX /usr/ports/security/nmap/work/nmap-3.81/libpcre/NON-UNIX-USE /usr/ports/x11/xcalib/files/patch-icclib-Makefile.UNIX /usr/src/libexec/bootpd/Makefile.UNIX # can i make data recovery from locate database?. i have no any backup file :-( Regards Clock __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: data recovery
anti cl0ck wrote: can i make data recovery from locate database?. No, this databases contains only filenames. Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: data recovery
On Sunday 25 September 2005 10:31 am, anti cl0ck wrote: Hi i just removed /home/mylib/UNIX with rm -rf /home/mylib/UNIX this dir is my important directory. now i`m trying to recover all data in this dir. there is no such file UNIX in /home/mylib bcos i removed it If you have no backup try google for data recovery. There are several companies that can recover lost data from a HD. Bear in mind it can be very expensive. Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ --- pgpIA9BzWa2f1.pgp Description: PGP signature
Re: data recovery
On Sun, 25 Sep 2005 11:11:57 -0800 Beecher Rintoul [EMAIL PROTECTED] wrote: On Sunday 25 September 2005 10:31 am, anti cl0ck wrote: Hi i just removed /home/mylib/UNIX with rm -rf /home/mylib/UNIX this dir is my important directory. now i`m trying to recover all data in this dir. there is no such file UNIX in /home/mylib bcos i removed it If you have no backup try google for data recovery. There are several companies that can recover lost data from a HD. Bear in mind it can be very expensive. if you didn't do any write operations on the HD since you deleted the files it could be possible to recover them with a data recovery tool. unfortunately i don't know any for freebsd/ufs but maybe you find one if you search a bit jonas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Data Recovery
Are there any ways to recover files from rm -rf dirname after a few days, assuming there have been few if any writes to the filesystem since? I've been playing with tools like foremost and jpegrescue a bit... and running tests on other filesystems, but it doesn't appear that I'm getting full images back from the disk. Looking at an octal dump of a disk image (dd if=/dev/blah of=/some/file), I can find the file header... and about 20k of the file, generally... and then there's garbage. Presumably the file's been broken into blocks and there's inode table data to consider... The tests Im running are trying to find jpeg files that HAVEN'T been deleted from the filesystem. My real scenario of course differs. Pointers/rtfm welcome. -Yanek. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
I hope that you have remounted this filesystem read-only .. or else you might not be able to recover anything. That might be one of the problems you are running into. Sleuthkit allows you to search inodes and fragment ranges of a device for particular file and directory names.. then images that inode or fragment range into a single image file elsewhere on the system. Foremost will then open that image file and extract files based on their header and footer information, but.. if you do not include footer information you might get truncated file recovery. Also.. as stated before.. if there have been multiple writes to the file system.. you probably wont get the file back at all. Hope this helps.. T - Original Message - From: Yanek Korff [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Thursday, March 17, 2005 10:24 AM Subject: Data Recovery Are there any ways to recover files from rm -rf dirname after a few days, assuming there have been few if any writes to the filesystem since? I've been playing with tools like foremost and jpegrescue a bit... and running tests on other filesystems, but it doesn't appear that I'm getting full images back from the disk. Looking at an octal dump of a disk image (dd if=/dev/blah of=/some/file), I can find the file header... and about 20k of the file, generally... and then there's garbage. Presumably the file's been broken into blocks and there's inode table data to consider... The tests Im running are trying to find jpeg files that HAVEN'T been deleted from the filesystem. My real scenario of course differs. Pointers/rtfm welcome. -Yanek. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Recovery
Yanek Korff writes: Are there any ways to recover files from rm -rf dirname after a few days, assuming there have been few if any writes to the filesystem since? You can restore the files from backup for as long as you keep the backups. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum Concat Data Recovery
Hi, I have made concat drive using 3 hard disks using vimum vm. Some weeks ago one of those 3 disks crashed completely (bios can't even detect it anymore). My question now is: is there any chance to recover the data that resides on the 2 (working) remaining disks? I cant provide more info than the config file since the disks are not in my server anymore atm. Thanks --- vinum.conf: drive a device /dev/ad6s1e drive b device /dev/ad4s1e drive c device /dev/ad5s1e volume storage plex org concat sd length 78528m drive a sd length 58643m drive b sd length 58643m drive c PS: I've searched the archives but I didnt find a satisfactory answer. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Concat Data Recovery
On Wednesday, 8 September 2004 at 13:13:22 +0200, Thomas Spreng wrote: Hi, I have made concat drive using 3 hard disks using vimum vm. Some weeks ago one of those 3 disks crashed completely (bios can't even detect it anymore). My question now is: is there any chance to recover the data that resides on the 2 (working) remaining disks? Not from the volume. This is a non-resilient configuration. You'll have use the backup. drive a device /dev/ad6s1e drive b device /dev/ad4s1e drive c device /dev/ad5s1e volume storage plex org concat sd length 78528m drive a sd length 58643m drive b sd length 58643m drive c Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgpaB54XUjR9n.pgp Description: PGP signature
Data recovery.
Hi, I've just had a disk (pretty much) fail on me. I'd been suspect of it for some time now, but finally confirmed it with a reinstall to 5.2.1 when GEOM started removing it for me ;) Some more tests with smartmontools (http://smartmontools.sourceforge.net/) indicate read failures at the same position on the disk. This problem is made worse by the fact that this is a 100GB disk, part of a Vinum RAID-0 array (together with two more 120GB disks). I have managed to get my hands on a 123GB disk for backing up the data to to. I know I am going to have to use dd for this, but this is something I've never done before (short of a quick flirt with floppy images, etc.) Since GEOM has previously removed the volume when it hit the bad area I need to know if I can disable this to recover as much data as possible (some is better than none). If this requires installing 4 then that's how I'll have to do it. Basically I would like to ask -questions if anybody has any advice (other than ``you should have made backups'' -- I was in the process of buying a 3Ware RAID card for this purpose ;) as to how I should go about this. Anything at all... I'm pretty desperate at this point! Thanks very much, -lewiz. -- I was so much older then, I'm younger than that now. --Bob Dylan, 1964. -| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |- pgp0.pgp Description: PGP signature
Re: Data Recovery companies (dead HD)
where are you located, Francisco? - Original Message - From: Francisco Reyes [EMAIL PROTECTED] To: FreeBSD Questions List [EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 10:44 AM Subject: Data Recovery companies (dead HD) Anyone has used any data recovery company they could recommend? It's a UFS HD with softupdates. Its the data disk of a FreeBSD 4.7 machine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Data Recovery companies (dead HD)
Anyone has used any data recovery company they could recommend? It's a UFS HD with softupdates. Its the data disk of a FreeBSD 4.7 machine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Advise on data recovery from failed drive
I've had a drive crash where the spindle motor bearings overheated and got stuck. Using mild violence I now have the drive spinning again and need to do some data recovery. It has to be something that is able to handle read errors without stopping, I am thinking dd, any other suggestions? Thanks, Per olof ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Advise on data recovery from failed drive
On Sat, Jul 12, 2003 at 01:19:32AM +0200 or thereabouts, Per olof Ljungmark wrote: I've had a drive crash where the spindle motor bearings overheated and got stuck. Using mild violence I now have the drive spinning again and need to do some data recovery. It has to be something that is able to handle read errors without stopping, I am thinking dd, any other suggestions? dd if=/dev/FAILED of=/dev/SPARE conv=noerror bs=32k The conv=noerror does it. -- Josh Thanks, Per olof ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Advise on data recovery from failed drive
On Friday July 12, 2003 (PST) Per olof Ljungmark wrote: I've had a drive crash where the spindle motor bearings overheated and got stuck. Using mild violence I now have the drive spinning again and need to do some data recovery. It has to be something that is able to handle read errors without stopping, I am thinking dd, any other suggestions? I have an ancient program that I once wrote to make copies of disk drives with bad sectors. It normally reads/writes in large units, but goes back and rereads a section of the input disk one 512 byte sector at a time if it gets a read error. It will retry a single sector read several times before giving up. Unreadable sectors are assumed to be zero. This program was intended to be used with raw disk devices (drivers) doing unbuffered physical I/O with simple error recovery procedures (perhaps a limited number of read retries). I have not ported it to FreeBSD or even looked at it in many years, but it ought to work ok as is. The traditional dd program has a few problems if you use it with the conv=noerror option to copy sick disks. One problem is that you must specify bs=512 (i.e. copy only one sector at a time) to avoid losing good disk sectors adjacent to a bad disk sector. This makes for a slow copy. Another problem is that is that if you tell dd to ignore input errors, it skips the bad blocks on input but not on output so that after a read error blocks are copied to a wrong disk address. I just did a man on the FreeBSD 4.8-RELEASE dd command and discovered a new option that avoids this problem. Specify conv=noerror,sync if you use the dd command. Dan Strick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
