I followed the above steps exactly and got the same error upon reboot that I got before, other than the location is of course different this time... when I rebooted the "Kubuntu" splash screen said "there was an error mounting /media/video, press S to skip or ESC to reboot". I think the system tried to mount it and it failed the same way. I'm not sure how to go back and look at exactly what happened.
Code:
chaz@brutus:~$ dmesg | grep mount |
Perhaps the disk has a filesystem error, in which case you should unmount it and then try running sudo fsck.ext4 /dev/sda1 on it, to see if it can be repaired.
Meanwhile, you can try mounting it manually, and see what the error is. You have already created the mountpoint at /media/video so try this: Code:
sudo mount -t ext4 /dev/sda1 /media/video dmesg | grep sda1 will be more informative than dmesg | grep mount |
Trying to mount it manually gives me the same error I've been getting.
Code:
chaz@brutus:~$ sudo mount /dev/sda1 /media/video/ Code:
chaz@brutus:~$ mount Code:
chaz@brutus:~$ umount /dev/sda1 Code:
chaz@brutus:~$ dmesg | grep sda1 |
Quote:
Code:
sudo fsck.ext4 /dev/sda1 After you fsck /dev/sda1, then see if you can now mount it from the live CD: Code:
sudo mount /dev/sda1 /mnt |
I am having trouble working out what is going on, but in post #18 you say
Quote:
|
Quote:
When I rebooted, I got the same exact error I had before...the Kubuntu splash screen said there was a problem mounting /dev/sda1. I pressed S to skip, then after my system booted I'm having exactly the same problem...even though the disk is freshly formatted! How can this be? Do I need to reinstall Ubuntu? Quote:
Quote:
|
Perhaps try mounting /dev/sda1 using it's UUID, since Ubuntu uses UUIDs to identify partitions in fstab.
First, run: "sudo blkid". This will list the partitions and their respective UUIDs. Then to mount /dev/sda1 run: Code:
sudo mount -t ext3 UUID /mnt/videos |
When I run blkid, it doesn't list the UUID for /dev/sda1. And when I tried to feed blkid "/dev/sda1" it returned nothing.
Code:
chaz@brutus:~$ sudo blkid |
Hi,
some irregularities I noticed: Quote:
From your follow-up posts I am going to assume that you meant /dev/sda1 is your new partition on your new drive. if I understood you correctly then you can confirm that - on your new drive there is nothing unusual like an lvm or encrypted disk etc. - it does mount without problem when using a liveCD - it is an internal drive and not an external USB drive So if it is an internal drive then I assume that your OS-drives got recognized as /dev/sdaX earlier. After you installed the second hd this changed to /dev/sdbX. So maybe there is some confusion because of the changed device names. Now your new disk appears as /dev/sda1. This should not cause any trouble normally, that is what UUID is for. However, you could try running Code:
sudo update-grub2 Also, whenever I use (g)parted to partition a drive I get problems when trying to install grub afterwards. Something about misaligned boundaries. So if possible I prefer fdisk for partitioning and after that format it manually. |
Quote:
Originally I had one 1TB hard drive. Call it Drive1. It was my old hard drive. It was formatted with ReiserFS. I'd had it for years. I wanted to get away from Reiser so some weeks ago when the new Ubuntu came out, I bought a new 1TB hard drive (call it Drive2). I plugged Drive2 into my system all by itself, partitioned and installed Ubuntu with the alternate CD. I said that I wanted to encrypt my home directory. So I had a new install but the home directory was 'empty' and all my data was still on my old Drive1. Then, I plugged in Drive1 as well, rebooted and manually mounted it (with no problems) and copied the entire contents of the old home partition from Drive1 onto the new, encrypted home directory on Drive2. This transferred all my files and my settings to the new system, and the transition away from Reiser was complete. Then, I used parted to delete and repartition Drive1 with one big Ext4 partition. I mounted this hard drive manually at least several times with no problems and copied a couple files to it just for testing purposes. I intended it to me my new drive for holding videos. Then I tried to add it to my fstab to have it mount to /home/video, and I could not do so because my encrypted home directory does not exist until I log in, so fstab couldn't mount it somewhere that doesn't exist. Then I made this thread saying "WTF". I figured out the reason it originally wouldn't mount with fstab, but now ever since then, when I try to mount the "new" hard drive to my system, or I try to have fstab do it, I get this error, even after repartitioning it again completely, and no matter where I attempt to mount it. Quote:
Quote:
Quote:
|
Hi,
ok, this sounds like we are chasing needles here. Can you post the output of the following commands Code:
sudo cat /proc/mounts Also, I am not sure about gparted. I do not use it. However, parted does not create a filesystem although it has an option that it can. I always ran into problems with it. So can you - from the liveCD - repartition/reformat it using fdisk/mke2fs? Pay attention that you get the correct device name when you run the liveCD. The device names might differ when using the liveCD, i.e. the 'video hd' might be /dev/sda on your OS but when using the liveCD it might be recognized as /dev/sdb. So run fdisk -l first to identify the correct hd. Partition the 'video hd' with 'fdisk /dev/sdX'. Make sure that you write the changes to disk before you exit fdisk. Then format it Code:
mke2fs -j -c -c /dev/sdX1 # will perform a read-write check and create an ext3 filesystem Quote:
I assume you already double-checked that the contacts are attached properly, anyway. Did you try the reinstalling grub? Even if it sounds unlikely after your description let us keep it as a possibility in mind. |
Code:
chaz@brutus:~$ sudo cat /proc/mounts Code:
chaz@brutus:~$ sudo find / -type f -name '*.lock' -print |
Hi,
- what about the other 'find' command? - Did you repartition using fdisk, not (g)parted? And then format with the command I provided? |
I started running
Code:
mke2fs -j -c -c /dev/sdX1 # will perform a read-write check and create an ext3 filesystem |
My power went out halfway through. Wonderful. I will run it again overnight I guess. Do I have to use a LiveCD, or can I just use my normal system?
|
All times are GMT -5. The time now is 05:52 PM. |