V2 error while preparing to record, disc full

[mishmash]

Hi everyone,
I've been running my V2 with a 256GB SD card for about a year. Recently I'd had a lot recording fail with an error message suggesting the disc is full - which it isn't. I figured the card had become corrupt so tried a USB SSD I had on hand. The V2 throws the same error instantly. I have "surface" tested both the SD card and the SSD and no errors have been reported.
Before I run out and buy another external drive I am wondering if there's something else going on?

I formatted the SD card as exFAT and plugged that into the V2. The V2 shows it as exFAT but if I do a file system check on it the unit crashes (log attached).
I know it needs to be EXT4 for the unit, but I didn't think it'd crash...
Anyone else having any similar issues with the disc being "full" when it's not?

Thanks in advance.

[mishmash]

Update.
I think the v2 is having a heart attack
Now I can't get past the bubble splash screen. That stays on screen. Change channel and the channel info bar comes up as normal but no TV content.
Menu system works ok.
Maybe another factory reset....

[MrQuade]

Update.
I think the v2 is having a heart attack
Now I can't get past the bubble splash screen. That stays on screen. Change channel and the channel info bar comes up as normal but no TV content.
Menu system works ok.
Maybe another factory reset....

If you see the bubbles screen, but the Infobar and all the other menus work as normal, it means that the V2 can't tune to a service.

Check your antenna connections to start with.

[Grumpy_Geoff]

If you see the bubbles screen, but the Infobar and all the other menus work as normal, it means that the V2 can't tune to a service.

Check your antenna connections to start with.

My thoughts too, but it could also be that the service scan tables have gone.

[mishmash]

If you see the bubbles screen, but the Infobar and all the other menus work as normal, it means that the V2 can't tune to a service.

Check your antenna connections to start with.

As usual, Mr Quade, you are correct. The aerial had dislodged a smidge with all the faffing about around the back.
I'll give the SD card one more go before I abandon it....

[Grumpy_Geoff]

I'll give the SD card one more go before I abandon it....

Where does it report the disk is full - in the timer's log entries?
Perhaps check the file /var/log/messages to see if any disk access errors are being reported (or grab a copy and attach it to a post and someone here may have a look).

[mishmash]

Where does it report the disk is full - in the timer's log entries?

It's an on-screen dialogue box.

Perhaps check the file /var/log/messages to see if any disk access errors are being reported (or grab a copy and attach it to a post and someone here may have a look).

I couldn't see anything obvious and really only entries from Jan 1 and today. File attached.

[Grumpy_Geoff]

Perhaps check the file /var/log/messages to see if any disk access errors are being reported (or grab a copy and attach it to a post and someone here may have a look).

I couldn't see anything obvious and really only entries from Jan 1 and today. File attached.

1-Jan timestamps are from when the box boots and before it contacts the time server.

There doesn't appear to be any "disk" errors listed for the microSD card.
However, there doesn't appear to be any USB tuner detected. It may be dead. Dead USB tuners have been known to cause all sorts of issues.

[mishmash]

However, there doesn't appear to be any USB tuner detected. It may be dead. Dead USB tuners have been known to cause all sorts of issues.

Or missing....I only have the 2 internal tuners

[Grumpy_Geoff]

However, there doesn't appear to be any USB tuner detected. It may be dead. Dead USB tuners have been known to cause all sorts of issues.

Or missing....I only have the 2 internal tuners

Well we can't blame a dead USB tuner then.

[prl]

Has the firmware flash somehow got filled up? In MENU>Information>Memory, how much free space is reported for "FLASH"?

[mishmash]

Has the firmware flash somehow got filled up? In MENU>Information>Memory, how much free space is reported for "FLASH"?

Says there's 6GB free.
I managed to run 2 concurrent recordings last night with no issue.
I'm going to just put this down to a glitch in the matrix and see how things go.
Thanks all for your responses, as always.
Ta lotsly

[prl]

OK, not that, then

[maverick#1]

I have the same problem every now and then on my U4. I have a 3TB HDD installed in it. The error seems to occur for me when there is a timer recording and I turn the U4 on. As soon as the PVR comes out of standby, the on-screen popup error message appears. The recording works up to the point where I turned the PVR on but the .ap or .sc file (I can't remember which) is missing and the recording can't be edited. I then can't record until I do a complete shutdown, but once I turn the U4 back on, it records fine.

[maverick#1]

I had this error occur again recently. I'm now suspecting that my problems are because the HDD I'm using is a shingled magnetic recording (SMR) drive. I suspect that the write buffer was full when the error occurred and the write speed of the drive dropped drastically. I've seen this in Windows when copying large amounts of data to SMR drives.

Also, the timer recording had something like the following in the timer info:

WRITE ERROR while recording, mount {file_location} is not writeable.

The error log had something like this:

Warning: All write buffers busy
Waiting for I/O to complete

I'm thinking of trying a conventional magnetic recording (CMR) drive with the U4 and seeing if the errors continue occurring.

[maverick#1]

UPDATE:
A day or two after my last post I took the 3TB SMR hard disk out of my U4 and replaced it with a 2TB CMR hard drive. Since then I haven't had any timer or general recording failures.

I definitely won't be using a shingled drive with any of my PVR's anymore. I'll only use CMR HDD's or SSD's from now on.

[maverick#1]

I just found this post which adds support to the idea that it's the SMR drive that was causing the recording problems on my U4:

Stream writing to a non-fragmented file system on a shingle drive initially works well, BUT once the file system has become used and reused beyond some point shingle rewrite overhead becomes horrific. At that time you basically need to reformat the partition and start again.