Is corrupt, and you might try running e2fsck with an alternate superblock: For example, if the Team A is 90-62 with 10 games remaining and Team B, the second-place team, is 85-67, Team A's magic number could be computed as follows: 163 - 90 - 67 6.
#MAGIC NUMBER PLUS#
That would be 162 games plus one, with zero wins and zero losses by the second-place team. If the device is valid and it really contains an ext2/ext3/ext4įilesystem (and not swap or ufs or something else), then the superblock Before the season starts, every team has a magic number of 163. The superblock could not be read or does not describe a valid ext2/ext3/ext4įilesystem. Running e2fsck I get the following: sudo e2fsck -n /dev/sdiĮxt2fs_open2: Bad magic number in super-blockĮ2fsck: Superblock invalid, trying backup blocks.Į2fsck: Bad magic number in super-block while trying to open /dev/sdi All the three have the same result ff d8 ff e0.
I have tested for the file formats of JPEG, JPG, and JFIF. There also exist JPEG files with a ff d8 ff e1 magic number and an Exif data block, which come without the JFIF string. I/O size (minimum/optimal): 4096 bytes / 4096 bytes What you tell over JPEG files is not true. Sector size (logical/physical): 512 bytes / 4096 bytes I took our the HD and connected it to my Linux box to try and rescue the data but so far without success. I have a WD Mybook Live disk which stopped working one day.