search for: oseek

.../dsk/c0t1d0 -n -s 256 block=507 (7ec00) transaction=15980522 Now lets say i want to go back in time on this, using the program can help me do that. If i wanted to go back in time to tgx 15980450... bash-3.00# /tmp/findUberBlock /dev/dsk/c0t1d0 -t 15980450 dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=180 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=181 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=182 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=183 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=184 count=1...

...0 0 0 corrupted data errors: No known data errors Why sparse files? See this post: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1007077+0+archive/2010/freebsd-stable/20100725.freebsd-stable The two tmp files were created via: dd if=/dev/zero of=/tmp/sparsefile1.img bs=1 count=0 oseek=1862g dd if=/dev/zero of=/tmp/sparsefile2.img bs=1 count=0 oseek=1862g And the array created with: zpool create -f storage raidz2 gpt/disk01 gpt/disk02 gpt/disk03 \ gpt/disk04 gpt/disk05 /tmp/sparsefile1.img /tmp/sparsefile2.img The -f flag was required to avoid this message: invalid vde...

So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I