Usernname & Password for Web Interface?

[prpr]

I think opkg is trying to use the wget on the hard disk, which has a dependency on libpcre.so.1, which is corrupt/missing, rather than using the wget in flash which doesn't have that dependency.
Try this:

PATH=/bin:/sbin
opkg update
opkg upgrade

 

[pADDYB]

Ok, that did lots! Seems like a lot of packages / services have been downloaded and installed, vbut now when I refresh the web portal I get 505 Internal Server Error?

 

[prpr]

Did you do the opkg install --force-reinstall libutil libpcre bit as well?

 

[pADDYB]

Just done the above, but same result with the web portal.

 

[prpr]

Does jimsh give you a Jim banner and prompt, or an error? "exit" to get back from the prompt.

 

[pADDYB]

Does jimsh give you a Jim banner and prompt, or an error? "exit" to get back from the prompt.

/bin/sh: jimsh: not found

 

[prpr]

You need your standard PATH back. Exit the command shell from earlier, re-enter and re-issue the command. Or try /mod/bin/jimsh .
I'm slightly confused by the error message not saying "/mod/bin/busybox/sh: jimsh: not found" though. Have you rebooted since earlier?
Or has the disk not mounted? Report the output of the mount command. Have you actually checked the disk is OK? What started all the problems off?
And what firmware version do you have installed, and have you done a fixdisk run from maintenance mode?

 

[Black Hole]

What started all the problems off?

Using password reset on the Telnet menu! It could be that corruption was the original cause of being prompted for a password in the first place.

 

[pADDYB]

/bin/sh: /mod/bin/jimsh: not found

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)
/dev/mtdblock2 on /sbin/wifi-up type jffs2 (rw)
/dev/sda1 on /media/drive1 type ext2 (rw)
/dev/sdb1 on /mnt/hd1 type ext3 (rw,data=ordered)
/dev/sdb2 on /mnt/hd2 type ext3 (rw,data=ordered)
/dev/sdb3 on /mnt/hd3 type ext3 (rw,data=ordered)
/dev/sdb2 on /opt/share/images/blue type ext3 (rw,data=ordered)
/dev/sdb2 on /mnt/hd2/My\040Video/[ModSettings] type ext3 (rw,data=ordered)
/dev/sdb2 on /media/drive1 type ext3 (rw,data=ordered)

Yes, I rebooted when the web portal stopped working.

 

[prpr]

Well I guess you need to force reinstall jim - opkg install --force-reinstall jim - and then see what the next thing is that's broken.
TBH, you'd probably have been better to blitz the whole /mod hierarchy and start again.
Still need to know about firmware version and fixdisk status.

 

[pADDYB]

Installing jim (0.82-2) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/jim_0.82-2_mipsel.opk.
wget: can't load library 'libpcre.so.1'
Collected errors:
* opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/base/jim_0.82-2_mipsel.opk, wget returned 16.
* opkg_install_pkg: Failed to download jim. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package jim.

Fw is: 1.03.12_mod_3.13

 

[Black Hole]

Use the menu to go into Maintenance Mode, then run fix-disk. When that finishes, run it again to confirm it reports no further errors found (the second run should be quick).

Your system seems to be so scrambled you might as well start again. The nuclear option: On the command line: rm -r /mod then reboot. Back to the browser, you should now see the CF installation page and can re-install WebIF.

 

[prpr]

rm /mod

rm -r /mod

 

[Black Hole]

Edited

 

[pADDYB]

Did fixxdisk.

First run, there were lots of "Inval.id Node" messages and a "FILE SYSTEM WAS MODIFIED". Exit Staus was 0

Second run results:

Checking disk sda (512 byte sectors)

Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted


Running short disk self test

No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3


