January 13, 2013

Samsung Smart TV - PVR HDD device error - solved!

Samsung Smart TV model ES5500 with Personal Video Recorder. After about two weeks of recording and only ~30 recordings I got this two messages. It's like I lost all my recordings. The TV is brand new, the attached HDD is brand new. Shame on you, Samsung!
The solution is bellow:

Fond this on internet and is working like a charm (but you will need a Linux PC or a bootable Linux CD):
- connected the corrupted USB HDD to a USB port on a Linux PC (Xubuntu 10.11 in my case but you can use Ubuntu or other Linux distro as well).
- Linux says something like "Cannot mount the drive I/O error..."
- open terminal
- typed "sudo xfs_repair -L /dev/sdc1" (you must see what sd is your hdd or your damaged partition - use gparted for this)
That's all folks!
If you have problems please comment or email me for help. In my case I recovered all my recordings but not the last one - maybe that one was with problems. When I try to play that recording a message about DRM appeared. Samsung, you must work on your software!


  1. note for me: in my case, sdb2 (GParted...Device...select sdb...)

  2. a list like this will appear, the important option is the word "done" bellow :)

    ubuntu@ubuntu:~$ sudo xfs_repair -L /dev/sdb2
    Phase 1 - find and verify superblock...
    Phase 2 - using internal log
    - zero log...
    ALERT: The filesystem has valuable metadata changes in a log which is being
    destroyed because the -L option was used.
    - scan filesystem freespace and inode maps...
    agi unlinked bucket 25 is 4273625 in ag 0 (inode=4273625)
    sb_icount 512, counted 576
    sb_ifree 21, counted 55
    sb_fdblocks 12918380, counted 10865246
    - found root inode chunk
    Phase 3 - for each AG...
    - scan and clear agi unlinked lists...
    - process known inodes and perform inode discovery...
    - agno = 0
    a7b14b70: Badness in key lookup (length)
    bp=(bno 2136784, len 16384 bytes) key=(bno 2136784, len 8192 bytes)
    - agno = 1
    - agno = 2
    - agno = 3
    - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
    - setting up duplicate extent list...
    - check for inodes claiming duplicate blocks...
    - agno = 1
    - agno = 0
    - agno = 2
    - agno = 3
    Phase 5 - rebuild AG headers and trees...
    - reset superblock...
    Phase 6 - check inode connectivity...
    - resetting contents of realtime bitmap and summary inodes
    - traversing filesystem ...
    bad hash table for directory inode 131 (no leaf entry): rebuilding
    rebuilding directory inode 131
    - traversal finished ...
    - moving disconnected inodes to lost+found ...
    Phase 7 - verify and correct link counts...
    resetting inode 119 nlinks from 1 to 2
    resetting inode 120 nlinks from 1 to 2
    resetting inode 121 nlinks from 1 to 2
    resetting inode 122 nlinks from 1 to 2
    resetting inode 123 nlinks from 1 to 2
    resetting inode 4273625 nlinks from 0 to 1


Note: Only a member of this blog may post a comment.