Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 10 of 10

Thread: Recorded files or Directory's will now not open.

  1. #1

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts

    Recorded files or Directory's will now not open.

    HELP!

    I have a VU+ Ultimo 4K
    I've had the machine & HDD for nearly 6 years
    I have a 2.00 TB HDD (25% was free space)
    I believe that I am running VIX 6.0 but I now have trouble finding information.
    I've disconnected 2 USB external drives that I store media files on.

    I started to get failed recordings and the message 'Write error while recording. Disk full?'

    I tried a reboot several times but again failed with later timer recordings.

    Looked on here for similar and then tried to mount

    'Blue button - ViX - Mount Manager - green button'

    It is showing
    HDD: ST2000LM015-2E81
    Size 2.00TB
    Mount: /media/hdd
    Device: /dev/sda1
    Type: ext4 R/W

    Tried this a few times but again no luck and eventually sometimes I cannot see any files or recordings or structure on the HDD, No files or directory will open without bombing the machine.


    If I do System -> Storage Devices - Filesystem check then;

    Checking File system ...
    Error: e2fsck -b 32768 <device>
    fsck.ext4: Input/output error while trying to open /dev/sda1


    Sorry I cannot remember how to copy the log file onto this post

    Am I going to have to reformat the drive and lose all the recording on the drive?
    Should a try a software update to 6.2 from a USB stick?

  2. #2

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts
    UPDATE

    Not had much time to look at this problem but when I came back to it I was getting the following:

    Error:
    /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)

    Could remember how to telnet the box and couldn't find a posting explaining how to do.

    Decided logically the the software was corrupt in some way.

    Managed to find that 1 was at Vix image 6.0.008
    When looked for software update it was saying that I was up to date.
    Went onto Vix website and found Image version 6.0.011 and loaded it on a my USB stick.
    Tried to update but but it would not work.
    Thank god the software guys had covered this and found the direct download software routine to the box.
    UPDATE worked this time, and I now have a stable working box again.

    THANKS to the software writers.

    I hope that this helps other users.

  3. #3

    Title
    ViX Beta Tester
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    2,049
    Thanks
    404
    Thanked 668 Times in 547 Posts
    Quote Originally Posted by DigitalAardvark View Post

    Error:
    /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)

    .
    Your hard drive is the problem. Maybe it is just corrupted data from power failures etc or else the drive may be failing.
    Zgemma H7S running OpenVIX 6.2, Darkmotor, Triax TD110 dish, Inverto Black Ultra dual lnb
    LG 50UM7450 4K TV, Pioneer VSX-534 Atmos AVR , Panasonic UB820 region free 4K Bluray & a PS4.

  4. The Following User Says Thank You to ronand For This Useful Post:

    DigitalAardvark (05-11-22)

  5. #4

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts
    Technically I'm struggling with Telnet the box.
    I've googled and searched on here but can't find idiots instructions for this.

    Would taking the hard drive out and using my PC to do a cleaning job on the drive, work.
    Widows 10 seems to find and clean up drives automatically.

    It seems to be recording and playing back the files that I have tried, but maybe the problem is elsewhere on the drive.

  6. #5

    Title
    ViX Beta Tester
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    2,049
    Thanks
    404
    Thanked 668 Times in 547 Posts
    Windows 10 cant work natively with linux drives. Telnet is simple. Download a telnet client like putty. You will need the IP address of your receiver (menu->information->network). When you connect to the ip address you will see a login prompt - the username will be root and the password will be one that you set yourself on the receiver (Menu->setup->network->password). then run the fsck command
    Zgemma H7S running OpenVIX 6.2, Darkmotor, Triax TD110 dish, Inverto Black Ultra dual lnb
    LG 50UM7450 4K TV, Pioneer VSX-534 Atmos AVR , Panasonic UB820 region free 4K Bluray & a PS4.

  7. The Following User Says Thank You to ronand For This Useful Post:

    DigitalAardvark (05-11-22)

  8. #6
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,612
    Thanks
    2,006
    Thanked 4,947 Times in 3,269 Posts
    And if you don't know the ip you should just be able to use "vuultimo4k.local".
    Help keep OpenViX servers online.Please donate!

  9. #7

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts
    Many thanks for everybody's help, very good instructions but I had trouble getting Putty going (its me, only low level technically)

    Finally I got here after using IP address and password

    root@vuultimo4K:~# fsck

    got back

    fsck (busybox 1.35.0)
    fsck: fsck.auto: No such file or directory

    Was this correct. Here I am stuck

  10. #8

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts
    I should add that no files are being displayed now.

    It is an ssd drive

  11. #9

    Title
    Member
    Join Date
    Jan 2017
    Posts
    34
    Thanks
    16
    Thanked 0 Times in 0 Posts
    Thinking that the hard drive is the problem as nothing showing now so decided that the easiest option was to get a replacement internal hard drive.
    I have run through the installing routine for the new hard drive but find that the default movie location has not been created.
    Only lost+found and .trash and timeshift folders have been created.

    I've been looking on here for a solution to this.

    Again many thanks for the help.

  12. #10

    Title
    ViX Beta Tester
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    2,049
    Thanks
    404
    Thanked 668 Times in 547 Posts
    Just create a "movie" folder (and any others you might need). Initialising the drive does not create the folder - it it only done when first installing the image.
    Zgemma H7S running OpenVIX 6.2, Darkmotor, Triax TD110 dish, Inverto Black Ultra dual lnb
    LG 50UM7450 4K TV, Pioneer VSX-534 Atmos AVR , Panasonic UB820 region free 4K Bluray & a PS4.

  13. The Following User Says Thank You to ronand For This Useful Post:

    DigitalAardvark (24-11-22)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.