[SOLVED] Error with new mounted Hard Drive.

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Mindrop

[SOLVED] Error with new mounted Hard Drive.

Post by Mindrop »

My computer finally used up its small hard drive so I needed to mount the extra hard drive I have hard for several months( but forgot to mount). I mounted it, and it threw and error, wiped it and re did it, and still an error.

INFO: Error read and cant access new hard drive.
OS: Mint 12 (64bit) (LISA)
Hard Drive: WD 74 Gig RapterDrive (7200)

I searched found https://help.ubuntu.com/community/Insta ... wHardDriveand first attempted to follow this to mount my hard drive was unsucsessful. I was fine up until the Fstab. I wiped the drive and moved on to another guide.

I got a page from a friend, and that worked, except it throws an error.

http://www.ehow.com/how_1000631_hard-drive-linux.html

Image

Yes, I am lost. The drive shows up in the folders under my "Computer" drive, but it gives me that error. I have rebooted it a few times, and nothing new.

Please Help.

EDIT: More info.

Code: Select all

sudo blkid -c /dev/null
/dev/sda1: UUID="e3a54a4b-ce32-4f5e-ab9b-be25b157386c" TYPE="ext4"
/dev/sda5: UUID="99b3e38d-071f-4bbd-97ee-679eb8f23bd1" TYPE="swap"
/dev/sdb1: UUID="e1b6a048-6115-458d-9ef9-f0e04759f44a" TYPE="ext2"

Code: Select all

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=e3a54a4b-ce32-4f5e-ab9b-be25b157386c / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=99b3e38d-071f-4bbd-97ee-679eb8f23bd1 none swap sw 0 0
/dev/sdb1 /media/mynewdrive ext3 defaults 0 2

Code: Select all

mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/shayne/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=shayne)
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
altair4
Level 20
Level 20
Posts: 11426
Joined: Tue Feb 03, 2009 10:27 am

Re: Error with new mounted Hard Drive.

Post by altair4 »

The best thing to do is post the output of the following commands to give everyone here something to work with:

Code: Select all

sudo blkid -c /dev/null

Code: Select all

cat /etc/fstab

Code: Select all

mount
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Mindrop

Re: Error with new mounted Hard Drive.

Post by Mindrop »

Thanks. Here you go. (Also editing it into my first post.)

Code: Select all

sudo blkid -c /dev/null
/dev/sda1: UUID="e3a54a4b-ce32-4f5e-ab9b-be25b157386c" TYPE="ext4"
/dev/sda5: UUID="99b3e38d-071f-4bbd-97ee-679eb8f23bd1" TYPE="swap"
/dev/sdb1: UUID="e1b6a048-6115-458d-9ef9-f0e04759f44a" TYPE="ext2"

Code: Select all

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=e3a54a4b-ce32-4f5e-ab9b-be25b157386c / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=99b3e38d-071f-4bbd-97ee-679eb8f23bd1 none swap sw 0 0
/dev/sdb1 /media/mynewdrive ext3 defaults 0 2

Code: Select all

mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/shayne/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=shayne)
altair4
Level 20
Level 20
Posts: 11426
Joined: Tue Feb 03, 2009 10:27 am

Re: Error with new mounted Hard Drive.

Post by altair4 »

Well, blkid says it's an ext2 partition and fstab is trying to mount it as an ext3 so if you really want it as an ext2 then change this in fstab:
/dev/sdb1 /media/mynewdrive ext3 defaults 0 2
To this:
/dev/sdb1 /media/mynewdrive ext2 defaults 0 2
Then run the following command to test for errors ( it will just come back to the prompt if there are no errors ) and if there are no errors mount the partition without a reboot:

Code: Select all

sudo mount -a
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Mindrop

Re: Error with new mounted Hard Drive.

Post by Mindrop »

Should the drive be ext2 or ext3 in your opinion? And how do I edit in Fstab?

Code: Select all

sudo mount -a
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
altair4
Level 20
Level 20
Posts: 11426
Joined: Tue Feb 03, 2009 10:27 am

Re: Error with new mounted Hard Drive.

Post by altair4 »

Last question first:

Code: Select all

gksu gedit /etc/fstab
First question last: If it were me

** I would use gparted and reformat it ext4 ( it is empty at the moment right? )
** I would then rerun the bklid command:

Code: Select all

sudo blkid -c /dev/null
Using the information you get from blkid I would rewrite the line in fstab to this:

Code: Select all

UUID=4638c269-d57d-44c0-9c0c-e7d7c330d33b /media/mynewdrive ext4 defaults,noatime 0 2
Note: The UUID number above is an example. Blkid will tell you the correct number.
Then run the mount command:

Code: Select all

sudo mount -a
Then there is one last step and that is to take possession of the mounted partition:

Code: Select all

sudo chown shayne /media/mynewdrive
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Mindrop

Re: Error with new mounted Hard Drive.

Post by Mindrop »

THANK YOU! That took way to long. Way to long to do. Well, now I will be able to do it when I get drives 3, 4 and 5.

I can finally save stuff on my computer again. I cant thank you enough.
haberst

Re: [SOLVED] Error with new mounted Hard Drive.

Post by haberst »

Hello,

I have similar problem, so I hope I can hijack this thread? :)

I have RAID1 setup altough. 2x500GB HDD's with 3 partitions. And 1x500GB as separate USB HDD for backup (not mounted yet).
/boot, swap and /root.

I already have rebuilt it 1 time (It was my mistake after Linux setup, not hw failure), and with that time the swap partition is broken or not working properly(since its RAID0).

I am using Linux software raid and partitions are following. Boot was partitioned as RAID1 so was root, but for swap I used RAID0! That maybe the culprit- dunno..


