Quantcast

Media & File Server Bundle for the Foxsat HDR - Release 4,0 - PART 3

Status
Not open for further replies.

REPASSAC

Well-known Member
For some reason my laptops have stopped connecting to the HDR. I'm getting "unable to open http.... Cannot locate the internet server or proxy server"

I've rebooted both laptops and restarted the HDR (with the remote). I've checked the address in the on screen menu and it's correct. I've restaretd the router.

any thoughts?
see previous post - changed DHCP IP? then allocate on router.
 

merlin777

Standard Member
sorry - replied out of sequence...

CPN - i haven't pinged, please could you tell me how?
repassac - I cant find the post. is it in this thread and please could you tell me the post number?
 

CPN

Novice Member
Ok, at least we know you have raw network connectivity. What browser are using? Clear it's cache of all the garbage and try connecting again to your HDR...
 

REPASSAC

Well-known Member
i'm using ie9.
i cleared the temp files and tried again but still won't connect
OK,
Several possabilities -
1. Do you see the custom firmware message when you boot the Foxsat (4.0.8)
if not you need to flash the new 4.0.8 firmware as the OTA has wipped 4.0.7
2. samba is not running - try and telnet to the foxsat and enter:
service auto mongoose
service start mongoose
 

REPASSAC

Well-known Member
thanks - i'll check these. does the OTA always rob you of your custom software?
Well not rob, everything is still present on disk - as soon as you flash the updated version (released before the OTA) you will back where you were.
Any OTA with a higher version number than installed will do it.
 

merlin777

Standard Member
wooo-hooo! All sorted.

It was the manufacturer's update wiping out the custom firmware. Shame you can't disable it.

Thanks for your help!
 

REPASSAC

Well-known Member
Goto the Setup section then "Software Update" and change it to manual...
I think the manual update option simply lets you enter a different transponder to look for. (Manual page GB53) - I must admit I never remember seeing it before.
 

grahamlthompson

Distinguished Member
wooo-hooo! All sorted.

It was the manufacturer's update wiping out the custom firmware. Shame you can't disable it.

Thanks for your help!
If you have the old custom firmware 4.0.7 and reflash it takes the built in firmware back to 1.0.20. The next night your 1.0.20 firmware is recognised as out of date so updates to 1.0.21. Custom firmware 4.0.8 contains 1.0.21 so installing it stops you going round in circles :D
 

CPN

Novice Member
I think the manual update option simply lets you enter a different transponder to look for. (Manual page GB53) - I must admit I never remember seeing it before.
You're absolutely right! I just assumed that because the options were "automatic" and "manual" that the latter disabled the former by default... (having never used them...)
 

merlin777

Standard Member
is there any guidance/instructions on using media tomb. i've installed it but the user interface is very unfriendly and the help file doesn't work.
 

Dbl-trouble

Novice Member
This reply is copied over from the part 2 thread. Sorry - it took me quite a while to get ready to respond...


Me (here):-
...I've just installed 4.0.7 on my box.

The install went as described in the readme, and the box reports "Custom FW v4.0.7" on the front panel display at bootup, but I'm not able to get the webpage up:-
"Firefox can't establish a connection to the server at 192.168.0.30."


The Humax has a net connection - I can stream iPlayer content from channel 901, and I can ping the box from my PC.

