T4 Fails to Re-boot

[Sandy B]

I was watching a recorded program at the same time I was recording another via HDMI in, when I got a flicking picture on my TV screen. As quickly as I could I power down via the rear power switch. After about 10 minutes I repowered however the T4 will not reboot, it is displaying the Beyonwiz Logo, but does not progress to the bubble screen.

Anybody got any good suggestions.

[Grumpy_Geoff]

How many times have you tried the bootup? If more than once, then try to reload the firmware.

[Paul_oz53]

I was watching a recorded program at the same time I was recording another via HDMI in, when I got a flicking picture on my TV screen. As quickly as I could I power down via the rear power switch. After about 10 minutes I repowered however the T4 will not reboot, it is displaying the Beyonwiz Logo, but does not progress to the bubble screen.

Anybody got any good suggestions.

This will sound almost ridiculous but my T4 did exactly that a few months back. Switch it off for at least 8 hours and try again.

I tried everything I could think off before ringing Warkus to send it off for repair. Opened it up, checked the PSU rails, fiddled with connections for the hard drive, etc. No joy. Wouldn't read a usb drive so I couldn't reflash.

Having left it switched off for at least a day I switched it back on as one final check before boxing it up - and remarkably, it fired up as though nothing had ever happened!

Switching off for an hour didn't help but after several hours it came good and has been operating normally ever since. Damned if I know why and Warkus didn't know either but it works as good as ever now. Maybe some residual charge somewhere locks something up but that's pure speculation. At least it's harmless to give it a try.

[Sandy B]

Thanks all for the quick reply.

I will try the 8 hour power off as the first alternative.

[Grumpy_Geoff]

I will try the 8 hour power off as the first alternative.

If it was me, that'd be the second choice. I'd try the firmware reload before waiting the eight hours.

[Sandy B]

If it was me, that'd be the second choice. I'd try the firmware reload before waiting the eight hours.

I did wait overnight and the T4 again failed to reboot. I was reluctant to reinstall the firmware as that would/did remove my direct external link to the attached hard drives. I have reinstalled the firmware from this site as noted below;

<T4 - http://beyonwiz.com.au/firmware/t4/beyo ... 17_usb.zip>

All appears to be working as normal now, without the "linkage" to the external drives. Another problem to solve, I really liked the old software which did not have this security feature and allowed access to external drives via "media"

I have noted that an update is available for the software, but when I previously tried to install it crashed out. Where can I find the up-date so I can try a USD upgrade.

Thanks

[MrQuade]

I did wait overnight and the T4 again failed to reboot. I was reluctant to reinstall the firmware as that would/did remove my direct external link to the attached hard drives. I have reinstalled the firmware from this site as noted below;

<T4 - http://beyonwiz.com.au/firmware/t4/beyo ... 17_usb.zip>

All appears to be working as normal now, without the "linkage" to the external drives. Another problem to solve, I really liked the old software which did not have this security feature and allowed access to external drives via "media"

There is nothing in the new update that should prevent you from accessing external drives.

Are you referring to this thread?
https://www.beyonwiz.com.au/forum/viewt ... 2&p=167095

If so, then you should be able to follow the advice there to resolve the issue.

Rather than sharing out /media/usb though (due to the inconsistency there), try sharing /media/

You can also share out /root like in the previous firmware versions, but you will be back to the old insecure sharing arrangement. Not a problem as long as you wear the risk yourself.

You can also use ftp if you prefer. Lots of ways to skin that particular cat.

[Grumpy_Geoff]

All appears to be working as normal now, without the "linkage" to the external drives. Another problem to solve, I really liked the old software which did not have this security feature and allowed access to external drives via "media"

What firmware did you have previously and what firmware did you load now (your link is a dud)? I'm guessing you loaded 20180417, so why didn't you restore your last backup, as it would have restored your Samba config file.

I have noted that an update is available for the software, but when I previously tried to install it crashed out. Where can I find the up-date so I can try a USD upgrade.

Are you referring to this 17.5-20190207 promoted to production release?

