trying to identify file (if any) corresponding to LBA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm running 64-bit F29 using the default LVM, but with no separate home partition. Today smartctl reported that "Current_Pending_Sector" and "Offline_Uncorrectable" increased from 0 to 1. Running a self-test failed almost immediately with

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     42494         3299402936

I'm trying to follow the instructions in https://www.smartmontools.org/wiki/BadBlockHowto . Fdisk gives

[root@lenovo-pc ~]# fdisk -lu /dev/sda
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc3017146

Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda1  *         2048    1026047    1024000   500M  7 HPFS/NTFS/exFAT
/dev/sda2         1026048  536872959  535846912 255.5G  7 HPFS/NTFS/exFAT
/dev/sda3       536872960  538970111    2097152     1G 83 Linux
/dev/sda4       538970112 3907028991 3368058880   1.6T  5 Extended
/dev/sda5       538972160 3907028991 3368056832   1.6T 8e Linux LVM
[root@lenovo-pc ~]#

so the bad LBA is in both sda4 and sda5. Trying tune2fs to find the block size gives

[root@lenovo-pc ~]# tune2fs -l /dev/sda4 | grep Block
tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda4
Couldn't find valid filesystem superblock.
[root@lenovo-pc ~]# tune2fs -l /dev/sda5 | grep Block
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
[root@lenovo-pc ~]# tune2fs -l /dev/mapper/fedora-root | grep Block
Block count:              419037184
Block size:               4096
Blocks per group:         32768
[root@lenovo-pc ~]#

so I'm guessing that the block size is 4096. In computing the problem block, I'm not sure whether to use /dev/sda4 or /dev/sda5. Also, if I run debugfs, it doesn't allow me to open either device, so at this point I'm not sure how to identify either the inode or file (if there is one) corresponding to the block. Can anyone help?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux