More disk mounting problems.....

khedger

Member
Credits
494
Hi all,
Another problem I"m having. Again I have a server with 3 SDDs.
I have a 1tb SDD partitioned with a single partition and installed Ubuntu to successfully.
I have second 500 gb SDD with a single partition that I entered a problem for earlier, but I can mount it.
I have a third 1tb SDD that I've partitioned with a single partition and then 3 partitions. With either scheme
I'm having the same problem. I made three mountpoints (a single mount point for the single partition try) and when
I try to mount the partitions (either full disk or one of three), I get the same error:
Code:
ount: /jupiter: wrong fs type, bad option, bad superblock on /dev/sdc2, missing codepage or helper program, or other error.
Just for info's sake, this is the fdisk output for one of the partitions:
Code:
Command (m for help): p
Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000MX500SSD1
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: dos
Disk identifier: 0xd5e35e20

Device     Boot      Start        End   Sectors  Size Id Type
/dev/sdc1             2048  524290047 524288000  250G 83 Linux
/dev/sdc2        524290048 1048578047 524288000  250G 83 Linux
/dev/sdc3       1048578048 1572866047 524288000  250G 83 Linux
Again, I'm at a loss here, everything seems to work fine except the mount.
So what have I screwed up?

keith
 


furtom

New Member
Credits
69
Try running fsck to see if the error message actually means what it says. Stranger things have happened. ;)

Lol. I don't mean to be a jerk. I've myself tried everything under the sun except the obvious. Many times. Since you didn't say you checked the fs, I thought I'd mention it.
 

khedger

Member
Credits
494
thanks for the tip. I ran fsck on the partitions. Here's the output of one execution.
Code:
sudo fdisk /dev/sdc

Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000MX500SSD1
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: dos
Disk identifier: 0xd5e35e20

Device     Boot      Start        End   Sectors  Size Id Type
/dev/sdc1             2048  524290047 524288000  250G 83 Linux
/dev/sdc2        524290048 1048578047 524288000  250G 83 Linux
/dev/sdc3       1048578048 1572866047 524288000  250G 83 Linux

Command (m for help): q

[email protected]:~$ sudo fscd /dev/sdc1
[sudo] password for khedger:
sudo: fscd: command not found
[email protected]:~$ sudo fsck /dev/sdc1
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
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/sdc1

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 dos partition table in /dev/sdc1
So, I know nothing about supeerblocks (I'll do some reading), but anybody
know how the superblocks would become corrupted on a newly installed and
partitioned disk? This is the first time I've tried partitioning and using this disk.

keith
 

furtom

New Member
Credits
69
Ok. So this might go badly. May be bad hard disk.

You can try the following, it's worth a shot:

if you have any important data on that drive, I hope it's backed up.

If the above does not work (and I have my doubts), you should create a new partition table, gpt, and recreate the partitions. Note, this will destroy all data on the partitions.

In fact, if you don't have anything critical on that drive, I'd just go with the new partition table first thing.

If you do that and stillhave problems, it's a hardware problem for sure.

good luck,
Tom
 

khedger

Member
Credits
494
This problem was related to the other problem I opened --
thanks for all of your help. Dummy me....I forgot that I actually have to MAKE a filesystem! DUH!
It's been a few years since I've mucked with this stuff....anyway, with your kind help I've made the filesystems, mounted them, unmounted them, edited /etc/fstab, done mount -a and everything now works. Thanks again for the help.

keith
 


Members online

No members online now.

Latest posts

Top