Network browsers no longer displaying other T2s IP address.

[peteru]

All as expected on a normally functioning system. Including a final black screen for a configuration with no valid service (or switched to HDMI input on T4/U4).

[Chrilynn2]

Just to confirm, the T2 is stuck on the splash screen, it hasn’t gone black on the reboot, and doesn’t respond to the remote.
I will now go ahead with the firmware update from USB.
Fingers crossed.

[Chrilynn2]

Just the start up, and splash screen on reboot.
It’s stuck on the bubbles screen, no black screen, and doesn’t respond to the remote.
Going ahead with a firmware update , of the new beta, from USB

[Chrilynn2]

Firmware upgrade worked successfully.
I haven’t yet installed the switch feed script, or made any changes.
I will get back to the original problem, once everything else is working.
I also have to update the other T2.
Assuming that’s got the online update ready, that fell over this morning on my first T2, do I go ahead and see if that
Has the same issues, or simply do USB update?

[MrQuade]

Has the same issues, or simply do USB update?

Easier and safer to do the USB update.

[Chrilynn2]

Hi MrQuade.
I decided to go ahead with the online updates on the other T2 and it worked.
I didn’t get the crash, as with the other T2.
Interestingly the online one had a different revision to the one that failed this morning.
I rechecked the software updates and sure enough they were waiting there to be updated.
I did this and now the two of them are in line.
So the online update for one worked fine but the other crashed and had to have a full USB update, and online refresh.
One interesting development is that now the T2, wired directly to the modem is reading the others files.
I didn’t do a dismount, and remount, it simply works since the software update.
I will now mount the second T2, to see if this now works, also.
Network browser still shows only the IP addresses.
I checked the auto.network file and it is now empty of data, on the USB firmware update T2, and there is no auto mounts.xml file
at all.
The online updated T2 does have the files, as mentioned by Grumpy_Geoff.
When you said to rename them, does clicking the blue rename button clear them, or is there a further step required?
I have now given each of them a name, as suggested by Grumpy_Geoff, but, as I said, nothing but IP addresses shows up on network browser.

[Chrilynn2]

The mount for the other T2’s files did not work, as before, so the fault reported originally on this feed still exists.
The mount for the NAS works fine, on both T2s.
So one T2 can now read the other’s files, but, not in reverse.
That anomaly is frustrating, especially if I am not following the correct procedure to mount the shares.

[Chrilynn2]

This is the auto.network file after the failed mount attempt.

691869AD-C8F5-4F2B-9880-6C402B2A4BE2.jpeg (110.13 KiB) Viewed 2589 times

[MrQuade]

This is the auto.network file after the failed mount attempt.

It seems to be fine now from looking at the config file.

Another question. Do you map a drive letter to either of your T2s from a Windows PC?


I am wondering if this is another case where changing from autofs to fstab style mount fixes the problem, and I am still trying to work out why that fix works for folks like Paul_oz53.
I am wondering if perhaps when Windows mounts a network share to a drive letter, it set some exclusive access flag that autonetwork chokes on.

[Grumpy_Geoff]

folks like Paul_oz53.

Speaking of Paul, I believe he has the same modem/router as Chrilynn2, a TP-Link VR1600v. I don't believe he has any name resolution / network browser issues. Paul?

[Grumpy_Geoff]

One T2 is wired to the modem.
The other through a WiFi extender, to which it is wired.

