Support Requests - CLICK TO READ BEFORE POSTING


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

External Hard Drive failing to mount
#1

System Specs
Operating System – Linux LiteLinux Lite 8.0
CPU / ProcessorIntel(R) N200
Memory (RAM)4 GB
StorageHard Drive (HDD)
Graphics (GPU)Intel UHD Graphics
Network deviceRealtek RTL8852BE PCIe 802.11ax Wireless Network Controller [1T1R]
My external hard drive is not mounting due to an error, "Failed to mount "Xbox Seagate Hard Drive". Error mounting /dev/sdb at /run/media/dj/Xbox Seagate Hard Drive: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error."

I tried on the latest antiX live boot too and it didnt mount there either.
it was able to mount the last time i used it on Linux Mint XFCE (yesterday)
it isnt showing up in File manager on Windows 11

i would appreciate if someone could help
Reply
#2

There can be interoperability problems with windows disks connected to Linux systems, however, with the limited information supplied, it may be that the disk has failed.  What is the make/model ?
Is the W11 system the one used to set the drive up originally ?
If not, try the external drive on whatever system you originally used to format it and see if it works there.

With the external disk connected to Linux Lite, open a terminal by pressing Ctrl, Alt and T together.
To get some information about how the system sees the disk, type or paste in the following commands followed by Enter.  Enter your password if asked.
Code:
sudo fdisk -l
Code:
lsblk -f
Post back the results.

stevef
clueless
Reply
#3

(07-12-2026, 09:41 PM)stevef Wrote:  There can be interoperability problems with windows disks connected to Linux systems, however, with the limited information supplied, it may be that the disk has failed.  What is the make/model ?
Is the W11 system the one used to set the drive up originally ?
If not, try the external drive on whatever system you originally used to format it and see if it works there.

With the external disk connected to Linux Lite, open a terminal by pressing Ctrl, Alt and T together.
To get some information about how the system sees the disk, type or paste in the following commands followed by Enter.  Enter your password if asked.
Code:
sudo fdisk -l
Code:
lsblk -f
Post back the results.

im sorry i dont know what W11 systems are, but this is a 2TB Seagate Xbox SSD 

when i tried sudo fdisk -l, i got this

Disk /dev/sda: 119.2 GiB, 127984992256 bytes, 31246336 sectors
Disk model: SDINFEO4-128G 
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 524288 bytes
Disklabel type: gpt
Disk identifier: B765787A-30CA-4AED-9AC0-7BEBEC4DEA3D

Device        Start      End  Sectors  Size Type
/dev/sda1      512  131583  131072  512M EFI System
/dev/sda2    131584 29235704 29104121  111G Linux filesystem
/dev/sda3  29235705 31246269  2010565  7.7G Linux swap


Disk /dev/sdb: 3.64 TiB, 4000787029504 bytes, 7814037167 sectors
Disk model: Game Drive Xbox
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: 09827DB7-80D5-42A4-8849-4EBCDA7D73E4

Device    Start  End Sectors Size Type
/dev/sdb1    34 32767  32734  16M Microsoft reserved

Partition 1 does not start on physical sector boundary.


when i tried lsblk -r, i got this 

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 119.2G 0 disk
sda1 8:1 0 512M 0 part /boot/efi
sda2 8:2 0 111G 0 part /
sda3 8:3 0 7.7G 0 part [SWAP]
sdb 8:16 0 3.6T 0 disk
sdb1 8:17 0 16M 0 part
zram0 252:0 0 0B 0 disk


i tried using it on Xbox just now (the device the hard drive was formatted on) and it didnt get recognized

thank you
Reply
#4

Quote:im sorry i dont know what W11 systems are, but this is a 2TB Seagate Xbox SSD
W11 is short for windows 11.

Your Linux Lite set up sees the Seagate drive (sdb) and reports it is 3.6TiB (aka 4TB) overall capacity.

A disk is usually sub-divided into partitions for different uses.  Your set up only reports one partition on the disk - sdb1 which is a small (16MB) MS reserved partition. Linux should ignore this.

For Linux to use the disk, it would need to see other partitions (sdb2 etc) which it might be able to use.  Seeing only sdb1 (the 16M MS partition) implies a problem with the partition table.

Have you changed anything significant since the drive last worked ?

Quote:i tried using it on Xbox just now (the device the hard drive was formatted on) and it didnt get recognized

Unless you've deliberately changed something significant since first using it, the fact that it fails on the 'original' system is not a good sign. I don't know anything about Xbox or what diagnostic capability it has but if it reports an error it may be more specific than the catch-all error message we get from Linux.

It's hard to give further advice without knowing more about what you use the disk for and how important any data on it may be.

