Stuck at busybox, fsck also not working

When i try fsck, it returns ‘sh: fsck: not found’
enter image description here

2TB USB drive not showing in diskutil, fsck not running, not showing in Finder

I recently purchased a 2TB USB drive and loaded a few files onto it after formatting it to FAT32 so I could use it on my TV.

I accidentally unplugged it without unmounting/ejecting it first and ever since I have been unable to view it in Finder.

I’ve also tried looking for it with diskutil but it does not show. Also, I have checked for fsck and it is not running on my system. Similarly, the disk does not show in Disk Utility.

I’ve tried plugging it into two separate TVs but it is not recognised on either.

What are my options to try and resuscitate this drive?

diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         121.1 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +121.1 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD — Data     101.7 GB   disk1s1
   2:                APFS Volume Preboot                 81.1 MB    disk1s2
   3:                APFS Volume Recovery                528.7 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.4 GB    disk1s5

macos – Macbook Air system fails and fsck does not work

My macbook air 13 (mid 2013) cannot boot correctly. It stops at the Apple logo loading screen.
After getting into the single user mode, here is the error I got by runningfsck -fy (didn’t find any information about the error code):
enter image description here

After running the command mount -uw /, I got this and the process just hangs there:enter image description here

I think because of some failed system files or potentially damaged hard drive, the system cannot boot or mount the main drive (macintosh HD). I also tried to re-install the OS in the recover mode and it was just stuck during the initial process (seems related to the mounting problem). I also used the diskutil repairVolume command, but the process went on for 10 hours without any results (guess it’s also stuck).
Any ideas about how to solve this problem? Is there a way to force formating the main drive without mounting it?

Trying to run fsck but not able to write in english language by default?

While typing fsck -f dev/sda2 the default input language is some other language. How I can change it?

fsck disk cannot run due to “Bad magic number in super-block”

fsck disk cannot run due to “Bad magic number in super-block”
Disk is an external one (WD passport HDD), connected through usb port.
It is mounted normally.
I can write / delete / play / run files normally (except in a particular directory).

I would like to run fsck that may fix that problem. However, i confronted that problem.

Using sudo e2fsck /dev/sdc, with different numbers didnt work.

What to do?

“sudo fsck /dev/sdc”

elias@eliasc:/home$ sudo fsck /dev/sdc
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Found a gpt partition table in /dev/sdc

sudo fdisk -l

  Disk /dev/sdc: 931.5 GiB, 1000170586112 bytes, 1953458176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 66BAEFE2-F3F9-491C-B40F-C964F28AE483

Device     Start        End    Sectors   Size Type
/dev/sdc1   2048 1953456127 1953454080 931.5G Microsoft basic data

hard drive – fsck, im stuck in the middle of operation

my hdd is slow as hell, i got a RV420 computer, and running latest mint distro, never used linux before (moved from windows 6 month ago) I realized my disk have errors, so i mounted an ubuntu studio 20.04 on a pendrive, because i plan to move to that later, and im trying to use as startup disk for repairing my normal hdd with the fsck, so now im running from a pendrive on ubuntu studio.

first make a list of devices …ok

ubuntu-studio@ubuntu-studio:~$ sudo df
Filesystem                  1K-blocks    Used Available Use% Mounted on
udev                          1405932       0   1405932   0% /dev
tmpfs                          290760    8832    281928   4% /run
/dev/sdb1                     3506176 3506176         0 100% /cdrom
/dev/loop0                    3373056 3373056         0 100% /rofs
/cow                          1453792  110556   1343236   8% /
/dev/disk/by-label/writable  11400384   41452  10760100   1% /var/log
tmpfs                         1453792   61276   1392516   5% /dev/shm
tmpfs                            5120       4      5116   1% /run/lock
tmpfs                         1453792       0   1453792   0% /sys/fs/cgroup
tmpfs                         1453792     556   1453236   1% /tmp
tmpfs                          290756      16    290740   1% /run/user/999

then i make another list

*ubuntu-studio@ubuntu-studio:~$ sudo fdisk -l
Disk /dev/loop0: 3.22 GiB, 3453935616 bytes, 6745968 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 596.18 GiB, 640135028736 bytes, 1250263728 sectors
Disk model: SAMSUNG HM641JI 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2abb65ff

