Power outage and now missing drive

firex726 · 5. Mai 2021

Long story short, had a power outage and now one drive is is not mounted. Hoping that does not mean what I think it does. I'm still new to linux and hope there is just some magic command I'm not aware of.

I've highlighted the drive and filesystem in the below screenshots. The web interface gives the the option to create a new file system, but I'd like to just mount it where it was and not reformat it.

In SSH the drive is being detected but not the partition.

Code

$ ls dev/disk/by-id
ata-Hitachi_HUA722020ALA331_B9KXPSZF
ata-Hitachi_HUA722020ALA331_B9KXPSZF-part1
ata-Hitachi_HUA722020ALA331_BFH4R6NF
ata-Hitachi_HUA722020ALA331_BFH4R6NF-part1
ata-MD4000GSA6472E_WCC130854242
ata-SPCC_Solid_State_Disk_2B5007831E0B01069769
ata-SPCC_Solid_State_Disk_2B5007831E0B01069769-part1
ata-SPCC_Solid_State_Disk_2B5007831E0B01069769-part2
ata-SPCC_Solid_State_Disk_2B5007831E0B01069769-part5
ata-TOSHIBA_HDWD120_Y742NG0AS
ata-TOSHIBA_HDWD120_Y742NG0AS-part1
ata-TOSHIBA_HDWD120_Y75LD2JAS
ata-TOSHIBA_HDWD120_Y75LD2JAS-part1
ata-WDC_WD1600JS-55MHB1_WD-WCANM9087432
ata-WDC_WD1600JS-55MHB1_WD-WCANM9087432-part1
ata-WDC_WD1600JS-55MHB1_WD-WCANM9087432-part2
ata-WDC_WD1600JS-55MHB1_WD-WCANM9087432-part5
wwn-0x5000039fd1c13584
wwn-0x5000039fd1c13584-part1
wwn-0x5000039fe5f2a28b
wwn-0x5000039fe5f2a28b-part1
wwn-0x5000cca222f752a3
wwn-0x5000cca222f752a3-part1
wwn-0x5000cca229d03c61
wwn-0x5000cca229d03c61-part1
wwn-0x50014ee2b3608d7e

Alles anzeigen

gderf · 5. Mai 2021

Run fsck on the unmounted partition.

firex726 · 5. Mai 2021

No luck thus far:

Code

$ sudo fsck /dev/sde -l
fsck from util-linux 2.33.1
e2fsck 1.46.2 (28-Feb-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/sde

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>

$ sudo e2fsck -b 8193 /dev/sde
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sde

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>

$ sudo e2fsck -b 32768 /dev/sde
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Bad magic number in super-block while trying to open /dev/sde

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>

$ sudo e2fsck /dev/sde
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sde

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>

$ sudo e2fsck -p /dev/sde
e2fsck: Bad magic number in super-block while trying to open /dev/sde
/dev/sde:
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>

Alles anzeigen

gderf · 5. Mai 2021

You can not run fsck on a device, it must be run on a partition:

sudo fsck /dev/sde1

firex726 · 5. Mai 2021

Sadly looks like it's not detected...

$ sudo fsck /dev/sde1

[sudo] password for firex726:

fsck from util-linux 2.33.1

e2fsck 1.46.2 (28-Feb-2021)

fsck.ext2: No such file or directory while trying to open /dev/sde1

Possibly non-existent device?

$

gderf · 5. Mai 2021

List them all then decide which one you should be checking on. Make sure the disk power and data cables are all connected.

sudo fdisk -l | grep /dev

firex726 · 5. Mai 2021

Double checked the physical cables...

Code

$ sudo fdisk -l | grep /dev
[sudo] password for firex726:
Disk /dev/sdc: 149.1 GiB, 160041885696 bytes, 312581808 sectors
/dev/sdc1  *         2048 299839487 299837440  143G 83 Linux
/dev/sdc2       299841534 312580095  12738562  6.1G  5 Extended
/dev/sdc5       299841536 312580095  12738560  6.1G 82 Linux swap / Solaris
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdb1   2048 3907029134 3907027087  1.8T Linux filesystem
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda1   2048 3907029134 3907027087  1.8T Linux filesystem
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdd1   2048 3907029134 3907027087  1.8T Linux filesystem
Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdg: 119.2 GiB, 128035676160 bytes, 250069680 sectors
/dev/sdg1  *         2048 241702911 241700864 115.3G 83 Linux
/dev/sdg2       241704958 250068991   8364034     4G  5 Extended
/dev/sdg5       241704960 250068991   8364032     4G 82 Linux swap / Solaris
Disk /dev/sdf: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdf1   2048 3907029134 3907027087  1.8T Linux filesystem
$

Alles anzeigen

Power outage and now missing drive

Jetzt mitmachen!

Ähnliche Themen

Another missing RAID

RAID5 - OS crash & HDD replacement