Ezra Pound
Well-Known Member
If you are asking me personally, the answer is definitely yes, bring it on, let us see who has to change their posting style the most to conform with thisWould you take any notice of it?
If you are asking me personally, the answer is definitely yes, bring it on, let us see who has to change their posting style the most to conform with thisWould you take any notice of it?
It is a direct quote, they are your words, It was not my intention to alienate any of the users detailed in my post, it was simply an attempt to point out that all these uses are of a similar opinion when it comes to that term, it was a hope that even someone who obviously sees himself as superior to all other users of this forum, who can only referrer to other users as 'you people' and 'oiks' will see reason in this matter and stop using misleading terminology that new users won't understandEzra: do not quote me as being for or against anything. You're being deliberately awkward in this thread and I do not want to be used as a tool for your whinging.
It is a direct quote, they are your words, It was not my intention to alienate any of the users detailed in my post, it was simply an attempt to point out that all these uses are of a similar opinion when it comes to that term, it was a hope that even someone who obviously sees himself as superior to all other users of this forum, who can only referrer to other users as 'you people' and 'oiks' will see reason in this matter and stop using misleading terminology that new users won't understand
Following the apparent failure of the previous UPD I had purchased a brand new SanDisk which I had difficulty initialising, so I fell back on an old one with which I had a similar difficulty but persisted and had running fine for less than four weeks! I will try again with the SanDisk now the process has been debugged, but before that is there anything I can do to find out what's going on?I don't beleeeeve it! Different UPD, and the modsettings folder has cleared out again.
Maintenance mode is initialising... Please wait...
............................................................
Menu version 1.12
Enter system PIN: ****
/---------------------------------------------\
| M A I N T E N A N C E M O D E M E N U |
\---------------------------------------------/
[ Humax HD-Fox T2 (HDFOX1) 1.03.02/3.02 ]
Note: Some areas of the hard disk are not mounted.
Not all functions will be available.
(normal if you have just run a disk check)
No suitable drive for EXT2 conversion detected.
epg - Clear persistent EPG data.
dlna - Reset DLNA server database.
x - Leave maintenance mode (Humax will restart).
diag - Run a diagnostic.
cli - System command line (advanced users).
Please select option: cli
-----------------------------------------------------------------------
Now starting a system command prompt. You can make this the default by
enabling 'Expert mode telnet server' on the web interface settings page.
-----------------------------------------------------------------------
Humax HD-Fox T2 (HDFOX1) 1.03.02/3.02
To return to the menu, type: exit
humax# mke2fs -m 0 -O sparse_super -q /dev/sda1
/dev/sda1 contains a ext2 file system
last mounted on Sat Jan 1 00:00:10 2000
Proceed anyway? (y,n) y
/dev/sda1: Read-only file system while setting up superblock
humax#
Menu version 1.12
Enter system PIN: ****
/---------------------------------------------\
| M A I N T E N A N C E M O D E M E N U |
\---------------------------------------------/
[ Humax HD-Fox T2 (HDFOX1) 1.03.02/3.02 ]
Note: Some areas of the hard disk are not mounted.
Not all functions will be available.
(normal if you have just run a disk check)
No suitable drive for EXT2 conversion detected.
epg - Clear persistent EPG data.
dlna - Reset DLNA server database.
x - Leave maintenance mode (Humax will restart).
diag - Run a diagnostic.
cli - System command line (advanced users).
Please select option: cli
-----------------------------------------------------------------------
Now starting a system command prompt. You can make this the default by
enabling 'Expert mode telnet server' on the web interface settings page.
-----------------------------------------------------------------------
Humax HD-Fox T2 (HDFOX1) 1.03.02/3.02
To return to the menu, type: exit
humax# e2fsck /dev/sda1
e2fsck 1.42.10 (18-May-2014)
/usr/lib/ext2/bin/e2fsck: Read-only file system while trying to open /dev/sda1
Disk write-protected; use the -n option to do a read-only
check of the device.
humax# e2fsck /dev/sda1 -n
<<< Too much output! >>>
You can write to a file in /tmp and then FTP etc. it off somewhere else.Obviously I can't divert it to a file...
Did you "umount /dev/sda1" before running e2fsck? It's not unmounted automatically in maintenance mode.No more guidance on this?
humax# umount /dev/sda1
umount: can't umount /dev/sda1: Invalid argument
humax# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /media type tmpfs (rw)
/dev/mtdblock1 on /var/lib/humaxtv type jffs2 (rw)
/dev/mtdblock2 on /var/lib/humaxtv_backup type jffs2 (rw)
humax# e2fsck /dev/sda1
e2fsck 1.42.10 (18-May-2014)
/usr/lib/ext2/bin/e2fsck: Read-only file system while trying to open /dev/sda1
Disk write-protected; use the -n option to do a read-only
check of the device.
humax# e2fsck /dev/sda1 -n
e2fsck 1.42.10 (18-May-2014)
/dev/sda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 98501 has zero dtime. Fix? no
Deleted inode 98502 has zero dtime. Fix? no
Deleted inode 98529 has zero dtime. Fix? no
Deleted inode 98536 has zero dtime. Fix? no
Deleted inode 98539 has zero dtime. Fix? no
Deleted inode 98541 has zero dtime. Fix? no
Deleted inode 98556 has zero dtime. Fix? no
Deleted inode 98567 has zero dtime. Fix? no
Error reading block 393339 (Attempt to read block from filesystem resulted in short read) while getting next inode from
scan. Ignore error? no
Error while scanning inodes (99648): Can't read next inode
/dev/sda1: ********** WARNING: Filesystem still has errors **********
e2fsck: aborted
/dev/sda1: ********** WARNING: Filesystem still has errors **********
humax#