Device     Boot Start        End    Sectors   Size Id Type
/dev/sda1  *     2048 1250263039 1250260992 596.2G 8e Linux LVM




Disk /dev/mapper/mint--vg-root: 595.19 GiB, 639073517568 bytes, 1248190464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/mint--vg-swap_1: 976 MiB, 1023410176 bytes, 1998848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 14.46 GiB, 15518924800 bytes, 30310400 sectors
Disk model: USB Flash Drive 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x56ab3f90

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sdb1  *          0  7012351  7012352  3.4G  0 Empty
/dev/sdb2       6965784  6973719     7936  3.9M ef EFI (FAT-12/16/32)
/dev/sdb3       7012352 30310399 23298048 11.1G 83 Linux*

i guess the drive i want to repair is dev/sda1 so i ask

ubuntu-studio@ubuntu-studio:~$ sudo fsck -C /dev/sda
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.

but if i try to unmount the device…

ubuntu-studio@ubuntu-studio:~$ sudo umount /dev/sda
umount: /dev/sda: not mounted.
ubuntu-studio@ubuntu-studio:~$ sudo umount /dev/sda1
umount: /dev/sda1: not mounted.
ubuntu-studio@ubuntu-studio:~$ 

and can-t go on from there, dont know if im spelling something wrong or i need to boot somewhere else or what, please help ii want to learn this. i reached this far with a video tutorial but i need some help. Thanks in advance.

SYSTEM INFO>
Window Manager (xfwm4)
Panel (xfce4-panel)
Desktop Manager (xfdesktop)
File Manager (thunar)
Volume manager (thunar-volman)
Session Manager (xfce4-session)
Setting System (xfce4-settings)
Application Finder (xfce4-appfinder)
Settings Daemon (xfconf)
A menu library (garcon)
Thumbnails service (tumbler)

linux: why do disk errors appear in dmesg output even though fsck has not been run?

I have an 8TiB disk connected via UBS3 and formatted in 3 EXT3 partitions that I use as a backup drive (it is plugged into a SATA base).

The disk has been connected and mounted for several days without being explicitly written to it (I backed up some data a couple of days ago).

I took a look at dmesg and saw the following (this is filtered to show only the entries that match the disk name, sdg):

(393945.628890) EXT4-fs (sdg2): error count since last fsck: 4
(393945.628894) EXT4-fs (sdg2): initial error at time 1589268773: ext4_validate_block_bitmap:406
(393945.628897) EXT4-fs (sdg2): last error at time 1589336019: ext4_validate_block_bitmap:406
(394076.698059) EXT4-fs (sdg1): error count since last fsck: 103
(394076.698063) EXT4-fs (sdg1): initial error at time 1589216157: ext4_validate_block_bitmap:406
(394076.698066) EXT4-fs (sdg1): last error at time 1589372294: ext4_lookup:1590: inode 186081476

I have not run fsck on this disk as it was partitioned and formatted. Since fsck has not run, what are you finding errors and how worried should you be?

When I rebooted the system this morning I checked dmesg again and found (again filtered to show only the entries that match sdg)

