Code: e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? Some background: Humax HDR Fox T2 with 1TB disk is about 5 months old. Firmware is 1.02.29 Custom Firmware is 2.13 Suddenly got the pop-up saying HDD must be formatted for no apparent reason. Can't find any of the 400GB recorded programs and cannot use any pvr features on live TV. I telnet via ethernet cable connection from my linux client. I ran fix-disk and the humax rebooted into MAINTENANCE mode on its display. I reconnected with telnet. I ran fix-disk again, but it immediately aborted saying sda1 had an unrecognised partition type. Code: /proc/scsi/scsi says I have a ST31000424CS ATA drive at Rev: SC13. /proc/partitions lists sda, sda1, sda2, sda3 e2fsck /dev/sda1 failed again with the message at the top of this post. e2fsck /dev/sda3 kept failing when I replied "y" to create lost+found, but ran successfully when I replied "n". The error was "memory allocation failed while trying to read bitmaps". sda3 is currently in "clean" state according to tune2fs. When I mount it on /mnt/hd3 it only contains cookie.txt (and an empty lost+found directory, so I must have got lucky!) e2fsck /dev/sda2 takes a long time to run, and if I reply "y" to create the lost+found directory, it always fails with the "read bitmaps" message. I ran it again, replied "n", and was relieved to find it completed all 5 phases. The report said the partition still has errors. tune2fs said the filesystem was not clean, but it did contain 1800 files and 118 directories. I mounted the partition on /mnt/HD2 and manually created a lost+found directory. I chmod'd it to match the other directories on the file system. I was VERY relieved to find the "My Video" directory contained a lot of my recordings. After umount, e2fsck ran successfully. Phew! I feel that I have achieved 90% recovery. Presumably I can ftp these files off the disk (I realise they are encrypted) and put them back later. It will take a long time, even on a 100 mbs LAN. I suspect all will be back to normal if I could only fix sda1... Code: humax# fdisk -l /dev/sda fdisk: can't open '/dev/sda': Input/output error Worries me a lot because it should be reading the partition table, which is (presumably) telling the system that I have sda1, sda2, sda3 and allowing me to check the file systems on 2 and 3. and I still get these errors. Code: humax# tune2fs -l /dev/sda1 tune2fs 1.41.14 (22-Dec-2010) tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Couldn't find valid filesystem superblock. humax# e2fsck -v /dev/sda1 e2fsck 1.41.14 (22-Dec-2010) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1 Could this be a zero-length partition? So, not surprisingly, I still get this: Code: humax# fix-disk Partition 1 - Unrecognised partition type, aborting... Do you think fdisk is just confused by the zero-length sda1, or is the partition table really corrupt? What ought to be on a clean sda1? Can I recover or recreate it?