I can't find my c drive after installing

Thanks for the question.

The one that you point to is indeed a linux partition, therefore if that was your windows partition that has been overriden now. However, you might want to look at your other drive (sdb) the first partition with 217GB is a windows FAT system. Maybe this is the partitition you are looking for.

I hope this helps.

Thanks, I think you're right and that is the drive I want to access. My question now is how do I go about using it. *-volume:0

On Sun, 27. May 2007 16:30:00 druff wrote:
> New question #7264 on Ubuntu:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Hello new friends, I'm new to both Linux and Ubuntu. I was trying to set up
> a dual boot with my windows media center, but I messed up somewhere and
> Ubuntu installed over windows. I have no real problem being without
> windows, but It doesn't seem that ubuntu is recognizing my main hard drive.
> I've been looking through other questions but can't find what I'm looking
> for, I am a total noob and hate asking but any help would be appreciated.
> In some of other questions that seemed to fit mine, I saw people being
> asked to run the command sudo lshw -C disk I got these results.
>
[...]
>
> The one marked *-volume:0 with the 183 gigs is the one I'm looking to have
> access to. Other than this issue I love Ubuntu and can't wait to become a
> member of the community. Thanks.

Please post the output of 'sudo fdisk -l' for this open a terminal and start
 sudo fdisk -l

Also post the content of your '/etc/fstab' file. For this start
 cat /etc/fstab | grep -v ^#