(  261.721822) sd 9:0:0:0: (sdg) Spinning up disk...
(  274.051062) sd 9:0:0:0: (sdg) 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
(  274.051065) sd 9:0:0:0: (sdg) 4096-byte physical blocks
(  274.051137) sd 9:0:0:0: (sdg) Write Protect is off
(  274.051140) sd 9:0:0:0: (sdg) Mode Sense: 43 00 00 00
(  274.051297) sd 9:0:0:0: (sdg) Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
(  274.051498) sd 9:0:0:0: (sdg) Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
(  274.134309)  sdg: sdg1 sdg2 sdg3
(  274.135296) sd 9:0:0:0: (sdg) Attached SCSI disk
(  274.654835) EXT4-fs (sdg3): mounting ext3 file system using the ext4 subsystem
(  274.696860) EXT4-fs (sdg3): warning: mounting fs with errors, running e2fsck is recommended
(  274.766709) EXT4-fs (sdg1): mounting ext3 file system using the ext4 subsystem
(  274.795109) EXT4-fs (sdg1): warning: mounting fs with errors, running e2fsck is recommended
(  274.825210) EXT4-fs (sdg2): mounting ext3 file system using the ext4 subsystem
(  274.891191) EXT4-fs (sdg2): warning: mounting fs with errors, running e2fsck is recommended
(  275.713323) EXT4-fs (sdg2): mounted filesystem with ordered data mode. Opts: (null)
(  276.460528) EXT4-fs (sdg3): mounted filesystem with ordered data mode. Opts: (null)
(  276.499085) EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: (null)
(  578.549827) EXT4-fs (sdg1): error count since last fsck: 103
(  578.549830) EXT4-fs (sdg1): initial error at time 1589216157: ext4_validate_block_bitmap:406
(  578.549832) EXT4-fs (sdg1): last error at time 1589372294: ext4_lookup:1590: inode 186081476
(  578.549836) EXT4-fs (sdg3): error count since last fsck: 47
(  578.549837) EXT4-fs (sdg3): initial error at time 1589268525: htree_dirblock_to_tree:1022: inode 31604737: block 126419458
(  578.549840) EXT4-fs (sdg3): last error at time 1589380312: ext4_lookup:1594: inode 33701921
(  578.549844) EXT4-fs (sdg2): error count since last fsck: 4
(  578.549845) EXT4-fs (sdg2): initial error at time 1589268773: ext4_validate_block_bitmap:406
(  578.549847) EXT4-fs (sdg2): last error at time 1589336019: ext4_validate_block_bitmap:406
(  639.938843) EXT4-fs (sdg1): mounting ext3 file system using the ext4 subsystem
(  640.950738) EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: (null)
(  650.900006) EXT4-fs (sdg2): mounting ext3 file system using the ext4 subsystem
(  651.207658) EXT4-fs (sdg2): mounted filesystem with ordered data mode. Opts: (null)
(  658.836040) EXT4-fs (sdg3): mounting ext3 file system using the ext4 subsystem
(  659.084558) EXT4-fs (sdg3): mounted filesystem with ordered data mode. Opts: (null)

Therefore, the system knows that there are errors and has still mounted the disk without displaying any other warnings other than the entries in dmesg.

About 30 minutes later I checked again because I was curious and found out:

(  955.353027) EXT4-fs (sdg2): error count since last fsck: 3248
(  955.353031) EXT4-fs (sdg2): initial error at time 1589268773: ext4_validate_block_bitmap:406
(  955.353033) EXT4-fs (sdg2): last error at time 1589437923: ext4_map_blocks:604: inode 103686210: block 1947002998
(  955.353039) EXT4-fs (sdg1): error count since last fsck: 103
(  955.353040) EXT4-fs (sdg1): initial error at time 1589216157: ext4_validate_block_bitmap:406
(  955.353042) EXT4-fs (sdg1): last error at time 1589372294: ext4_lookup:1590: inode 186081476
(  956.751484) EXT4-fs error (device sdg2): ext4_map_blocks:604: inode #103686210: block 1947002998: comm updatedb.mlocat: lblock 12 mapped to illegal pblock 1947002998 (length 1)
(  956.767496) EXT4-fs error (device sdg2): ext4_map_blocks:604: inode #103686210: block 1947002998: comm updatedb.mlocat: lblock 12 mapped to illegal pblock 1947002998 (length 1)
(  956.782683) EXT4-fs warning (device sdg2): htree_dirblock_to_tree:994: inode #103686210: lblock 12: comm updatedb.mlocat: error -117 reading directory block

Eeek! The error count has increased for sdg2!

Again, I haven't explicitly written to disk all this time.

Before partitioning and formatting the drive with gparted, I used fsck to run an incorrect block scan (took several days) and no errors were found. This is also a new album. For this reason, I am reasonably sure that the hardware is good.

What is possibly happening here? How concerned should you be about the integrity of the file systems on this disk? What should my next steps be?

Linux: FSCK unmount and run problem

A / dev / sdb partition on the web my server has failed the FSCK check but I can't seem to find a way to repair it. The operating system is CentOS 6.8.

In / etc / fstab, I have commented on this partition.

I used the umount / dev / sdb command and it came back saying it is not mounted.

Also, I tried

root@server3 (/)# umount /dev/sdb1
umount: /dev/sdb1: not mounted

root@server3 (/)# fsck -A /dev/sdb1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/sda5 is mounted.
e2fsck: Cannot continue, aborting.

