search for: possiblesb

...oned, that there is a possibility that the partition table itself may have been clobbered in a way to change the real starting address of the partition, I decided to search for possible candidates for a superblock using fsck in a shell script as follows: sb=0; while [ $sb -lt 429496729600 ]; do possibleSB=`e2fsck -n -b $sb /dev/sdc7 2>&1 | grep 'The superblock could not be read|Bad magic number'` [ "x$possibleSB" = "x" ] && echo $sb - "$possibleSB" sb=`expr $sb + 512` done > possibleSB I found these blocks, the value of which might hint that...

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On