Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here is the error

Error mounting system-managed device /dev/sdb1: Command-line `mount "/mnt/287319a7-69ba-45b8-b8bf-e2fd4d6ea6f0"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail  or so
share|improve this question
up vote 0 down vote accepted

/dev/sdb1 disk will mount if you update your kernal.Run the below command on terminal to update linux kernal,

sudo apt-get install linux-generic

These errors are caused mainly due to bugs in the kernal.Updating your kernal will solve this mounting problem.

share|improve this answer
I was running NADIA using a single Drive, added another drive and installed PETRA, figured I could try and recover files from the disk this way, new to Linux and not sure what to do just to get the bad drive to mount. Considering testdrive but not sure how to use. Tried Gparted (w parted algos) it had no luck, the drive does show up in the Computer, and does indicate 60 some bad sectors. – Dan Nov 30 '13 at 16:23
try sudo badblocks -sv /dev/sdb1 to check for badblocks. – Avinash Raj Nov 30 '13 at 16:29
see this… to recover data from disks which contains badblocks. – Avinash Raj Nov 30 '13 at 16:34
Its checking... is there a way to run fsck on the bad disk (thinking I have to be able to mount it first) – Dan Nov 30 '13 at 16:38
fsck /dev/sdb1 – Avinash Raj Nov 30 '13 at 16:40

Your Answer


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.