The file system is currently configured as:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda5       221G  156G   55G  75% /
tmpfs            16G     0   16G   0% /dev/shm
/dev/sda1       504M   66M  413M  14% /boot
/dev/sda3       4.0G  139M  3.7G   4% /tmp
/dev/sdb2       219G   66G  142G  32% /wjgbk

The FSTAB file looks like this:

#
# /etc/fstab
# Created by anaconda on Fri Oct 11 07:42:05 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=8fec8cf7-4999-489c-a344-8b16ab7402e2       /       ext4    usrjquota=quota.user,jqfmt=vfsv0        1       1
UUID=7f2583f8-7d07-43a9-9f81-0f24a449e97a /boot                   ext4    defaults        1 2
#UUID=793f6375-bd81-4392-9cf7-adff4149b72c      /home2  ext4    usrjquota=quota.user,jqfmt=vfsv0        1       2
UUID=2e71e9e4-a05a-4282-9e48-a82a364ef3e8 /tmp                    ext4    defaults        1 2
UUID=7e4202fe-c53a-4475-bfb8-66271e08137f       /wjgbk  ext4    defaults        1       2
UUID=67f4cccf-fca2-46b8-8f4c-53af3512b7af swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/tmp             /var/tmp                    ext3    defaults,bind,noauto        0 0

And UIDs refer to the following:

root@server3 (/dev)# blkid
/dev/sdb1: UUID="793f6375-bd81-4392-9cf7-adff4149b72c" TYPE="ext4"
/dev/sdb2: UUID="7e4202fe-c53a-4475-bfb8-66271e08137f" TYPE="ext4"
/dev/sda1: UUID="7f2583f8-7d07-43a9-9f81-0f24a449e97a" TYPE="ext4"
/dev/sda2: UUID="67f4cccf-fca2-46b8-8f4c-53af3512b7af" TYPE="swap"
/dev/sda3: UUID="2e71e9e4-a05a-4282-9e48-a82a364ef3e8" TYPE="ext4"
/dev/sda5: UUID="8fec8cf7-4999-489c-a344-8b16ab7402e2" TYPE="ext4"

Any ideas on how to proceed with FSCK verification? I need to recover the data from this partition and move it to a new server as soon as possible.

Linux Mint System won't boot :( Fsck clean – Any suggestions?

I just made some changes to my PC that now won't boot. I am trying to install a new graphics card, so I installed a RAM upgrade and also connected a new hard drive, which is not related to my Linux build (it is used to run Windows configuration which my brother uses on the same computer ).

My system is running a 1TB primary disk, the above mentioned 250GB Windows disk and a 250GB mounted drive that I set up a while back. Being new to these things, I think I managed to mount the additional disk incorrectly since the next time I booted I was put into recovery mode and rescued by some utility that helped me fix the errors. Sorry, I don't remember the name. or details of this, but I thought it might be important.

Now, I made all the changes listed above, and for a while left me in recovery mode, now only a blinking cursor appears. Following some online advice, I started Mint from a live USB and ran fsck on both drives, which were clean again, so I'm a bit stuck on what to do next. Any suggestion?

Final info: I think the drives were configured incorrectly because my 1TB main drive is listed as / dev / sdb1, while the 250GB drive is in / dev / sda. I think this was probably the reason why when I rebooted a while ago I had to fix these errors: was I trying to start / dev / sda by default? Just a thought …

Any ideas would be highly appreciated, regards.

fsck does not run on ubuntu 18 lts. mistakes no matter what I tried

I want to fsck the 249G volume, because this hard drive has trouble booting. , hoping he can help repair the disk so it can start again. It's my ubuntu boot disk.

[error when clicking with nautilus] [1] [1]: https://i.stack.imgur.com/lDZpD.png

[result of the mounted device "df"] [1] [1]: https://i.stack.imgur.com/41ExG.png
It shows that my sda hard drive is not mounted.

["lsblk result] [1] [1]: https://i.stack.imgur.com/o2Up1.png

Sda is the hard drive where I ran ubuntu, but it has a problem, I think even the computer can't read it …
The hard drive and its contents are fine. I used "diskinternals linux reader and active disk editor" and I was able to navigate through all the subfolders and data on a Windows computer.

[fsck error] [1] [1]: https://i.stack.imgur.com/snBlg.png
How can you use my sda? Seeing that it is not even mounted!

Can anybody help me?

Thank you
Andrew