root@serv:/etc# cat /proc/mdstat
Personalities : [raid0] [raid1]
md2 : active raid1 sda3[0] sdb3[2]
480473976 blocks super 1.2 [2/2] [UU]

md1 : inactive sda2[0] sdb2[2](S)
15622144 blocks super 1.2

md0 : active raid1 sda1[0] sdb1[2]
96244 blocks super 1.2 [2/2] [UU]


Fstab shows that root partition has rw errors?!

root@r22serv:/etc# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/md2 during installation
UUID=dd98aabc-5b21-4adc-9dea-daf59e5b4e0b / ext3 errors=remount-ro 0 1
# /boot was on /dev/md0 during installation
UUID=83256d09-8800-4e73-bfd5-13154de308f6 /boot ext3 defaults 0 2
# swap was on /dev/md1 during installation
UUID=a079b990-7cda-4248-869c-0a0c5bb7ff61 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0

Mount command shows this:

root@r22serv:/etc# mount
/dev/md2 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)


BLKID shows this:

root@r22serv:/etc# blkid -c /dev/null
/dev/sda1: UUID="5da577d4-9be4-5276-a179-0973dd0b1a4f" LABEL="r22serv:0" TYPE="linux_raid_member"
/dev/sda2: UUID="c64cef5e-6570-33ea-e7b8-732aeefdecfa" LABEL="r22serv:1" TYPE="linux_raid_member"
/dev/sda3: UUID="3bce03da-b85d-6145-5809-cf311bb7c7a0" LABEL="r22serv:2" TYPE="linux_raid_member"
/dev/sdb1: UUID="5da577d4-9be4-5276-a179-0973dd0b1a4f" LABEL="r22serv:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="c64cef5e-6570-33ea-e7b8-732aeefdecfa" LABEL="r22serv:1" TYPE="linux_raid_member"
/dev/sdb3: UUID="3bce03da-b85d-6145-5809-cf311bb7c7a0" LABEL="r22serv:2" TYPE="linux_raid_member"
/dev/md0: UUID="83256d09-8800-4e73-bfd5-13154de308f6" TYPE="ext3"
/dev/md2: UUID="dd98aabc-5b21-4adc-9dea-daf59e5b4e0b" TYPE="ext3"


It shows that here the problem is not mounting wrong filesystem type, but something else?
I am quite a novice with Linux partitioning.

Big Thanks in advance!
altair4
Level 20
Level 20
Posts: 11426
Joined: Tue Feb 03, 2009 10:27 am

Re: [SOLVED] Error with new mounted Hard Drive.

Post by altair4 »

If this is a question to me I'm sorry but I don't do RAID. RAID is for servers not home PC's unless you work from home for Disney or Dreamworks and do a lot of video editing. You are also hijacking a [SOLVED] question so I would suggest you start your own topic with the word RAID in it so you will get responses from folks who have convinced themselves that it makes a difference and have experience setting it up.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
markator

Re: [SOLVED] Error with new mounted Hard Drive.

Post by markator »

Hope you can help another newbie with this one that looks similar.

I created 3 partitions + swap during a fresh install of Linux Mint 17.1, Cinnamon.
The install was done over a windows 7 that I wanted to erase.
After the installation was ready, I could see only the system partition that had Mint on it. The other partitions are nowhere to be found.

If I run in terminal "cat /etc/fstab" I get the result:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=dc45f815-d8fa-402e-a574-497283ff73d7 / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=4f3d5fd0-a2f7-4928-9003-5e428acc2286 /boot ext4 defaults 0 2
# /home was on /dev/sda3 during installation
UUID=698009ca-3e8f-4e2c-8dd4-917a19fa3fca /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=92312079-6148-43ba-96a4-65abb64759e3 none swap sw 0 0

I see there is an error but don't know how to fix it.

If I write sudo blkid -c /dev/null in terminal, I get:

/dev/sda1: UUID="dc45f815-d8fa-402e-a574-497283ff73d7" TYPE="ext4"
/dev/sda2: UUID="4f3d5fd0-a2f7-4928-9003-5e428acc2286" TYPE="ext4"
/dev/sda3: UUID="698009ca-3e8f-4e2c-8dd4-917a19fa3fca" TYPE="ext4"
/dev/sda4: UUID="92312079-6148-43ba-96a4-65abb64759e3" TYPE="swap"

I don't see what is wrong (appart from the obvious errors=remount-ro mesage).

Thank you in advance!
altair4
Level 20
Level 20
Posts: 11426
Joined: Tue Feb 03, 2009 10:27 am

Re: [SOLVED] Error with new mounted Hard Drive.

Post by altair4 »

After the installation was ready, I could see only the system partition that had Mint on it. The other partitions are nowhere to be found.
Run the following command:

Code: Select all

mount
The "system partition that had Mint on it" is where all of your other partitions ( /home and /boot ) are or should be already mounted and visible.

There is nothing to fix.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
markator

Re: [SOLVED] Error with new mounted Hard Drive.

Post by markator »

If I run "mount" I get the folowing:

"/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sda2 on /boot type ext4 (rw)
/dev/sda3 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=aventur)"

No partitions mounted. What do I do wrong?
WinterTroubles

Re: [SOLVED] Error with new mounted Hard Drive.

Post by WinterTroubles »

markator wrote:If I run "mount" I get the folowing:

"/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sda2 on /boot type ext4 (rw)
/dev/sda3 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=aventur)"

No partitions mounted. What do I do wrong?
The lines I've coloured red are your mounted partitions :)

Regards
WT
Locked

Return to “Storage”