perryt
(perry tsacoumis)
December 2, 2020, 3:16pm
1
i am stroke and aphasia (not words and not numbers) –
i am HP laptop and 2 fedora 33 and windows.
i am Clonezilla when clone disk and disk. i am HP laptop disk for HP error 301. it is Clonezilla is error disk data.
i am CD Fedora 33 live disk. i am
sudo mount /dev/sda7 /mnt
sudo badblocks -o badblocks.txt /dev/sda7
sudo mke2fs -l badblocks.txt -n /dev/sda7
/dev/sda7 is apparently in use by the system; will not make a filesystem here!
sudo mount /dev/sda7 /mnt
mount: /mnt: unknown filesystem type ‘LVM2_member’.
[liveuser@localhost-live ~]$ sudo e2fsck -l badblocks.txt /dev/sda7
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda7 is in use.
e2fsck: Cannot continue, aborting.
[liveuser@localhost-live ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 5.8G 0 5.8G 0% /dev
tmpfs 5.8G 42M 5.8G 1% /dev/shm
tmpfs 5.8G 9.9M 5.8G 1% /run
/dev/sr0 1.9G 1.9G 0 100% /run/initramfs/live
/dev/mapper/live-rw 7.4G 5.5G 1.9G 76% /
tmpfs 5.8G 92K 5.8G 1% /tmp
vartmp 5.8G 0 5.8G 0% /var/tmp
tmpfs 1.2G 5.3M 1.2G 1% /run/user/1000
/dev/sdb6 477M 252M 196M 57% /run/media/liveuser/06137cb7-c8a7-4156-8839-fd372c42121b
/dev/sdb3 120G 64G 57G 53% /run/media/liveuser/Windows
/dev/sda1 200M 8.8M 192M 5% /mnt
/dev/sdb1 200M 8.7M 192M 5% /mnt/sdb1
??? what ? how ?
lcts
(Christopher Engelhard)
December 4, 2020, 9:55am
2
Hi, not familiar with badblocks or any errors related to that, but from what you write it seems like you’re trying to mount a logical volume, rather than the filesystem contained within it. The actual filesystem will be under /dev/mapper/...
.
Could you run
lsblk
from your livesystem and post here what it says?
perryt
(perry tsacoumis)
December 4, 2020, 3:33pm
3
[liveuser@localhost-live mnt1]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 1.7G 1 loop
loop1 7:1 0 7.5G 1 loop
├─live-rw 253:0 0 7.5G 0 dm /
└─live-base 253:1 0 7.5G 1 dm
loop2 7:2 0 32G 0 loop
└─live-rw 253:0 0 7.5G 0 dm /
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 200M 0 part /mnt
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 119.8G 0 part
├─sda4 8:4 0 980M 0 part
├─sda5 8:5 0 15.4G 0 part
├─sda6 8:6 0 500M 0 part
└─sda7 8:7 0 794.6G 0 part
├─fedora-swap 253:2 0 5.8G 0 lvm
├─fedora-root 253:3 0 80G 0 lvm
└─fedora-home 253:4 0 708.8G 0 lvm
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 200M 0 part /mnt1
├─sdb2 8:18 0 16M 0 part
├─sdb3 8:19 0 119.8G 0 part
├─sdb4 8:20 0 980M 0 part
├─sdb5 8:21 0 15.4G 0 part
├─sdb6 8:22 0 500M 0 part
└─sdb7 8:23 0 794.6G 0 part
sr0 11:0 1 1.9G 0 rom /run/initramfs/live
perryt
(perry tsacoumis)
December 5, 2020, 3:30pm
4
i am computer disk trouble!!
[liveuser@localhost-live mnt1]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 4.0
loop1 ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7
├─live-rw ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7 1G 86% /
└─live-base ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7
loop2
└─live-rw ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7 1G 86% /
sda
├─sda1 vfat FAT16 8A18-7BB5 191.1M 4% /mnt
├─sda2
├─sda3 ntfs Windows 2CAEF147AEF10A5A
├─sda4 ntfs Windows RE tools 564EBE4A4EBE22A3
├─sda5 ntfs RECOVERY B2649FFB649FC111
├─sda6 ext4 1.0 06137cb7-c8a7-4156-8839-fd372c42121b
└─sda7 LVM2_memb LVM2 001 NiiWMH-aRIa-nhO5-TgJ7-LU7u-lipW-lyZDbc
├─fedora-swap
│ swap 1 5b8c3d81-8f09-4aaa-9604-277e20018558
├─fedora-root
│ ext4 1.0 7dc8cbc1-a5c9-43ef-8aae-09560e51bef4
└─fedora-home
ext4 1.0 04066381-5562-4ea0-9024-042a5529ec17
sdb
├─sdb1 vfat FAT16 8A18-7BB5 191.1M 4% /mnt1
├─sdb2
├─sdb3 ntfs Windows 2CAEF147AEF10A5A
├─sdb4 ntfs Windows RE tools 564EBE4A4EBE22A3
├─sdb5 ntfs RECOVERY B2649FFB649FC111
├─sdb6 ext4 1.0 06137cb7-c8a7-4156-8839-fd372c42121b
└─sdb7 LVM2_memb LVM2 001 NiiWMH-aRIa-nhO5-TgJ7-LU7u-lipW-lyZDbc
sr0 iso9660 Joliet Ext Fedora-WS-Live-32-1-6 2020-04-22-22-45-14-00 0 100% /run/initr
[liveuser@localhost-live mnt1]$
perryt
(perry tsacoumis)
December 5, 2020, 3:30pm
5
<pre>[liveuser@localhost-live mnt1]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 4.0
loop1 ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7
├─live-rw ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7 1G 86% /
└─live-base ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7
loop2
└─live-rw ext4 1.0 Anaconda 85f7fe5c-e901-4eda-b778-07e5c56483b7 1G 86% /
sda
├─sda1 vfat FAT16 8A18-7BB5 191.1M 4% /mnt
├─sda2
├─sda3 ntfs Windows 2CAEF147AEF10A5A
├─sda4 ntfs Windows RE tools 564EBE4A4EBE22A3
├─sda5 ntfs RECOVERY B2649FFB649FC111
├─sda6 ext4 1.0 06137cb7-c8a7-4156-8839-fd372c42121b
└─sda7 LVM2_memb LVM2 001 NiiWMH-aRIa-nhO5-TgJ7-LU7u-lipW-lyZDbc
├─fedora-swap
│ swap 1 5b8c3d81-8f09-4aaa-9604-277e20018558
├─fedora-root
│ ext4 1.0 7dc8cbc1-a5c9-43ef-8aae-09560e51bef4
└─fedora-home
ext4 1.0 04066381-5562-4ea0-9024-042a5529ec17
sdb
├─sdb1 vfat FAT16 8A18-7BB5 191.1M 4% /mnt1
├─sdb2
├─sdb3 ntfs Windows 2CAEF147AEF10A5A
├─sdb4 ntfs Windows RE tools 564EBE4A4EBE22A3
├─sdb5 ntfs RECOVERY B2649FFB649FC111
├─sdb6 ext4 1.0 06137cb7-c8a7-4156-8839-fd372c42121b
└─sdb7 LVM2_memb LVM2 001 NiiWMH-aRIa-nhO5-TgJ7-LU7u-lipW-lyZDbc
sr0 iso9660 Joliet Ext Fedora-WS-Live-32-1-6 2020-04-22-22-45-14-00 0 100% /run/initr
[liveuser@localhost-live mnt1]$
</pre>
lcts
(Christopher Engelhard)
December 5, 2020, 7:58pm
6
Hey, thanks & sorry for taking so long to reply.
So your sda7 is indeed part of a logical volume group (as it should be, this is the default for Fedora) and your actual root/home/swap filesystems are fedora-...
.
You’ll find them under /dev/mapper
, so the commands you’re looking for are
fsck /dev/mapper/fedora-home
to check the home filesystem and
mount /dev/mapper/fedora-home /mnt
to mount it to /mnt
.
perryt
(perry tsacoumis)
December 5, 2020, 11:18pm
7
[liveuser@localhost-live mnt1]$ sudo fsck /dev/mapper/fedora-home
fsck from util-linux 2.35.1
e2fsck 1.45.5 (07-Jan-2020)
/dev/mapper/fedora-home: clean, 1947832/46456832 files, 29529346/185809920 blocks
[liveuser@localhost-live mnt1]$ sudo mount /dev/mapper/fedora-home /mnt
[liveuser@localhost-live mnt1]$ sudo mke2fs -l badblocks.txt -n /dev/sda7
mke2fs 1.45.5 (07-Jan-2020)
/dev/sda7 contains a LVM2_member file system
Proceed anyway? (y,N) y
/dev/sda7 is apparently in use by the system; will not make a filesystem here!
[liveuser@localhost-live mnt1]$ sudo e2fsck -l badblocks.txt /dev/sda7
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda7 is in use.
e2fsck: Cannot continue, aborting.
[liveuser@localhost-live mnt1] umount /dev/mapper/fedora-home
umount: /mnt: must be superuser to unmount.
[liveuser@localhost-live mnt1] sudo umount /dev/mapper/fedora-home
[liveuser@localhost-live mnt1]$ sudo e2fsck -l badblocks.txt /dev/sda7
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda7 is in use.
e2fsck: Cannot continue, aborting.
???
lcts
(Christopher Engelhard)
December 6, 2020, 9:02am
8
You can’t make/test an ext filesystem on /dev/sda7
because it is not the partition the filesystem resides on. Basically, all your mke2fs/fsck/badblocks commands need to be run on /dev/mapper/fedora-home
and/or /dev/mapper/fedora-root
rather than /dev/sda7
.
Actually, both mke2fs/mkfs.ext4 and e2fsck/fsck can deal with invoking badblocks for you, so if you want to find & mark bad blocks on your existing filesystem, you can run
sudo fsck -vcck /dev/mapper/fedora-home
(this will keep your data intact).
If you want to create a new filesystem with bad blocks marked, you can run
sudo mkfs.ext4 -cc /dev/mapper/fedora-home
(this will destroy your data ).
Hope this helps.