Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I have browsed the many other questions related to my question, there seems to be many solutions for others, but not for me, when I try to mount my HDD using:

sudo mount /dev/sdd /media/jinglez/MainFiles

I get the error:

jinglez@jinglezServer:~$ mount /dev/sdd /media/jinglez/MainFiles mount: wrong fs type, bad option, bad superblock on /dev/sdd, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

As requested, I ran dmesg | tail which returned:

jinglez@jinglezServer:~$ dmesg | tail
[   64.337321] init: transmission-daemon main process (882) terminated with status 127
[   64.337361] init: transmission-daemon respawning too fast, stopped
[   64.896160] tg3 0000:02:00.0: irq 42 for MSI/MSI-X
[   65.695028] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   65.695463] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   99.933921] systemd-hostnamed[3202]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[  120.906364] init: plymouth-stop pre-start process (4631) terminated with status 1
[  377.372510] EXT4-fs (sdd): bad geometry: block count 732566646 exceeds size of device (732566381 blocks)
[  380.264264] EXT2-fs (sdd): error: couldn't mount because of unsupported optional features (240)
[  382.129108] EXT3-fs (sdd): error: couldn't mount because of unsupported optional features (240)

I'm fairly new to Ubuntu, so it's safe to say I'm stumped now, what else can I try?

share|improve this question

1 Answer 1

After vigorous research on something I really know nothing about, I did find my solution.

After 'googling' pretty much every line that looked like an error in the dmesg, the bad geometry block was my winner.

377.372510] EXT4-fs (sdd): bad geometry: block count 732566646 exceeds size of device (732566381 blocks)

Have a block count that exceeds the size of the device blocks makes sense. However I was very scared when reading that I should use resize2fs to resize it, I took a deep breath, and wallah! I was able to view my files again.

I knew that I only had about 1.5TB of space used on the disk, so just to be safe, I did this:

resize2fs /dev/sdd 2500000M

I was then able to mount the drive without any problems!

That was my solution!

share|improve this answer
    
For your information: you can (and in fact should) accept your own answer when you find the solution to your problem yourself. It helps others with the same problem find the solution at a glance and also prevents the StackExchange system from periodically "poking" and highlighting it as an unanswered question. –  n.st Jan 30 at 0:31
    
I would have, but it doesn't let me do it for 2 days! :( @n.st –  Shannon Hochkins Jan 30 at 4:08

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.