running fsck gives this:
sudo fsck /dev/sda1
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
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/sda1

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>
 


Can you give us the output from (lines with a hash are comments only, not commands)

Code:
sudo fdisk -l

# that's an l for list
 
Can you give us the output from (lines with a hash are comments only, not commands)
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: HGST HTS725050A7
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: gpt
Disk identifier: 0D93ADCC-5087-458E-AB55-8C93270577EB

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 1054719 1050624 513M EFI System
/dev/sda3 1054720 206723071 205668352 98.1G Linux filesystem
/dev/sda4 206723072 452485119 245762048 117.2G Microsoft basic data
/dev/sda5 452485120 800645119 348160000 166G Microsoft basic data
/dev/sda6 800645120 976773119 176128000 84G Microsoft basic data
 
Well that all looks OK.

The bad magic number and invalid superblock references above are because you were trying to run fsck on a partition which is not EXT formatted.

Is everything else working OK?
 
Is everything else working OK?
Off and on. By now I had to reboot twice, with the same problem coming up, ie. the drives turn 'read-only' and block any copying or downloading. Earlier this was not affecting USB drives. But since yesterday that too has started. Is there any other app other than Smartctl to check the hard drive?
 
Beyond my paygrade, I am afraid.

Someone else may have the information.

Hope it works out for you.
 
Running badblocks gave this ouput:
Checking blocks 0 to 488386583
Checking for bad blocks (read-only test): 0.00% done, 0:00 elapsed. (0/0/0 errdone
Pass completed, 0 bad blocks found. (0/0/0 errors)
 


Latest posts

Top