Wrong fs type, bad option, bad superblock on a harddisk missing codepage or helper program, or other error

Ota-Coder · 01-23-2021, 04:16 PM

I'm on KDE Manjaro and I'm getting this error suddenly on my 4TB external harddisk whenever trying to mount in Dolphin.

Code:

An error occurred while accessing 'Akari', the system responded: The requested operation has failed: Error mounting /dev/sdg1 at /run/media/daaishi/Akari1: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error

I don't really remember what fs type it is but I'm sure it was either ntfs or btrfs, one or the other.

It used to work the other day when I backed up some of my files.

Suddenly, it doesn't let me mount the harddisk.

Checking KDE Partition Manager and GParted, it still has more than 1TB of free space and it is in BTRFS.

Am I screwed?

Searching around, I don't want to try using mkfs because it would erase the data it has.

I tried using these commands and gave me the same error:

Code:

[daaishi@ayumin ~]$ sudo mount -t btrfs /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[daaishi@ayumin ~]$ sudo mount -t auto /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.

When I tried using NTFS:

Code:

[daaishi@ayumin ~]$ sudo mount -t ntfs /dev/sdg1 /run/media/daaishi/Akari
NTFS signature is missing.
Failed to mount '/dev/sdg1': Invalid argument
The device '/dev/sdg1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Is there anything I can do to still be able to get my data or better yet, let it be mounted and be used again?

I tried now fsck:

Code:

[daaishi@ayumin ~]$ sudo fsck /dev/sdg1
fsck from util-linux 2.36.1
If you wish to check the consistency of a BTRFS filesystem or
repair a damaged filesystem, see btrfs(8) subcommand 'check'.

Any help would be appreciated. Thank you.

michaelk · 01-23-2021, 06:14 PM

The output of the lsblk command will show you the filesystem type. Post the output of

lsblk -f

Ota-Coder · 01-23-2021, 06:43 PM

Thanks michaelk for responding!

Code:

[daaishi@ayumin ~]$ lsblk -f
NAME   FSTYPE   FSVER LABEL   UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/core/10577
loop1  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/freecad/16
loop2  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/gnome-3-28-1804/
loop3  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/plexmediaserver/
loop4  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/plexmediaserver/
loop5  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/gtk-common-theme
loop6  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/core18/1932
loop7  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/freecad/19
loop8  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/core/10583
loop9  squashfs 4.0                                                      0   100% /var/lib/snapd/snap/gtk-common-theme
loop10 squashfs 4.0                                                      0   100% /var/lib/snapd/snap/gnome-3-28-1804/
loop11 squashfs 4.0                                                      0   100% /var/lib/snapd/snap/core18/1944
sda                                                                               
├─sda1 btrfs                  653c7d91-a061-40ba-9c64-e4fd20a57d39   96.9G    50% /run/timeshift/backup
├─sda2 btrfs                  d14b9564-e139-44a4-885c-c20876218324   98.1G    97% /home
└─sda3 vfat     FAT32         A025-47FB                             510.4M     0% /boot/efi
sdb                                                                               
└─sdb1 btrfs          Daaishi 81ec711c-b912-4acf-9059-fd56a93b8a00  136.5G    96% /mnt/Daaishi
sdc                                                                               
└─sdc1 btrfs          Daachan 0d80ec0a-ee4b-4df3-b1ab-02d9039ff144   37.8G    98% /mnt/Daachan
sdd                                                                               
└─sdd1 btrfs          Ayumin  b1e39ec5-e8fc-40c7-9d41-2a673e05e7d0  131.6G    95% /mnt/Ayumin
sde                                                                               
└─sde1 btrfs          Darling 4776e238-021c-48fb-bc47-4a5b0de4000c  698.8G    25% /mnt/Darling
sdf                                                                               
└─sdf1 btrfs          Ayuyu   fb414eb5-098c-41b4-ae43-a5d94db118f8    1.6T    13% /mnt/Ayuyu
sdg                                                                               
└─sdg1 btrfs          Akari   9906e5f8-9a9d-49d3-8a6c-3f4576153a1c                
[daaishi@ayumin ~]$

Looks like it is btrfs. Now what gives that it doesn't allow me to mount it?

michaelk · 01-23-2021, 07:58 PM

My knowledge of btrfs is limited...

My only suggestion is to follow the guides for checking a filesystem.

https://btrfs.wiki.kernel.org/index.php/Btrfsck

Ota-Coder · 01-23-2021, 09:21 PM

Sadly, no joy still. Oh no!

Code:

[daaishi@ayumin ~]$ sudo mount -o recovery,ro /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[daaishi@ayumin ~]$ sudo mount -o recovery /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[daaishi@ayumin ~]$ sudo mount -o ro /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[daaishi@ayumin ~]$ sudo btrfs check --repair /dev/sdg1
enabling repair mode
WARNING:

	Do not use --repair unless you are advised to do so by a developer
	or an experienced user, and then only after having accepted that no
	fsck can successfully repair all types of filesystem corruption. Eg.
	some software or hardware bugs can fatally damage a volume.
	The operation will start in 10 seconds.
	Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
bad tree block 1971159416832, bytenr mismatch, want=1971159416832, have=0
ERROR: failed to read block groups: Input/output error
ERROR: cannot open file system
[daaishi@ayumin ~]$

Edit: Should've used btrfs rescue chunk-recover first before btrfs check. Oh no!

Code:

[ayumin daaishi]# btrfs rescue chunk-recover /dev/sdg1
Scanning: DONE in dev0                    
Check chunks successfully with no orphans
Chunk tree recovered successfully
[ayumin daaishi]# btrfs rescue super-recover /dev/sdg1
All supers are valid, no need to recover
[ayumin daaishi]# mount -o recovery /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[ayumin daaishi]# mount -o ro /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[ayumin daaishi]# mount -o recovery,ro /dev/sdg1 /run/media/daaishi/Akari
mount: /run/media/daaishi/Akari: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error.
[ayumin daaishi]# sudo btrfs fi show /dev/sdg1
[sudo] password for daaishi: 
Label: 'Akari'  uuid: 9906e5f8-9a9d-49d3-8a6c-3f4576153a1c
	Total devices 1 FS bytes used 2.01TiB
	devid    1 size 3.64TiB used 2.09TiB path /dev/sdg1

dmesg -w output when running 'mount -o usebackuproot /dev/sdg1 /run/media/daaishi/Akari/'

Code:

[36378.660377] BTRFS warning (device sdg1): 'usebackuproot' is deprecated, use 'rescue=usebackuproot' instead
[36378.660379] BTRFS info (device sdg1): trying to use backup root at mount time
[36378.660380] BTRFS info (device sdg1): disk space caching is enabled
[36378.660380] BTRFS info (device sdg1): has skinny extents
[36382.937004] sd 6:0:0:0: [sdg] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=4s
[36382.937006] sd 6:0:0:0: [sdg] tag#0 Sense Key : Medium Error [current] 
[36382.937007] sd 6:0:0:0: [sdg] tag#0 Add. Sense: Unrecovered read error
[36382.937009] sd 6:0:0:0: [sdg] tag#0 CDB: Read(16) 88 00 00 00 00 00 e3 99 68 e0 00 00 00 20 00 00
[36382.937011] blk_update_request: critical medium error, dev sdg, sector 3818481888 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0
[36386.539698] sd 6:0:0:0: [sdg] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
[36386.539701] sd 6:0:0:0: [sdg] tag#0 Sense Key : Medium Error [current] 
[36386.539702] sd 6:0:0:0: [sdg] tag#0 Add. Sense: Unrecovered read error
[36386.539704] sd 6:0:0:0: [sdg] tag#0 CDB: Read(16) 88 00 00 00 00 00 e3 b9 68 e0 00 00 00 20 00 00
[36386.539705] blk_update_request: critical medium error, dev sdg, sector 3820579040 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0
[36386.539745] BTRFS error (device sdg1): failed to read block groups: -5
[36386.542858] BTRFS error (device sdg1): open_ctree failed

In case somebody finds this, these links might help:
- https://ownyourbits.com/2019/03/03/h...rfs-partition/
- https://unix.stackexchange.com/quest...-bad-key-order
- https://bbs.archlinux.org/viewtopic.php?id=236385

As of writing, I can't use btrfs restore because I don't have that big of free space and hopeful still I would recover data

lvm_ · 01-24-2021, 04:01 AM

Quote:

Originally Posted by Ota-Coder

Code:

[36382.937006] sd 6:0:0:0: [sdg] tag#0 Sense Key : Medium Error [current] 
[36382.937007] sd 6:0:0:0: [sdg] tag#0 Add. Sense: Unrecovered read error
[36382.937009] sd 6:0:0:0: [sdg] tag#0 CDB: Read(16) 88 00 00 00 00 00 e3 99 68 e0 00 00 00 20 00 00
[36382.937011] blk_update_request: critical medium error, dev sdg, sector 3818481888 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0
[36386.539698] sd 6:0:0:0: [sdg] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
[36386.539701] sd 6:0:0:0: [sdg] tag#0 Sense Key : Medium Error [current] 
[36386.539702] sd 6:0:0:0: [sdg] tag#0 Add. Sense: Unrecovered read error
[36386.539704] sd 6:0:0:0: [sdg] tag#0 CDB: Read(16) 88 00 00 00 00 00 e3 b9 68 e0 00 00 00 20 00 00
[36386.539705] blk_update_request: critical medium error, dev sdg, sector 3820579040 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0
[36386.539745] BTRFS error (device sdg1): failed to read block groups: -5
[36386.542858] BTRFS error (device sdg1): open_ctree failed

Looks like your disk has failed - hardware issue. Check SMART status to make sure: 'smartctl -a /dev/sdg'

Ota-Coder · 01-29-2021, 03:24 PM

Sorry for the late response. Oh no T_T

Code:

[daaishi@ayumin ~]$ sudo smartctl -a /dev/sdg
[sudo] password for daaishi: 
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.7-3-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Elements / My Passport (USB, AF)
Device Model:     WDC WD40NMZW-11GX6S1
Serial Number:    WD-WX21D86A6FVX
LU WWN Device Id: 5 0014ee 6b201966a
Firmware Version: 01.01A01
User Capacity:    4,000,753,472,000 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jan 30 05:23:21 2021 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 2684) seconds.
Offline data collection
capabilities: 			 (0x1b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  22) minutes.
SCT capabilities: 	       (0x30b5)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   198   198   051    Pre-fail  Always       -       230
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       5150
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
194 Temperature_Celsius     0x0022   127   095   000    Old_age   Always       -       25

SMART Error Log Version: 1
ATA Error Count: 1
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 2542 hours (105 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 41 d6 53 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d6 01 98 4f c2 00 00      00:00:10.111  SMART WRITE LOG
  b0 d5 01 80 4f c2 00 00      00:00:10.092  SMART READ LOG
  ec 90 01 00 00 00 00 00      00:00:10.091  IDENTIFY DEVICE
  ec 90 06 30 a5 fb 00 00      00:00:10.090  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

[daaishi@ayumin ~]$