Thu Nov 23 11:54:08 GMT 2023: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 8.06/ 2.40/ 4.33
Pass 1: I/O read: 163MB, write: 0MB, rate: 20.22MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (260k/81k), time: 0.00/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 418.41MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 8.53/ 2.67/ 4.35
Pass 3A: Memory used: 340k/0k (260k/81k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (259k/82k), time: 0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (53k/287k), time: 0.99/ 0.98/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time: 2.50/ 1.98/ 0.04
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.40MB/s

15 inodes used (0.00%, out of 655776)
2 non-contiguous files (13.3%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 3/2/0
131619 blocks used (5.02%, out of 2622611)
0 bad blocks
1 large file

4 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
6 files
Memory used: 340k/0k (53k/288k), time: 12.03/ 5.64/ 4.39
I/O read: 165MB, write: 1MB, rate: 13.71MB/s
Thu Nov 23 11:54:21 GMT 2023

Thu Nov 23 11:54:21 GMT 2023: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time: 0.85/ 0.25/ 0.47
Pass 1: I/O read: 17MB, write: 0MB, rate: 19.97MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time: 0.01/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 87.29MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time: 0.98/ 0.28/ 0.48
Pass 3A: Memory used: 140k/0k (72k/69k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (71k/70k), time: 0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (50k/91k), time: 0.11/ 0.11/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time: 0.32/ 0.26/ 0.01
Pass 5: I/O read: 1MB, write: 0MB, rate: 3.15MB/s

14 inodes used (0.02%, out of 65808)
1 non-contiguous file (7.1%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
16505 blocks used (6.27%, out of 263062)
0 bad blocks
1 large file

2 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
5 files
Memory used: 140k/0k (50k/91k), time: 1.42/ 0.65/ 0.49
I/O read: 17MB, write: 1MB, rate: 11.95MB/s
Thu Nov 23 11:54:22 GMT 2023

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=34ea09b4-3d9c-4f1b-8bbf-8e2408d7109f

Thu Nov 23 11:54:45 GMT 2023: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 592k/4672k (454k/139k), time: 1563.52/823.33/216.85
Pass 1: I/O read: 7570MB, write: 0MB, rate: 4.84MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 592k/9344k (434k/159k), time: 2.22/ 0.70/ 0.20
Pass 2: I/O read: 4MB, write: 0MB, rate: 1.80MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 592k/9344k (434k/159k), time: 1584.25/842.00/217.12
Pass 3A: Memory used: 592k/9344k (450k/143k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 592k/9344k (427k/166k), time: 0.07/ 0.05/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 14.11MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 592k/0k (375k/218k), time: 47.36/46.89/ 0.04
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 592k/0k (359k/234k), time: 125.33/92.91/ 1.80
Pass 5: I/O read: 29MB, write: 0MB, rate: 0.23MB/s


11053 inodes used (0.04%, out of 29860704)
312 non-contiguous files (2.8%)
12 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 532/242/7
73460403 blocks used (61.62%, out of 119209984)
0 bad blocks
40 large files

9284 regular files
538 directories
90 character device files
112 block device files
0 fifos
2 links
1020 symbolic links (1013 fast symbolic links)
0 sockets
------------
11046 files
Memory used: 592k/0k (359k/234k), time: 1757.09/981.84/218.96
I/O read: 7603MB, write: 1MB, rate: 4.33MB/s
Thu Nov 23 12:24:03 GMT 2023
Removing extra swap space.

Finished
fix-disk: session terminated with exit status 0

Now I can't access Telnet with Putty, but can through web intface. rm /mod returns "can't remove '/mod' read only filr system" but perhaps I need to exit Maintence Mode before running it?

 

[Black Hole]

Now I can't access Telnet with Putty

So what are you accessing the maintenance mode menu with – the browser implementation? I don't suppose it makes a difference, but there should be no reason you can't use Telnet.

Having run fix-disk the HDD isn't mounted, so yes you'll have to reboot out of maintenance mode first (sorry).

 

[pADDYB]

Thanks. Can you clarify with I should be using:
rm - r /mod
or
rm /mod

Both return Read only file system errors.

 

[Black Hole]

Can you clarify with I should be using:
rm - r /mod
or
rm /mod

Neither, it should be rm -r /mod.

-r means recursive, without which rm /mod will simply complain that the directory isn't empty.

Both return Read only file system errors.

Perhaps that's because /mod is actually a redirect. All I'm trying to do is blitz the non-FLASH CF. There are two options on the Telnet menu (non-maintenance): reset and rma. I've forgotten exactly what reset does, but you have nothing to lose by trying it. The other, rma, I believe does the same as reset but then sets a flag preventing re-installation of the CF, being to (a) clear the CF off the HDD and then (b) stand ready to flash standard firmware so there is no evidence left, after which if you do want to reinstall CF you have to use the Telnet menu to clear the RMA flag first.

Alternatively try rm -r /mnt/hd2/mod

 

[/df]

/mod is a symlink in the RO filesystem /.

/mod/* expands in the shell to a list of the files and directories in the directory linked from /mod, whose filesystem is RW.

Either rm -r /mod/* (leaves the empty mod directory, probably a good thing) or rm -r $(realpath /mod), but the realpath command is not in the bare firmware (needs busybox package, or use readlink -e with coreutils).

 

[prpr]

BH had it with his final comment above.