Need to recover from an ID-10-T error.
UNGER, JOHN WM
JWU001 at SHSU.EDU
Thu Dec 24 04:41:43 UTC 2009
I'm wearing out as well.
If this doesn't fix it the brute force will have to take over. I'll be out of pocket myself for the next week.
Here is what we got:
ubuntu at ubuntu:~$ sudo -s
root at ubuntu:~# mkdir /mnt/boot /mnt/root
root at ubuntu:~# mount -t ext3/dev/sda1 /mnt/boot
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
One can change the type of mount containing the directory dir:
mount --make-shared dir
mount --make-slave dir
mount --make-private dir
mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
mount --make-rshared dir
mount --make-rslave dir
mount --make-rprivate dir
mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
root at ubuntu:~# mount mount -t ext3 /dev/sda1 /mnt/boot
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
One can change the type of mount containing the directory dir:
mount --make-shared dir
mount --make-slave dir
mount --make-private dir
mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
mount --make-rshared dir
mount --make-rslave dir
mount --make-rprivate dir
mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
root at ubuntu:~# mount -t ext3 /dev/sda4 /mnt/root
root at ubuntu:~# ls /mnt/boot
root at ubuntu:~# ls /mnt/root
bin cdrom etc hold-boot initrd lib lib64 media mnt proc sbin sys usr vmlinuz
boot dev grub home initrd.img lib32 lost+found memtest86+.bin opt root srv tmp var windows
root at ubuntu:~# mount -l
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /lib/modules/2.6.24-24-generic/volatile type tmpfs (rw,mode=0755)
tmpfs on /lib/modules/2.6.24-24-generic/volatile type tmpfs (rw,mode=0755)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)
/dev/sda4 on /mnt/root type ext3 (rw) []
root at ubuntu:~# ls -l -v /mnt/root
total 228
drwxr-xr-x 2 root root 4096 2009-09-28 14:08 bin
drwxr-xr-x 4 root root 4096 2009-12-23 19:22 boot
lrwxrwxrwx 1 root root 11 2009-09-28 18:59 cdrom -> media/cdrom
drwxr-xr-x 4 root root 4096 2009-07-09 07:56 dev
drwxr-xr-x 130 root root 12288 2009-12-22 19:53 etc
drwxr-xr-x 2 root root 4096 2009-12-24 03:50 grub
drwxr-xr-x 2 root root 4096 2009-12-22 19:39 hold-boot
drwxr-xr-x 4 root root 4096 2009-09-29 00:44 home
drwxr-xr-x 2 root root 4096 2009-12-23 16:42 initrd
lrwxrwxrwx 1 root root 33 2009-09-28 14:07 initrd.img -> boot/initrd.img-2.6.24-24-generic
drwxr-xr-x 15 root root 12288 2009-10-07 02:45 lib
drwxr-xr-x 4 root root 4096 2009-10-07 02:45 lib32
lrwxrwxrwx 1 root root 4 2009-09-28 18:59 lib64 -> /lib
drwx------ 2 root root 16384 2009-09-28 18:58 lost+found
drwxr-xr-x 3 root root 4096 2009-12-22 19:14 media
-rw-r--r-- 1 root root 103204 2007-09-28 11:03 memtest86+.bin
drwxr-xr-x 2 root root 4096 2008-04-15 05:53 mnt
drwxr-xr-x 2 root root 4096 2009-07-09 07:40 opt
drwxr-xr-x 2 root root 4096 2008-04-15 05:53 proc
drwxr-xr-x 13 root root 4096 2009-12-22 19:20 root
drwxr-xr-x 2 root root 4096 2009-10-26 01:25 sbin
drwxr-xr-x 2 root root 4096 2009-07-09 07:40 srv
drwxr-xr-x 2 root root 4096 2008-04-18 16:02 sys
drwxrwxrwt 10 root root 4096 2009-12-22 19:53 tmp
drwxr-xr-x 12 root root 4096 2009-10-01 02:07 usr
drwxr-xr-x 15 root root 4096 2009-07-09 08:04 var
lrwxrwxrwx 1 root root 30 2009-09-28 14:07 vmlinuz -> boot/vmlinuz-2.6.24-24-generic
drwxr-xr-x 2 root root 4096 2009-09-28 18:59 windows
root at ubuntu:~# ls -l /mnt/boot
total 0
________________________________________
From: ubuntu-users-bounces at lists.ubuntu.com [ubuntu-users-bounces at lists.ubuntu.com] On Behalf Of Rashkae [ubuntu at tigershaunt.com]
Sent: Wednesday, December 23, 2009 8:27 PM
To: Ubuntu user technical support, not for general discussions
Subject: Re: Need to recover from an ID-10-T error.
UNGER, JOHN WM wrote:
> and the one I edited was not the right one.
> Let me go searching some.
>
> Any ideas how I can get to the partitions through the terminal? I'd rather do that than keep working with the GUI that seems to be directing me somewhere else...
>
> -John U
>
John, I am really very very sorry to say, but the exact nature of your
knot is proving vexing to untangle. I am 100% certain that once the
true picture of what files are where is fully known, this will be an
easy fix. However, it's getting very close to my bedtime, and I'll have
no time tomorow morning before I depart for family X-mas. If you don't
hear back from me, you'll have to either seek someone else who can help,
brute force it with a re-install, or e-mail me directly (rashkae at
tigershaunt dot com) in 4 days.
--
ubuntu-users mailing list
ubuntu-users at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
More information about the ubuntu-users
mailing list