I wanted to use my HD-FOX to download some recordings. It had been left in standby but I hadn't used it for a while. Webif gave the 'no disk detected' page and the telnet landing page warned of 'areas of the disk being unmounted'. I ran the 'df' command and got the following:
Oddly, a temporary file system was mounted as drive1, with the actual hard drive mounted as drive2. I ran e2fsck on the hard drive: there were no errors. I had a hunch and did some digging. The current version of ntfs-3g also installs virtual-disk2. This is necessary with the HDR-FOX, if mounting a large NTFS drive with gpt, to make the USB menu available with the SUI. The HD-FOX does not need virtual-disk2 as the USB menu is always available. The problem seems to be that the virtual disk is preferentially mounted as 'drive1', forcing the hard drive to 'drive2'. This causes problems as the custom firmware is looking for the 'mod' folder on 'drive1'. A temporary fix is to uninstall virtual-disk2. If you are already having this problem, you can only uninstall the package from maintenance mode. The command is:A permanent fix is for the package provider (@xyz321, I think) to prevent virtual-disk2 from being installed when installing ntfs-3g on the HD-FOX.
HDFox# df -h Filesystem Size Used Available Use% Mounted on /dev/root 20.7M 20.7M 0 100% / tmpfs 61.0M 116.0K 60.9M 0% /tmp tmpfs 61.0M 0 61.0M 0% /media /dev/mtdblock1 2.0M 568.0K 1.4M 28% /var/lib/humaxtv /dev/mtdblock2 2.0M 520.0K 1.5M 25% /var/lib/humaxtv_backup /dev/mtdblock2 2.0M 520.0K 1.5M 25% /etc/opkg /dev/sda1 53.0K 53.0K 0 100% /media/drive1 /dev/sdb1 458.4G 27.4G 407.7G 6% /media/drive2
opkg remove virtual-disk2 --force-depends