[Paul_oz53]

Thanks all for the quick reply.

I will try the 8 hour power off as the first alternative.

Glad to hear it's working after a reflash. Mine wouldn't recognise the USB to reflash when it was off for short periods. After the extended delay, it rebooted so I then reflashed it. Your sequence sounds different.

Regardless, I think the current firmware 17.5 20190207 is very stable and agree with GG's recommendation.

[Sandy B]

Sorry about the delayed response, I did not have a good day yesterday (not related to the T4).

Are you referring to this thread?
https://www.beyonwiz.com.au/forum/viewt ... 2&p=167095

If so, then you should be able to follow the advice there to resolve the issue.

Yes I was referring to the above mentioned thread, it's just that I am not capable of programing and I have to rely on my "expert" who lives in Adelaide. FTP does not give the flexibility as File Explorer (FE), e.g. I can not create a directory with FTP but can with FE.

Are you referring to this 17.5-20190207 promoted to production release?

Yes that is the update that I could not find, thanks.

Glad to hear it's working after a reflash. Mine wouldn't recognise the USB to reflash when it was off for short periods. After the extended delay, it rebooted so I then reflashed it. Your sequence sounds different.

Regardless, I think the current firmware 17.5 20190207 is very stable and agree with GG's recommendation.

Over the last few weeks when recording from Apple TV via HDMI input, I had "similar" problems, however I was able to do a simple reboot which resolved the issue. However this time it did not reboot and hence my problem.

Many thanks all for your assistance.

[Grumpy_Geoff]

...FTP does not give the flexibility as File Explorer (FE), e.g. I can not create a directory with FTP but can with FE.

You can create directories with an FTP client.

[Grumpy_Geoff]

Rather than sharing out /media/usb though (due to the inconsistency there), try sharing /media/

I just tried a write to a directory underneath a global path = /media share - teeny-weeny files can be written, but anything greater than 64KB can't be written.
So no change in behaviour in 20190207.
Specific references to external drives would still be needed.

[prl]

Rather than sharing out /media/usb though (due to the inconsistency there), try sharing /media/

I just tried a write to a directory underneath a global path = /media share - teeny-weeny files can be written, but anything greater than 64KB can't be written.

It's even more restrictive than that:

Code: Select all

root@beyonwizu4:/media/hdd/logs# mount
...
tmpfs on /media type tmpfs (rw,relatime,size=64k)
...

The size=64k means that the size of the filesystem is 64kB, not that that's the limit on file size.

Simple rule: don't put anything other than mount points in /media.

[Sandy B]

I know I am only dreaming, but would it not be nice if there was a plug-in/patch that could be installed which allowed access to <root>. I realise the security implications but if made clear to users prior to installation I would not see any problem.

This would certainly make life easier for people like me with very limited knowledge of programming and do not want to enter the operating system.

Well I can dream.

[peteru]

I know I am only dreaming, but would it not be nice if there was a plug-in/patch that could be installed which allowed access to <root>. I realise the security implications but if made clear to users prior to installation I would not see any problem.

There is no mechanism for a plugin to give instructions or warnings during installation.

do not want to enter the operating system.

Making the root directory available on the network is exactly that and more. It opens up the box not only to malware, but also to accidental damage by users.

The hurdle is intentional.

[prl]

do not want to enter the operating system.

Making the root directory available on the network is exactly that and more. It opens up the box not only to malware, but also to accidental damage by users.

Most of the people on the forum who say that they export the root file system from their Beyonwizes do it in order to be able to modify the firmware.

[Sandy B]

Making the root directory available on the network is exactly that and more. It opens up the box not only to malware, but also to accidental damage by users.

The hurdle is intentional.

Pardon my stupidity but if the path <root/media/usb> was introduced would that not pose the same risk as the current path of <root/media/movie>.

[MrQuade]

As we established previously there are other technical problems with sharing the USB mount that make it unusable. That may or may not be a solvable issue

[Grumpy_Geoff]