(This are two commands connected via a pipe (|), 'cat /etc/fstab' will list
the whole content of the fstab file and pipe it to the next command 'grep -v
^#' which will cut all lines which start with a '#')

regards,
thomas

sudo fdisk -l

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 23947 192354246 83 Linux
/dev/sda2 23948 24321 3004155 5 Extended
/dev/sda5 23948 24321 3004123+ 82 Linux swap / Solaris

Disk /dev/sdb: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 1 28413 228227391 c W95 FAT32 (LBA)
/dev/sdb2 * 28414 30421 16129260 83 Linux
/dev/sdb3 30422 30515 755055 5 Extended
/dev/sdb5 30422 30515 755023+ 82 Linux swap / Solaris

 cat /etc/fstab | grep -v ^#

proc /proc proc defaults 0 0
UUID=da6615bd-6f75-4143-a131-d5c272615e19 / ext3 defaults,errors=remount-ro 0 1
UUID=74788ba3-f991-4473-a43a-8e76c2d7b113 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0

Thanks Thomas

Here are some general instructions on howto mount and access windows drives under ubuntu https://help.ubuntu.com/community/MountingWindowsPartitions.

Thanks again, when I try to run the mkdir /media/windows command I get the following message. This seems like it would work if I had permission.

mkdir: cannot create directory `/media/windows': Permission denied

On Sun, 27. May 2007 17:28:36 druff wrote:
> Question #7264 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Status: Answered => Open
>
> druff is still having a problem:
> sudo fdisk -l
>
> Disk /dev/sda: 200.0 GB, 200049647616 bytes
> 255 heads, 63 sectors/track, 24321 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 23947 192354246 83 Linux
> /dev/sda2 23948 24321 3004155 5 Extended
> /dev/sda5 23948 24321 3004123+ 82 Linux swap /
> Solaris
>
> Disk /dev/sdb: 251.0 GB, 251000193024 bytes
> 255 heads, 63 sectors/track, 30515 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 28413 228227391 c W95 FAT32 (LBA)
This above is you old windows partition

> /dev/sdb2 * 28414 30421 16129260 83 Linux
> /dev/sdb3 30422 30515 755055 5 Extended
> /dev/sdb5 30422 30515 755023+ 82 Linux swap /
> Solaris
>
>
> cat /etc/fstab | grep -v ^#
>
> proc /proc proc defaults 0 0
> UUID=da6615bd-6f75-4143-a131-d5c272615e19 / ext3 defaults,errors=remount-ro
0 1
> UUID=74788ba3-f991-4473-a43a-8e76c2d7b113 none swap sw 0 0
> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
And here a line for mounting your old windows partition is missing.
For this we first have to create a folder to which we can mount your old C:
partition.

I will use the name 'oldwin' for this, you may choose another name.
In Linux a partition like this is commonly mounted below the /mnt directory.
It should be there but lets have a look first if /mnt really exists.

For this open a terminal by right-click on the desktop and choose 'Terminal'
Start the comand:
 ls -d /mnt

If it shows:
 /mnt
you know it exists.

But if it shows:
 ls: /mnt: No such file or directory
we have to create it first.

For this start:
 sudo mkdir /mnt

Now we will create the directory 'oldwin'
Start
 sudo mkdir /mnt/oldwin

To mount the old C: partition (/dev/sdb1) on startup we have to add a line to
the /etc/fstab file.

Start:
 sudo gedit /etc/fstab

Add the following line at the end of the file:
 /dev/sdb1 /mnt/oldwin vfat defaults,umask=000 0 0

Save the file and quit gedit.

Now this partition will be mounted during startup.

To have this partition mounted whithout a restart go back to the terminal and
start:
 sudo mount /mnt/oldwin

Thats it, you will see the old C: partition (e.g. in nautilus) at /mnt/oldwin

If you are using Gnome you may add a link to see this partition as a folder on
your desktop.

Open a terminal and start:
 cd
 ln -s /mnt/oldwin Desktop/oldwin

You will see a folder symbol on the desktop which has a link symbol in the
bottom left corner. You now have read and write access to your old C:
partition.

regards,
thomas

Thomas thanks, that's exactly what I needed, but it was on the wrong drive, that one was my external that was already working fine. I really appreciate your help and this should be the last issue, but how would I do the same process for,
   *-volume:0
          description: Linux filesystem partition
          physical id: 1
          bus info: scsi@2:0.0.0,1
          logical name: /dev/sda1
          capacity: 183GB
          capabilities: primary bootable

change the line in /etc./fstab from

/dev/sdb1 /mnt/oldwin vfat defaults,umask=000 0 0

to

/dev/sda1 /mnt/oldwin vfat defaults,umask=000 0 0

Thanks Ralph Janke, that solved my question.

One more thing. Now I have access but read only. How would I change the settings so I could write to the drive?

thanks again

On Sun, 27. May 2007 18:32:57 druff wrote:
> Question #7264 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Status: Answered => Open
>
> druff is still having a problem:
> Thomas thanks, that's exactly what I needed, but it was on the wrong drive,
> that one was my external that was already working fine. I really appreciate
> your help and this should be the last issue, but how would I do the same
> process for, *-volume:0
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@2:0.0.0,1
> logical name: /dev/sda1
> capacity: 183GB
> capabilities: primary bootable

Due to:
/dev/sda1 * 1 23947 192354246 83 Linux

and
/dev/sdb2 * 28414 30421 16129260 83 Linux

in the fstab there are two linux partitions but only one is mounted.

Due to the fact that there is a linux partition mounted with the UUID:
da6615bd-6f75-4143-a131-d5c272615e19
we have to figure out if this is sda1 or sdb2 before we can add a new line to
the fstab file. For this we have to check the given UUID and if needed figure
out the missing UUID for the new partition to mount.

- Step 1: figure out if sda1 or sdb2 is mounted
So open a terminal again and start:
 sudo vol_id /dev/sda1 | grep grep ID_FS_UUID=

If it shows the UUID da6615bd-6f75-4143-a131-d5c272615e19 this is the
partition which is mounted via the existing fstab ine.

If it shows another UUID we now knew the UUID for a new fstab line.
This will be the UUID we can use for a new fstab line and can go on with step
3

- Step 2: figure out the UUID of the second linux partition
If it shows the UUID da6615bd-6f75-4143-a131-d5c272615e19 we have to look for
the UUID of sdb2

For this case start:
 sudo vol_id /dev/sdb2 | grep grep ID_FS_UUID=

We will need this UUID for mounting the partition later on

- Step 3: Now we have to add a directory to mount the partition and add a new
line to fstab (same procedure as we did for your old windows partition)

Open a terminal and start:
 sudo mkdir /data
(You may choose another name than data)

Now start:
 sudo gedit /etc/fstab
add a line as follows:
 UUID=($UUID) /data ext3 defaults,user_xattr,acl 0 2

For ($UUID) add the UUID we figured out for the partition which is *not*
mounted.
Or strictly speaking *not* the UUID da6615bd-6f75-4143-a131-d5c272615e19 :-)

Note: To be honest we don't know here if the new partition is formatted as
      ext2 or ext3. So if you facing problems mounting this partition
      change 'ext3' to 'auto'

Save the fstab file and close gedit.

In a terminal a:
 mount -a
should mount the new partition.

Thats it.

Resume: You just made your first step towards becoming a MOTU. [1]
        - You now knew how to examine which drives are present in a system by
          using the fdisk -l command,
        - learned how to compare this with the currently mounted partitions
          shown by the 'cat /etc/fstab | grep -v ^#' command(s)
        - saw the first example of piping one command to another by using '|',
          this is a fundamental procedure on all Linux, BSD, Solaris and OS/X
          Systems (precisely on all UNIX flavours)
        - learned how to add a new directory from a terminal with mkdir ,
        - learned how to add a link to an existing folder / file with the ln
          command,
        - learned how to examine the UUID for a partition using the vol_id
          command,
        - learned how to mount a partition via it's UUID

Not bad, isn't it. :-))
Congratulations!

If you are keen on learning more about linux commands now it may be time to
visit the Linux Documentation Project: http://tldp.org/ You will find HowTos
and documentations for ther most interesting Linux comands and services.

[1] MOTU: Master Of The Universe, may be seen as a master degree in the ubuntu
          community.

regards.
thomas

On Sun, 27. May 2007 18:50:06 Ralph Janke wrote:
> Question #7264 on Ubuntu changed:
> https://answers.beta.launchpad.net/ubuntu/+question/7264
>
> Status: Open => Answered
>
> Ralph Janke proposed the following answer:
> change the line in /etc./fstab from
>
> /dev/sdb1 /mnt/oldwin vfat defaults,umask=000 0 0
>
> to
>
> /dev/sda1 /mnt/oldwin vfat defaults,umask=000 0 0
Hhhhhmmmm, can *this* be correct?

According to what druff wrote in one of his last postings this *must* be
wrong!

He wrote:
---8<--- ---8<--- ---8<---
 sudo fdisk -l

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 23947 192354246 83 Linux
---8<--- ---8<--- ---8<---

So sda1 has a Linux partition ID 83)and *not* a windows vfat partition ID (c)!

At least it would be the first time ever since I use UNIX'oide Systems
(started somwhere in the mid 1980ies) if it will work.
*If* this will work someone *must* have changed the partition type mannually
using fdisk or cfdisk.

regards,
thomas

Thanks again, thanks. When i entered sudo vol_id /dev/sda1 | grep grep ID_FS_UUID I got the following message grep: ID_FS_UUID: No such file or directory .

On Sun, 27. May 2007 20:15:45 druff wrote:
> Question #7264 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Status: Solved => Open
>
> druff is still having a problem:
> Thanks again, thanks. When i entered sudo vol_id /dev/sda1 | grep grep
> ID_FS_UUID I got the following message grep: ID_FS_UUID: No such
> file or directory .

ARRGGLLL, shame on me....

It should be:
 sudo vol_id /dev/sda1 | grep ID_FS_UUID

pardon me please,
thomas

On Sun, 27. May 2007 20:48:11 coastgnu wrote:
> Question #7264 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Status: Open => Answered
>
> coastgnu proposed the following answer:
>
> On Sun, 27. May 2007 20:15:45 druff wrote:
> > Question #7264 on Ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+question/7264
> >
> > Status: Solved => Open
> >
> > druff is still having a problem:
> > Thanks again, thanks. When i entered sudo vol_id /dev/sda1 | grep grep
> > ID_FS_UUID I got the following message grep: ID_FS_UUID: No such
> > file or directory .
>
> ARRGGLLL, shame on me....
>
> It should be:
> sudo vol_id /dev/sda1 | grep ID_FS_UUID
sudo vol_id /dev/sda1 | grep ID_FS_UUID=

Golly gosh!

The '=' should be there, example:
 sudo vol_id /dev/sda1 | grep ID_FS_UUID
 ID_FS_UUID=1b95fc8e-2fed-4ff6-a727-917f9ce9bb97
 ID_FS_UUID_SAFE=1b95fc8e-2fed-4ff6-a727-917f9ce9bb97

and

 sudo vol_id /dev/hda1 | grep ID_FS_UUID=
 ID_FS_UUID=1b95fc8e-2fed-4ff6-a727-917f9ce9bb97

I will not use cut'and'paste anymore today...

regards,
thomas

Thomas, the sudo vol_id /dev/sda1 | grep ID_FS_UUID command did bring up ID_FS_UUID=da6615bd-6f75-4143-a131-d5c272615e19 but that was all it brought up, when i entered sudo vol_id /dev/sdb2 | grep grep ID_FS_UUID= and it responded with grep: ID_FS_UUID=: No such file or directory

no need for a pardon, I appreciate your efforts fully

On Sun, 27. May 2007 21:01:32 druff wrote:
> Question #7264 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/7264
>
> Status: Answered => Open
>
> druff is still having a problem:
> Thomas, the sudo vol_id /dev/sda1 | grep ID_FS_UUID command did bring
> up ID_FS_UUID=da6615bd-6f75-4143-a131-d5c272615e19 but that was all it
> brought up, when i entered sudo vol_id /dev/sdb2 | grep grep
> ID_FS_UUID= and it responded with grep: ID_FS_UUID=: No such file or
> directory
This was because of 'grep grep ID_FS_UUID='
This cmmand says 'start grep and search for the string grep in the file
ID_FS_UUID='. So it is to be expected to fail because there is no
file 'ID_FS_UUID='.

>
> no need for a pardon, I appreciate your efforts fully

So the line in fstab which says:
UUID=da6615bd-6f75-4143-a131-d5c272615e19 / ext3 --- ---

is for sda1

Now we know that it is sdb2 which is not mounted.

To examine the UUID for sdb2 start the command:
 sudo vol_id /dev/sda1 | grep ID_FS_UUID=

After this follow the instructions to create a mount directory /data and to
add a line in fstab.

regards,
thomas