stevef
clueless
Reply
#5

(07-13-2026, 06:32 AM)stevef Wrote:  
Quote:im sorry i dont know what W11 systems are, but this is a 2TB Seagate Xbox SSD
W11 is short for windows 11.

Your Linux Lite set up sees the Seagate drive (sdb) and reports it is 3.6TiB (aka 4TB) overall capacity.

A disk is usually sub-divided into partitions for different uses.  Your set up only reports one partition on the disk - sdb1 which is a small (16MB) MS reserved partition. Linux should ignore this.

For Linux to use the disk, it would need to see other partitions (sdb2 etc) which it might be able to use.  Seeing only sdb1 (the 16M MS partition) implies a problem with the partition table.

Have you changed anything significant since the drive last worked ?

Quote:i tried using it on Xbox just now (the device the hard drive was formatted on) and it didnt get recognized

Unless you've deliberately changed something significant since first using it, the fact that it fails on the 'original' system is not a good sign. I don't know anything about Xbox or what diagnostic capability it has but if it reports an error it may be more specific than the catch-all error message we get from Linux.

It's hard to give further advice without knowing more about what you use the disk for and how important any data on it may be.

i dont remember significantly changing the drive itself before getting on Windows 

this all started happening after i started using antiX live boot.  
i think it was the same error as on Linux Lite (the wrong fs type, bad superblock, etc) 
Before that it worked as usual on Linux Mint XFCE.

later on i plugged into Windows i tried changing it back from GPT to MBR then back to GPT because at that point nothing was working so i was just trying stuff  

that was probably a bad idea but i havent been able to see the results yet

I believe there wasnt any recent physical damage to it ether so when it happened i thought it was just antiX failing to see the drive for some reason

on Xbox it didn't recognize the drive, as if it wasnt plugged in at all.

i have important data on the disk like old Photos, Backups, Music, Drumkits, and Recovery stuff so i havent tried formatting it yet
Reply
#6

From what you revealed so far the problem appears to be with the partition table.
1dj Wrote:this all started happening after i started using antiX live boot.
I don't know anything about antix or what it does but just connecting a drive to a system using a legitimate OS should not do anything adverse.

1dj Wrote:i have important data on the disk
Any back ups ?

If the data is valuable and is only on the drive, consider contacting a data recovery specialist.  If it is possible to recreate the xbox partitioning, it may be that some of the files are still intact.
If recovery is intended, don't try anything more as it may reduce the chances of success.

Out of interest, what is the exact model of the drive ?

Good luck.

stevef
clueless
Reply
#7

(07-13-2026, 03:18 PM)stevef Wrote:  From what you revealed so far the problem appears to be with the partition table.
1dj Wrote:this all started happening after i started using antiX live boot.
I don't know anything about antix or what it does but just connecting a drive to a system using a legitimate OS should not do anything adverse.

1dj Wrote:i have important data on the disk
Any back ups ?

If the data is valuable and is only on the drive, consider contacting a data recovery specialist.  If it is possible to recreate the xbox partitioning, it may be that some of the files are still intact.
If recovery is intended, don't try anything more as it may reduce the chances of success.

Out of interest, what is the exact model of the drive ?

Good luck.

its Game Drive for Xbox 2TB Model No: STKX2000400

thank you for the Help  Big Grin
do you think formatting the disk would make it usable again? in case i decided the data wasnt worth it
Reply
#8

1dj Wrote:its Game Drive for Xbox 2TB Model No: STKX2000400
How old is the drive ?
In the UK that model has 2 year warranty and '3 years of rescue data recovery services' included.

If your kit is not covered by the manufacturer support in your area and professional data recovery is not an option then it may be worth looking at the Seagate support pages.
This is the UK product page, your area may be different.
https://www.seagate.com/gb/en/support/ga...ame-drive/

1dj Wrote:do you think formatting the disk would make it usable again? in case i decided the data wasnt worth it
Without knowing why it stopped working, no one can predict for sure if the disk can be used again.
If it was mine and I didn't care about the data, I would try to see if it could be fixed just for the learning but I might not trust the drive too much afterwards.

1dj Wrote:thank you for the Help
Not sure I've helped much, but you're welcome

stevef
clueless
Reply
#9

In addition to all the good advice Steve has given you might want to look at the tool gsmartcontrol. That takes away much of the guesswork regarding disk health.

And, if "i tried changing it back from GPT to MBR then back to GPT" indicates that you indeed created a new partition table, then there is no surprise you can't see anything anymore. Like Steve said, it would be worth a try to recreate exactly the original partition table - if you have written down the info somewhere, like the output of fdsik -l.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)