On raydon's advice :blush: I attempted to install telnet, which failed:-
Install started
cp: unable to open `/opt/tmp/telnet_1.0_mips.opk': No such file or directory
Collected errors:
* make_directory: Cannot create directory `/opt//var': Read-only file system.
* make_directory: Cannot create directory `/opt/var': Read-only file system.
* make_directory: Cannot create directory `/opt//var': Read-only file system.
* pkg_init_from_file: Failed to make temp file /telnet_1.0_mips.opk.control.Ni3gw9: Read-only file system.
* rm_r: Failed to open dir : No such file or directory.
rm: cannot remove `/opt/tmp/telnet_1.0_mips.opk': No such file or directory
Install done


Thinking about it, I wonder if this is because I've upgraded the disk to 2TB?

REPASSAC (here):-
Hmmm - how did you partition it and what sizes?
Answer: see "fdisk output.txt" and "GUI partition properties.txt", attached.
2.2 GB
107 MB
1.1 GB
2.0 TB


raydon (here):-
Custom firmware installs to the Music and Photos partition so (a) It needs to exist and (b) it needs to be writable. Going by the log of the unsuccessful telnet

install, it appears that it failed because the file system is read only. Maybe you need to remove the drive and check it with e2fsk.
Had quite a bit of hassle with Ubuntu (and other half insisted I backed up the recordings before I started playing, which was fun :laugh:, but my NAS is now 1.4TB fuller.

Attached is the output from e2fsck (hope that is what you wanted). There were a couple of errors found & fixed with the 2.0 TB filesystem. However, the 1.1 GB filesystem (the Music and Photos partition, I'm sure), does give me a nasty-looking error:-

[email protected]:~$ sudo e2fsck /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
e2fsck: Group descriptors look bad... trying backup blocks...
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4


/dev/sdc4: ********** WARNING: Filesystem still has errors **********
So, what's the next step from here? I don't have any music or photos, so can I just re-format the partition or something like that? If so, what process would I need to follow in Ubuntu to do that? After the filesystem fix, do I just re-install 4.08 again?

Many thanks for any help.

cheers, Martin
 

Attachments

Last edited:

raydon

Well-known Member
So, what's the next step from here? I don't have any music or photos, so can I just re-format the partition or something like that? If so, what process would I need to follow in Ubuntu to do that? After the filesystem fix, do I just re-install 4.08 again?
Google is your friend. Information HERE and HERE
 

Dbl-trouble

Novice Member
No change, but then e2fsck last time reported it was trying that automatically, anyway. More googling.

Edit: that's reported as a fail of the process at the second of those links, but it doesn't seem anyone has posted a fix.

"e2fsck: Group descriptors look bad... trying backup blocks...
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4"

[email protected]:~$ sudo mke2fs -n /dev/sdc4
mke2fs 1.42 (29-Nov-2011)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65808 inodes, 263064 blocks
13153 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=272629760
9 block groups
32768 blocks per group, 32768 fragments per group
7312 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

[email protected]:~$ e2fsck -b 32768 -fv /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
e2fsck: Permission denied while trying to open /dev/sdc4
You must have r/w access to the filesystem or be root
[email protected]:~$ sudo e2fsck -b 32768 -fv /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4


/dev/sdc4: ********** WARNING: Filesystem still has errors **********

[email protected]:~$ sudo e2fsck -b 98304 -fv /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4


/dev/sdc4: ********** WARNING: Filesystem still has errors **********

[email protected]:~$ sudo e2fsck -b 163840 -fv /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4


/dev/sdc4: ********** WARNING: Filesystem still has errors **********

[email protected]:~$ sudo e2fsck -b 229376 -fv /dev/sdc4
e2fsck 1.42 (29-Nov-2011)
/dev/sdc4: recovering journal
e2fsck: unable to set superblock flags on /dev/sdc4


/dev/sdc4: ********** WARNING: Filesystem still has errors **********

[email protected]:~$
 
Last edited:

Dbl-trouble

Novice Member
Re my issue above, I'm not finding any obvious solutions via google.

Is there an easy "nuclear" option, to just format that partition empty?

thanks, Martin
 

Dbl-trouble

Novice Member
mkfs.ext3 /dev/sdc4
Great, thanks, that ran OK. I also resized sdc4 (some of my searching led me to parted) to use the small amount of unused space at the end of the drive, which runs checks before & after and they listed the partition as fine.

The firmware appears to have installed OK - reports 4.08 at boot, I can now get to the web interface on the box, and Browse Media Files is working. Woot!

I'm really stoked at the possibilities with the custom firmware, so thanks for your patient help.



But, telnet still failed for the same error:-
Install started
cp: unable to open `/opt/tmp/telnet_1.0_mips.opk': No such file or directory
Collected errors:
* make_directory: Cannot create directory `/opt//var': Read-only file system.
* make_directory: Cannot create directory `/opt/var': Read-only file system.
* make_directory: Cannot create directory `/opt//var': Read-only file system.
* pkg_init_from_file: Failed to make temp file /telnet_1.0_mips.opk.control.5VomKW: Read-only file system.
* rm_r: Failed to open dir : No such file or directory.
rm: cannot remove `/opt/tmp/telnet_1.0_mips.opk': No such file or directory
Install done
Perhaps something with chmod (though I'm not sure exactly what)?

Thanks again, Martin
 

raydon

Well-known Member
But, telnet still failed for the same error:-


Perhaps something with chmod (though I'm not sure exactly what)?

Thanks again, Martin
Nothing to do with chmod I'm afraid. You still have your original problem.

* make_directory: Cannot create directory `/opt//var': Read-only file system.

It looks like /dev/hd4 (the Music and Photos partition) is still not being mounted read/write. In which case the custom firmware cannot create the directory structure it requires. You can access the basic web interface simply because that is implemented entirely in firmware. However, if you try and click on the "Download & Install the Full Web Interface" button I suspect it will just return more Read-only errors in the status report. Try copying an mp3 from USB stick to Music, or a jpg to Photos to confirm the Read-only status.
 

Dbl-trouble

Novice Member
Nothing to do with chmod I'm afraid. You still have your original problem.

* make_directory: Cannot create directory `/opt//var': Read-only file system.

It looks like /dev/hd4 (the Music and Photos partition) is still not being mounted read/write. In which case the custom firmware cannot create the directory structure it requires. You can access the basic web interface simply because that is implemented entirely in firmware. However, if you try and click on the "Download & Install the Full Web Interface" button I suspect it will just return more Read-only errors in the status report. Try copying an mp3 from USB stick to Music, or a jpg to Photos to confirm the Read-only status.
Well, that didn't confirm read-only.

Went into file manager and the Photo directory didn't exist on the HD (hardly surprising). Tried copying a JPG (actually one of the early MSL images), and it created the Photo directory and worked! Eh, what?

So then I tried the telnet install again:-

Install started
Installing telnet (1.0) to root...
Configuring telnet.
Install done
The Humax firmware obviously created the Photo directory, and presumably did something to open the partition r/w, also. Time to try the full install on the web interface:-
Downloading http://hummypkg.org.uk/foxsat/base/Packages.gz. Inflating http://hummypkg.org.uk/foxsat/base/Packages.gz. Updated list of available packages in /opt/var/opkg/base.

Installing webif (2.71) to root... Downloading http://hummypkg.org.uk/foxsat/base/webif_2.71_mips.opk.
Installing jim-tcl (0.7.1) to root... Downloading http://hummypkg.org.uk/foxsat/base/jim-tcl_0.7.1_mips.opk.
Installing service-manager (1.1-1) to root... Downloading http://hummypkg.org.uk/foxsat/base/service-manager_1.1-1_mips.opk.
Installing busybox (1.18.4-1) to root... Downloading http://hummypkg.org.uk/foxsat/base/busybox_1.18.4-1_mips.opk.
Installing epg (1.5) to root... Downloading http://hummypkg.org.uk/foxsat/base/epg_1.5_mips.opk.
Installing sysclock (1.1) to root... Downloading http://hummypkg.org.uk/foxsat/base/sysclock_1.1_mips.opk.
Installing hmt (2.1) to root... Downloading http://hummypkg.org.uk/foxsat/base/hmt_2.1_mips.opk.
Configuring busybox.
Configuring jim-tcl.
Configuring service-manager.
Configuring sysclock.
Configuring epg.
Configuring hmt.
Configuring webif.

-------------------------------------------------------------------------------
!! CONGRATULATIONS !!
-------------------------------------------------------------------------------
You have successfully installed the full web interface and supporting packages.
Please restart your Foxsat HDR in order to complete the initialisation process.
-------------------------------------------------------------------------------
(I added some line breaks)

I think I'm sorted - fantastic!

cheers, Martin

Edit: and, of course, many thanks for all your help!
 
Last edited:
Status
Not open for further replies.

Trending threads

Latest News

Kef Reference Series gets new finish and additional model
  • By Andy Bassett
  • Published
Naim announces native Qobuz support for its streaming hardware
  • By Andy Bassett
  • Published
Disney+ generates $100M in mobile app spending since launch
  • By Andy Bassett
  • Published
Bang & Olufsen announces Beoplay E8 3rd generation wireless earphones
  • By Andy Bassett
  • Published
Top Bottom