So one can now see the other, but not the reverse.
Which one had the USB update applied (which would've cleared out the mount files, unless you restored settings)?
From a command prompt on your computer, can you ping each T2 by their respective names? You did give them different names, right?
Have you rebooted the wireless extender?

[Chrilynn2]

The one that can see the other T2 is the one updated online.
The one that can’t see the other T2 was the one updated from USB.
I didn’t reboot the WiFi extender after this update but I have done so over the period of the problem solving.
I did rename the T2s, as you suggested.
Thanks for confirming the file refreshes after a USB update, the other didn’t.
I have been able to ping the T2s via a third party app on my IPad.
It recognises the name change on the problem T2, but not the one that is wired directly.

[Grumpy_Geoff]

The one that can’t see the other T2 was the one updated from USB.

Delete the mounts for the "can't see" T2 on this box.
Reboot.
Do a network browser scan and mount those "can't see" mounts as type "FSTAB".
Save.
See how you go then.

[sub3R]

The one that can see the other T2 is the one updated online.
The one that can’t see the other T2 was the one updated from USB.

That sounds familiar. I don’t want to interfere with the good advice you are getting, but if everything else fails (including peteru’s advice), try USB updating with restore settings the Server T2 (the one the other T2 [the Client] can’t see).

[Chrilynn2]

Well, it gets more interesting.
Online update came through again today, so I did the update with no problems.
As per Grumpy_Geoff’s advice I deleted the mount on the T2 that would not display the other T2.
I rebooted, then did the remount FSTAB.
Bingo, I can now read the other T2.
I checked the wired T2 , after doing the online update but it no longer displayed the other T2.
So I thought, Ok, demount reboot, mount as FSTAB, as per advice.
Unfortunately, when I tried to access setup it crashed, and gave me the enigma crash file advice, then rebooted.
Fortunately it rebooted successfully, and behaved Ok.
I tried accessing setup again, a couple of times, but same result.
Where to from here?
Do I redo the firmware from USB, as per the other T2, and hope it was a small glitch from doing the update from online.
I couldn’t save the crash file to USB, not sure what the other options are, I displayed it but it’s far too long to screen dump, and attach.
Sorry it’s taken so long to respond to yesterday’s advice.

[peteru]

Post the crash file here. If there is a crashing issue, I'd like to jump on it straight away and get it fixed before the next release.

[Chrilynn2]

I notice in a parallel thread that it was possible to copy a crash file, to a USB stick, for posting to the forum.
I attempted this through sources/files, internal flash, but with no luck.
I could access, and read the crash files but nothing happened when I clicked on yellow(copy), or green(move).
What might I be doing wrong?

[Grumpy_Geoff]

I notice in a parallel thread that it was possible to copy a crash file, to a USB stick, for posting to the forum.
I attempted this through sources/files, internal flash, but with no luck.
I could access, and read the crash files but nothing happened when I clicked on yellow(copy), or green(move).
What might I be doing wrong?

Not opening the target device and folder in the "other" panel.
The source panel is the one with the file(s) selected.

[Chrilynn2]

Sorry Grumpy_Geoff, I’ve forgotten how to jump to the other panel!

[sub3R]

I could access, and read the crash files but nothing happened when I clicked on yellow(copy), or green(move).
What might I be doing wrong?

WizHQ made a YouTube video under ‘Beyonwiz T2/T3/T4/U4/V2 >> FAQs, Tips & How to Guides’ called ‘Video: Transferring Recordings’.

If you go straight to 10:31 in that video it gives instructions from that spot onwards on how to transfer recordings from a Wiz to a USB drive plugged into the Wiz using the File Commander. This is the same procedure for copying the crash file to a USB drive.

When in File Commander HELP is very helpful as is MENU.

[MrQuade]

Sorry Grumpy_Geoff, I’ve forgotten how to jump to the other panel!

NEXT/PREV

[Chrilynn2]

Thank you, now to get the file onto the USB stick.

[Chrilynn2]

Ok, how do I get the file onto the USB stick.
Thank you

[Grumpy_Geoff]

Ok, how do I get the file onto the USB stick.
Thank you

Try this method instead -
In a browser on your computer, open this URL - file://{IP-address-of-T2}/Logs/
You should see a list of files, one at least will be the crash log in question.
Right-click it, choose the "save link as" option and download it to the computer.

You should also be able to open that particular T2's "Logs" share in Windows File Explorer, then just drag and drop the crash log.

[Chrilynn2]

Once again I must apologise for the delay in updating.
I have finally figured out how to copy the crash files onto USB.
The crash happened again this morning.
There was a new online update this morning.
I have not run it for the T2 that keeps crashing but it appeared to work Ok on the T2 that was updated by USB.
Hopefully the attachments will be useful peteru.
Eventually I hope to be able to logon to the T2s by URL as per other suggestions.
At the moment I can only access OpenWebif, I keep getting weird results for ftp URLs.
Thank you.

[Grumpy_Geoff]

The crash happened again this morning.

I'm an amateur at this, but my guess is you've a screwed /etc/enigma2/automounts.xml file.
Please grab it and attach here.

[prl]

The crash is happening because the file that contains the mountpoint definitions, /etc/enigma2/automounts.xml, isn a valid XML file.

I can get the same error if I try to read an empty file using the same calls that the code that reads automounts.xml uses, so I suspect that the file has been emptied somehow, but it may be broken in some other more inventive manner.

Even when there are no mounts it should contain:

Code: Select all

<?xml version="1.0" ?>
<mountmanager>
</mountmanager>

As Grumpy_Geoff suggests, please post it here.

[Chrilynn2]

Ok.
I got the automounts.xml file but on an attempt to attach it I got a
file too large to attach message

[Chrilynn2]

Tried it again.
Still says file too large

[MrQuade]

Ok.
I got the automounts.xml file but on an attempt to attach it I got a
file too large to attach message

Well there's your problem!

That file should only be a few hundred bytes in length.

How big is yours??

[Chrilynn2]

I've just had a look at the file, on the T2 and it is blank, no data.
I also looked at the copy on the USB stick I copied it to using the other T2 and it is blank, whereas the file on the T2 which didnt crash has data.

[Chrilynn2]

The file on the working T2 has 45 lines

[Grumpy_Geoff]

If it were me -
I'd delete /etc/enigma2/automounts.xml and /etc/auto.network using File commander.
Then reboot.
Then perform an online update to 20210825 (which is the latest that came overnight).
Then cleanup the opkg config clashes - by running prl's script from here - viewtopic.php?f=56&t=14841#p196090
And as posted there -
"You still need to run switch_feed_to_beta.sh after the opkg-fix.sh script runs."

If that doesn't work, then -
flash it with 20210825 via USB - don't restore settings, set it up from scratch

[Chrilynn2]

Thanks Grumpy_Geoff.
I may try that, if nothing further comes up.

[prl]

I've just had a look at the file, on the T2 and it is blank, no data.
I also looked at the copy on the USB stick I copied it to using the other T2 and it is blank, whereas the file on the T2 which didnt crash has data.

I said that I thought that a likely cause was that the file was empty.

[prl]

Ok.
I got the automounts.xml file but on an attempt to attach it I got a
file too large to attach message

Well there's your problem!

That file should only be a few hundred bytes in length.

How big is yours??

The forum incorrectly complains that the file is too large if you try to upload an empty file.

[Chrilynn2]

Just a thought bubble, on the basis that there is no such thing as a stupid question.
What would happen if I deleted the file from the crashed T2 and substituted it with a copy of the other T2’s file?
What might need to be rewritten in the copy?

[prl]

Just a thought bubble, on the basis that there is no such thing as a stupid question.
What would happen if I deleted the file from the crashed T2 and substituted it with a copy of the other T2’s file?

The copy of /etc/enigma2/automounts.xml would then probably be out of sync with the system files that it is used to modify: /etc/fstab and /etc/auto.network. It would likely make your situation even messier than what it is now.

What might need to be rewritten in the copy?

Impossible to know without knowing what the content of the three files is.

My suggestion is that at this point the crashed T2 should either have a Factory reset done, or have its firmware reloaded from USB, without restoring settings, and that you re-do all your settings on it.

[peteru]

Thanks for the crash logs. I have a fix to prevent crashes.

[Chrilynn2]

Thanks for the feedback peteru, I’m so glad I figured out how to do it.
At this point I think I’ll let yesterday’s online update run, and If that still crashes on accessing setup I’ll run the update from USB.
I thought that messing with the files was more likely to cause problems, than fix them.

[Chrilynn2]

Just to confirm, I ran yesterdays online update and the T2 still crashes when I access setup.
Here is the last log from the last crash:

[peteru]

I only posted less than an hour ago, so clearly yesterday's update can not fix that!

[Chrilynn2]

Ok,
I’ve reinstalled the beta firmware, via USB, on the T2 which had the crash, and the script.
All seems to have gone well and the online updates have been completed.
Settings have been restored manually with no problems, and accessing setup does not lead to a crash.
I have only one area for concern, at this time, and that is that I am getting the spin when I try to access media.
It allows me to exit but otherwise the spin continues.
I have switched off for the time being and will try again later, but have lost the link to this T2 that I established previously.
Not sure what’s gone wrong with that.
More questions.
Thanks for all previous contributions.

[Grumpy_Geoff]

I’ve reinstalled the beta firmware, via USB, on the T2 which had the crash, and the script.
All seems to have gone well and the online updates have been completed.

What online updates? There shouldn't have been any if you loaded 20210825 as advised.

[Chrilynn2]

Ok, now I’m confused Grumpy_Geoff.
I downloaded the current firmware from the beta thread again, also ran the script, and there was an online software update available.
Information/about shows the revision you quote, after the update.
Is there anther thread with the current update zip, which does not require a further online update?

[sub3R]

In peteru’s post here

[Chrilynn2]

Ok, I’d just spotted it, in the beta thread, also.
Would this work better than the online update, using the script?

[Chrilynn2]

I’d not thought to look at the end of the beta thread for the latest revision.

[peteru]

There will be a new update coming tonight that will have a lot of improvements to the mount editor.

I strongly suggest that you update by flashing the 20210826 USB image and DO NOT RESTORE backup. Instead, set up from scratch using the new firmware.