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 5 of 5

Thread: Recordings listings slow to load and playback judders

  1. #1

    Title
    Member
    Join Date
    Mar 2016
    Posts
    80
    Thanks
    27
    Thanked 7 Times in 5 Posts

    Recordings listings slow to load and playback judders

    I have noticed the recording listing being very slow to load and playback recordings juddering and the sound dropping out. Is this the end of my hard drive or does anyone know of a fix for this?

    TIA

  2. #2

    Title
    Forum Supporter
    Donated Member
    Join Date
    Jun 2014
    Posts
    1,321
    Thanks
    612
    Thanked 418 Times in 270 Posts
    Could be. See this post for putty/telnet command for checking HDD.

  3. The Following 2 Users Say Thank You to bbbuk For This Useful Post:

    abu baniaz (02-01-21),gdmm (01-01-21)

  4. #3

    Title
    Member
    Join Date
    Mar 2016
    Posts
    80
    Thanks
    27
    Thanked 7 Times in 5 Posts
    This is the text

    umount /dev/sda1
    e2fsck -p -c -f /dev/sda1root@vusolo2:~# umount /dev/sda1
    root@vusolo2:~# e2fsck -p -c -f /dev/sda1
    sh: badblocks: command not found
    /dev/sda1: Updating bad block inode.
    /dev/sda1: 4258/262432 files (0.7% non-contiguous), 1658496/122096384 blocks

    This doesn't mean a thing to me. Can you interpret?

  5. #4

    Title
    Member
    Join Date
    Mar 2016
    Posts
    80
    Thanks
    27
    Thanked 7 Times in 5 Posts
    PS

    Whatever that script did, it appears to have worked. Thanks for your help.

  6. The Following User Says Thank You to gdmm For This Useful Post:

    bbbuk (02-01-21)

  7. #5

    Title
    Forum Supporter
    Donated Member
    Join Date
    Jun 2014
    Posts
    1,321
    Thanks
    612
    Thanked 418 Times in 270 Posts
    Quote Originally Posted by gdmm View Post
    PS

    Whatever that script did, it appears to have worked. Thanks for your help.
    If it's working now after running that check disk command (and nothing else was changed) then it's likely you had/have HDD errors.

    Could have been just structure issue (nothing major) or sign of HDD starting to fail (major).

    Assuming the command works similar to Windows' chkdsk command then that command told it to check for errors (including bad sectors/blocks) and fix them or mark bad sectors/blocks as such to prevent further files being written to that sector/block. Adding the -v option displays more information about what it's doing/done/found.

  8. The Following User Says Thank You to bbbuk For This Useful Post:

    gdmm (02-01-21)

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.