I know I am only dreaming, but would it not be nice if there was a plug-in/patch that could be installed which allowed access to <root>. I realise the security implications but if made clear to users prior to installation I would not see any problem.

This would certainly make life easier for people like me with very limited knowledge of programming and do not want to enter the operating system.

Why do you need to access the root file directory?

I'm guessing you're still on 20180417.
Why did you not restore from your last backup? That backup file would have had your SMB User Config file in it.

Regardless, on your PC, use Notepad to create a file named "smb_user.conf", with contents of -

Code: Select all

[USB-usb]
  comment = /sdb1
  path = /media/usb
  guest ok = yes
  read only = no

[USB-sdc1]
  comment = /sdc1
  path = /media/sdc1
  guest ok = yes
  read only = no

[USB-sdd1]
  comment = /sdd1
  path = /media/sdd1
  guest ok = yes
  read only = no

Then copy it onto your T4 as advised in your "Accessing </root>" thread from last year.

From that old thread of last year, you stated your second connected USB drive presented itself as /media/sdc2 so you'll need to make the appropriate adjustments for the second and third devices. You can easily find what they present as by going to MENU>>Information>>Devices, or by viewing the list of devices in the SimpleUmount plugin (in 20180417, BLUE button from live TV [in later f/w it's in the plugins column of the main menu]), or by going up a couple of levels in the media listing to /media contents.

[Sandy B]

Stupid question of the year, does the line <Code: Select all> have to be included in the Notepad created file named "smb_user.conf".

I was thinking of just copying your coding into Notepad and installing on the T4 via USB and File Commander

[Grumpy_Geoff]

Stupid question of the year, does the line <Code: Select all> have to be included in the Notepad created file named "smb_user.conf".

No, you don't include that line. If you click the 'Select all' link, then it selects all of the "code" lines and you can right-click on the "code block", then copy them for pasting elsewhere.

I was thinking of just copying your coding into Notepad and installing on the T4 via USB and File Commander

You can also copy the file to /etc/samba/ directory using FTP if you wish (and you've unlocked the 'root' user account).

[Sandy B]

Well that was easy, I don't now why I made all the fuss.

The only problem I had was that Notepad was creating a <smb_user.conf.txt> file, Quickly realised the problem and rectified.

Many thanks Grumpy

[Grumpy_Geoff]

Well that was easy, I don't now why I made all the fuss.

Now take a backup, so you won't have to do this again if you reload the 17.5-series 20180417 firmware or the later 20190207 and restore settings.
There appears to be a 19.3-series coming in due course, so you may have to repeat this process so keep this file somewhere.

[Sandy B]

Now take a backup, so you won't have to do this again if you reload the 17.5-series 20180417 firmware or the later 20190207 and restore settings.

Already backed up the file in 3 locations.

Again thanks

[Grumpy_Geoff]

Now take a backup, so you won't have to do this again if you reload the 17.5-series 20180417 firmware or the later 20190207 and restore settings.

Already backed up the file in 3 locations.

I'm talking about a settings backup taken on the PVR - MENU>>Setup>>Software manager>>Create backup.
Alternatively, via MENU>>Plugins>>Software management>>Backup system settings.

The system will offer to restore your settings after loading firmware. It save you having to perform a setup again (including your Samba User Config).

[Sandy B]

I'm talking about a settings backup taken on the PVR - MENU>>Setup>>Software manager>>Create backup.
Alternatively, via MENU>>Plugins>>Software management>>Backup system settings.

I thought that I had backup using MENU>>Setup>>Software manager>>Create backup. I will again try using the Plugins method to be sure.

[prl]

I'm talking about a settings backup taken on the PVR - MENU>>Setup>>Software manager>>Create backup.
Alternatively, via MENU>>Plugins>>Software management>>Backup system settings.

I thought that I had backup using MENU>>Setup>>Software manager>>Create backup. I will again try using the Plugins method to be sure.

Using MENU>Setup>Software manager>Create backup does exactly the same thing as PLUGIN>Software management>Backup system settings.