Re: recover superblock
Problem solved. I could restore the superblock using: dd if=disk skip=32 of=disk seek=16 bs=512 count=16 Thx to http://groups.google.de/groups?selm=Pine.BSF.4.21.0212150052530.41793-10_root.org%40ns.sol.netoe=UTF-8output=gplain Cheers, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Mon, 25 Aug 2003, Thomas Gutzler wrote: Problem solved. I could restore the superblock using: dd if=disk skip=32 of=disk seek=16 bs=512 count=16 Thx to http://groups.google.de/groups?selm=Pine.BSF.4.21.0212150052530.41793-10_root.org%40ns.sol.netoe=UTF-8output=gplain Not really solved. fsck_ffs is supposed to be able to find alternative superblocks automatically, and the primary superblock shouldn't get trashed. Apparently the first alternative is at offset 32 (this is a normal place for it IIRC), but fsck_ffs can't find it there for some reason. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
Bruce Evans wrote this message on Mon, Aug 25, 2003 at 16:12 +1000: Thx to http://groups.google.de/groups?selm=Pine.BSF.4.21.0212150052530.41793-10_root.org%40ns.sol.netoe=UTF-8output=gplain Not really solved. fsck_ffs is supposed to be able to find alternative superblocks automatically, and the primary superblock shouldn't get trashed. Apparently the first alternative is at offset 32 (this is a normal place for it IIRC), but fsck_ffs can't find it there for some reason. I've also had the problem of when you do use an alternate superblock via -b, it doesn't over drive the primary. If you have a disk with bad blocks on the primary, you have to manualy rewrite it with dd. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
I don't have the solution. But I known a program taht allow you to restore partitions : http://www.cgsecurity.org/index.html?testdisk.html It seems to be very powerfull. With it you could get your data from broken partitions. PS : I know the developper, so if you have problem ... [ On Sun, 24 Aug, 2003 at 21:26, Thomas Gutzler wrote: ] Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] [ End of original mail from Thomas Gutzler ] -- No guts No glory =] PASSELAC Armand [= ( @ @ ) Ingenieur Systemes-Reseaux Securite ORBYTES INGENIERIE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
John-Mark Gurney [EMAIL PROTECTED] writes: I've also had the problem of when you do use an alternate superblock via -b, it doesn't over drive the primary. If you have a disk with bad blocks on the primary, you have to manualy rewrite it with dd. ...provided the drive automatically reassigns bad blocks on write (ARWE). I've seen a drive shipping with ARRE set but ARWE unset - it would reassign on read rather than write. Whatever the manufacturer had in mind configuring the drive before shipping it... -- Matthias Andree ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
Am Sun, 24.Aug.2003 um 23:50:56 -0700 schraubte John-Mark Gurney: Bruce Evans wrote this message on Mon, Aug 25, 2003 at 16:12 +1000: Thx to http://groups.google.de/groups?selm=Pine.BSF.4.21.0212150052530.41793-10_root.org%40ns.sol.netoe=UTF-8output=gplain Not really solved. fsck_ffs is supposed to be able to find alternative superblocks automatically, and the primary superblock shouldn't get trashed. Apparently the first alternative is at offset 32 (this is a normal place for it IIRC), but fsck_ffs can't find it there for some reason. Hm, newfs said, that the first backup is at 144. But the nice dd line worked anyway. I copied the result in a file and # file alternate_sb alternate_sb: Unix Fast File system (little-endian), last mounted on , last written at Fri Sep 6 11:53:08 2002, clean flag 1, number of blocks 78148161, number of data blocks 75746877, number of cylinder groups 173 5, block size 8192, fragment size 1024, minimum percentage of free blocks 8, rotational delay 0ms, disk rotational speed 60rps, TIME optimization running fsck -b 144 didn't work. I've also had the problem of when you do use an alternate superblock via -b, it doesn't over drive the primary. If you have a disk with bad blocks on the primary, you have to manualy rewrite it with dd. I'm pretty sure that this harddrive works well, cause it's just 3 weeks old and SMART doesn't find any errors, reallocations .. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
recover superblock
Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. Cheers, Mezz # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003, Jeremy Messenger wrote: On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 15:53:26 -0400 (EDT), Andre Guibert de Bruet [EMAIL PROTECTED] wrote: On Sun, 24 Aug 2003, Jeremy Messenger wrote: On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... I am pretty aware of it and I don't care of those are lost because I always backup my personal stuff daily. I run everything in bleed edge such as - CURRENT, Gnome 2.4, VIM-cvs and etc, so I know my risk. Cheers, Mezz Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
