| View previous topic :: View next topic |
| Author |
Message |
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
 Posted: Fri Dec 08, 2006 8:08 am Post subject: GRUB error on a fresh install |
 |
|
Hi there,
Just upgrading a server and thought I'd give the opterons a go with this build, as the old server was x86/gentoo for years.
asus A8N-E with an opteron 144 2 gig of ram and two barracudas in RAID 1.
Followed the install instructions to the letter substituting /dev/hda for /dev/sda where applicable due to the SATA drives.
After the kernel compile and reboot with out the CD I get :
"GRUB Loading stage1.5"
printed in a loop and nothing else.
Any ideas please ? I've been at this for two days and must be missing something !! help 
Thanks. |
|
| Back to top |
|
 |
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Fri Dec 08, 2006 8:21 am Post subject: |
|
|
Just updated to BIOS 1013, just to make sure that wasn't it.
Still the same issue atm. |
|
| Back to top |
|
|
Monkeh
Veteran
Joined: 06 Aug 2005
Posts: 1656
Location: England
|
| Posted: Fri Dec 08, 2006 12:05 pm Post subject: |
|
|
| Make sure your /boot partition is on the first SATA drive.. I ran into a painful problem trying to have GRUB installed on hd0, with /boot on hd1, same board. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Fri Dec 08, 2006 5:10 pm Post subject: |
|
|
| Monkeh wrote: | | Make sure your /boot partition is on the first SATA drive.. I ran into a painful problem trying to have GRUB installed on hd0, with /boot on hd1, same board. |
Well its on both drives as they are mirrored, I'm thinking I'm going to have to put in an old ATA drive now just for the /boot partition and then have everything else on the sata raid.
grub-install for some reason is detecting two though.
Though I'm going to try this first :
http://www.dur.ac.uk/a.d.stribblehill/mirrored_grub.html
then
http://www.dirigo.net/tuxTips/avoidingProblems/GrubMdMbr.php |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Fri Dec 08, 2006 6:44 pm Post subject: |
|
|
Well i've forced GRUB to put the MBR on both disks, now it hangs at stage2 ! lol
Just have to find out "what" stage 2 is now. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Fri Dec 08, 2006 8:52 pm Post subject: |
|
|
Back to fdisk now to try and get both disks set up the same....
Though with these commands :
mount /dev/sda3 /mnt/gentoo
mkdir /mnt/gentoo/boot
mount /dev/sda1 /mnt/gentoo/boot
I'm mounting the physical device, so its all only going to be installed on one drive ........argh !! Looking like single boot drive here, this is getting silly. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
|
| Back to top |
|
|
thedude0001
Arch/Herd Tester
Joined: 16 Jan 2005
Posts: 69
|
| Posted: Sat Dec 09, 2006 5:28 am Post subject: |
|
|
I've done it both on amd64 and x86 and haven't run into any big trouble...
What kind of RAID1 are you using? A pure software RAID with mdadm or some hardware RAID controller? What's your /boot/grub/grub.conf? What's the partition layout?
| Quote: | | And I've just redone the install again (on #5 now as you can't remount the drives after rebooting) |
Not even if you boot from the live CD? What error message is it giving you?
Basically the whole thing is pretty close to a normal installation. Create the RAID, create a FS, mount it, emerge grub, put your kernel in /boot/, install grub (once with root (hd0,0) & setup (hd0) and once with root (hd1,0) & setup (hd1) if we're talking about sda and sdb) and add the right "root=" command to grub.conf.
This is an example for the entries in grub.conf taken from my server:
| Code: | title=Gentoo Linux 2.6.17-r7 regular sda
# Partition where the kernel image (or operating system) is located
root (hd0,0)
kernel /kernel-2.6.17-r7 root=/dev/md1 console=tty0 console=ttyS0,57600
title=Gentoo Linux 2.6.17-r7 regular sdb
# Partition where the kernel image (or operating system) is located
root (hd1,0)
kernel /kernel-2.6.17-r7 root=/dev/md1 console=tty0 console=ttyS0,57600 |
Pitfalls are that RAID1 has to be compiled into the kernel (not as a module), same goes for the file system used on /boot.
If this still doesn't help please provide a bit more verbose report of what you are doing, especially commands and output from creating the RAID and installing grub.
_________________
Das Schlimme auf dieser Welt ist
daß die Dummen so selbstsicher sind
und die Gescheiten so voller Zweifel. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Sat Dec 09, 2006 7:22 am Post subject: |
|
|
Hi thanks for the post
I'm going for RAID 1 over two 320G barracudas (SATA2).
| thedude0001 wrote: | I've done it both on amd64 and x86 and haven't run into any big trouble...
What kind of RAID1 are you using? A pure software RAID with mdadm or some hardware RAID controller? What's your /boot/grub/grub.conf? What's the partition layout? |
I was pretty sure its me being a n00b, though with lilo & ext2 experince and no raid know how it's hard going.
I was using the raid that comes with the Asus A8N-E so the nForce4 Storage, actually building the raid in the bios, then using mdadm as per this wiki .
After searching and reading about it looks like the modo NVIDIA nForce4 Ultra RAID option was a waste and I should of just gone straight with kernel RAID, is that the accepted case ?
| Quote: | | Not even if you boot from the live CD? What error message is it giving you? |
I go back in with the LiveCD, though I can't create and mount the metadevice nodes again to access the RAID to try and change the config to try again.
The last error I got before more searching and starting again was the VFS floppy one, I'd lay money I passed "--no-floppy" to grub as well, this time I've physically removed the drive (I only put it in to flash the bios to ensure that was at 1013, the latest before this build).
| thedude0001 wrote: |
Basically the whole thing is pretty close to a normal installation. Create the RAID, create a FS, mount it, emerge grub, put your kernel in /boot/, install grub (once with root (hd0,0) & setup (hd0) and once with root (hd1,0) & setup (hd1) if we're talking about sda and sdb) and add the right "root=" command to grub.conf. |
I belive its the root= command I must be getting wrong, I'll post here again before doing the final umount and reboot to double check ! 
I am current running "mdadm --create" and its wirring away sync'ing up the drives.
I set :
| Code: |
device mount size
/dev/sda1 /boot 32MB Linux raid autodetect
/dev/sda2 swap 6G Linux raid autodetect
/dev/sda3 / 20GB Linux raid autodetect
/dev/sda4 /home (the rest) Linux raid autodetect
|
| thedude0001 wrote: |
This is an example for the entries in grub.conf taken from my server:
| Code: | title=Gentoo Linux 2.6.17-r7 regular sda
# Partition where the kernel image (or operating system) is located
root (hd0,0)
kernel /kernel-2.6.17-r7 root=/dev/md1 console=tty0 console=ttyS0,57600
title=Gentoo Linux 2.6.17-r7 regular sdb
# Partition where the kernel image (or operating system) is located
root (hd1,0)
kernel /kernel-2.6.17-r7 root=/dev/md1 console=tty0 console=ttyS0,57600 |
|
I'll post mine here before I reboot to double check, though I'm sure I didn't have 1 lines for each hd, 2 in total 
The gurb here and here only had the one. I didn't use genkernal as I don't like the idea of not knowing whats going in or not, for instance was SATA in there or did I need to add it as scsi as per another post I read.
| thedude0001 wrote: |
Pitfalls are that RAID1 has to be compiled into the kernel (not as a module), same goes for the file system used on /boot.
If this still doesn't help please provide a bit more verbose report of what you are doing, especially commands and output from creating the RAID and installing grub. |
So far I have :
Then set up my sda drive thus :
| Code: |
/dev/sda1 * 1 13 40131 fd Linux raid autodetect
/dev/sda2 6 76 6008310 fd Linux raid autodetect
/dev/sda3 754 3244 20008957+ fd Linux raid autodetect
/dev/sda4 3245 38913 286511242+ fd Linux raid autodetect
|
Copied that over to sdb with :
| Code: |
> sfdisk -d /dev/hda | sfdisk /dev/hdb
|
Been nice and lazy and :
| Code: |
> for i in `seq 1 4`; do mknod /dev/md$i b 9 $i; mdadm --create /dev/md$i --level=1 --raid-devices=2 /dev/sda$i /dev/sdb$i; done
|
Backed up the details :
| Code: |
> mdadm --detail --scan >> /etc/mdadm.conf
|
Watched it torture the harddrives with :
| Code: |
> watch -n1 'cat /proc/mdstat'
|
RAIDS's sync'ed.
Now, create some file systems and mount the basics :
| Code: |
> mke2fs -j /dev/md1
> mke2fs -j /dev/md3
> mkfs.ext3 -j -O dir_index /dev/md4
> mkswap /dev/md2
> swapon /dev/md2
> mount /dev/md3 /mnt/gentoo
> mkdir /mnt/gentoo/boot
> mount /dev/md1 /mnt/gentoo/boot
> mkdir /mnt/gentoo/home
> mount /dev/md4 /mnt/gentoo/home
|
File systems build on HD's, swap made and turned on, files systems mounted to points.
Local LAN is all dhcp no nice and easy.
Off to get portage and stage 3 with links:
| Code: |
> stage3-amd64-2006.1.tar.bz2
> portage-latest.tar.bz.2
|
Get stage 3 in there :
| Code: |
> tar xvjpf stage3-amd64-2006.1.tar.bz2
|
..... go make tea ....... wait .........
| Code: |
> tar xvjf /mnt/gentoo/portage-latest.tar.bz2 -C /mnt/gentoo/usr
|
... drink tea .... wait some more ... |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Sat Dec 09, 2006 9:36 am Post subject: |
|
|
Add "-march=opteron to" /mnt/gentoo/etc/make.conf which now looks like this :
| Code: |
CFLAGS-"-march=opteron -02 -pipe"
CHOST="x86_64-pc-linuc-gnu"
CXXFLAGS="${CFLAGS}"
|
Any other suggestions to go in there ?
Copied over some config files.
My /etc/mdadm.conf looks like :
| Code: |
MAILADDR root@localhost
#PROGRAM /user/sbin/handle-mdadm-events
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=(alpha numeric string)
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=(alpha numeric string)
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=(alpha numeric string)
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=(alpha numeric string)
|
So I copied that to the new system (will look up PROGRAM later) :
| Code: |
> cp -L /etc/mdadm.conf /mnt/gentoo/etc
> cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf
|
Mount proc and dev as per instructions the chroot in.
| Code: |
> chroot /mnt/gentoo /bin/bash
> env-update
> source /etc/profile
> export PS1="(chroot) $PS1"
> emerge --sync
|
I like the profile and didn't touch USE.
| Code: |
> emerge mdadm
> emerge raidtools
> emerge vixie-cron
> emerge dhcpcd
> emerge USE="-gtk" evms
> emerge slocate
> emerge syslog-ng
> emerge vim
|
Now for the fun bit ....
| Code: |
> USE="-doc symlink" emerge gentoo-sources
> ls -l /usr/src/linux
lrwxrwxrwx 1 root root 22 Dec 8 16:53 /usr/src/linux -> linux-2.6.18-gentoo-r4
> cd /usr/src/linux
> make menuconfig
|
In the kernal config I added :
| Code: |
Processor type and features ---> Processor family ---> AMD - Opteron/Athlon64
Multi-device support ---> <*> RAID support ---> RAID-1 (mirroring) mode
Multi-device support ---> <*> RAID support ---> Multipath I/O support
|
Built it :
| Code: |
> make && make modules_install
> cp arch/x86_64/boot/bzImage /boot/kernel-2.6.18-gentoo-r4
|
No kernel modules.
Set up /etc/fstab to this :
| Code: |
/dev/md1 /boot ext3 noauto,noatime 1 2
/dev/md3 / ext3 noatime 0 1
/dev/md2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9600 noauto 0 0
proc /proc proc noauto 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
|
Set up network and hostname.
Now the nemisis .....
| Code: |
> emerge grub
> grub --no-floppy
> grub
grub> find /boot/grub/stage1
find /boot/grub/stage1
(hd0,0)
(hd1,0)
grub> device (hd0) /dev/sda
device (hd0) /dev/sda
grub > root (hd0,0)
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
|
Even though I set it to ext3 ?
| Code: |
grub > setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded.
succeeded
Running "install /boot/grub/stage 1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"....
succeeded
Done.
grub> device (hd0) /dev/sdb
device (hd0) /dev/sdb
grub > root (hd0,0)
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
|
Even though I set it to ext3 ?
| Code: |
grub > setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded.
succeeded
Running "install /boot/grub/stage 1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"....
succeeded
Done.
grub > quit
|
SO......
should my "/boot/grub/grub.conf" be this :
| Code: |
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=My example Gentoo Linux
root (hd0,0)
kernel /boot/kernel-2.6.18-gentoo-r4 root=/dev/md3
|
and what else have I missed ? apart from :
| Code: |
exit
> cd
> umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo
> reboot
|
Please tell me !! I really don't want to have to do this all again or change distros !! |
|
| Back to top |
|
|
thedude0001
Arch/Herd Tester
Joined: 16 Jan 2005
Posts: 69
|
| Posted: Sun Dec 10, 2006 2:51 am Post subject: |
|
|
| JerryH wrote: |
I was using the raid that comes with the Asus A8N-E so the nForce4 Storage, actually building the raid in the bios, then using mdadm as per this wiki .
After searching and reading about it looks like the modo NVIDIA nForce4 Ultra RAID option was a waste and I should of just gone straight with kernel RAID, is that the accepted case ? |
Yeah, these "RAID" adapters are called "fakeraid" for a reason. Basically it just does a software RAID with its driver. That might be interesting under Windows where only the server versions support software RAID, in linux its not really sensible.
| Quote: |
I'll post mine here before I reboot to double check, though I'm sure I didn't have 1 lines for each hd, 2 in total |
grub itself won't access a raid device to boot a kernel (it can't do that), it accesses a partition. I added the second entry in case my sda fails, so I can boot from sdb. This is only used to load the kernel.
| Quote: | | Code: |
> emerge mdadm
> emerge raidtools
> emerge vixie-cron
> emerge dhcpcd
> emerge USE="-gtk" evms
> emerge slocate
> emerge syslog-ng
> emerge vim
|
|
No need for EVMS, you're using mdadm for the whole RAID management. Plus it's quite confusing (at least in my opinion). It's a powerful program, but you don't need it for what you're trying to do.
| Quote: |
Now the nemisis .....
| Code: |
> emerge grub
> grub --no-floppy
> grub
grub> find /boot/grub/stage1
find /boot/grub/stage1
(hd0,0)
(hd1,0)
grub> device (hd0) /dev/sda
device (hd0) /dev/sda
grub > root (hd0,0)
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
|
Even though I set it to ext3 ?
| Code: |
grub > setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded.
succeeded
Running "install /boot/grub/stage 1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"....
succeeded
Done.
grub> device (hd0) /dev/sdb
device (hd0) /dev/sdb
grub > root (hd0,0)
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
|
Even though I set it to ext3 ?
| Code: |
grub > setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded.
succeeded
Running "install /boot/grub/stage 1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"....
succeeded
Done.
grub > quit
|
|
I didn't know about the "device" command in the grub shell before, had to check the info pages for that. It seems to be ok, though I would just have used
| Code: | grub > root (hd0,0)
grub > setup (hd0)
grub > root (hd1,0)
grub > setup (hd1) |
But again, it seems to be ok the way you did it, just wanted to note it.
Ext3 is just a pimped-up ext2 with a journal added. You can mount an ext3 file system as ext2, it just won't use journaling then. That is why grub shows it as ext2. (You don't really need a journalling FS for your /boot/, ext2 would have been good enough as well.)
| Quote: |
SO......
should my "/boot/grub/grub.conf" be this :
| Code: |
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=My example Gentoo Linux
root (hd0,0)
kernel /boot/kernel-2.6.18-gentoo-r4 root=/dev/md3
|
|
Here is one error I spot. When you give grub the location of a file you have to give it the partition where it is on and the location on that partition. Your kernel is /boot/kernel-2.6.18-gentoo-r4. You have /dev/md1 mounted on /boot, so the "grub location" of your kernel is "(hd0,0)/kernel-2.6.18-gentoo-r4"
Your grub.conf should be like this:
| Code: |
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=My example Gentoo Linux
root (hd0,0)
kernel /kernel-2.6.18-gentoo-r4 root=/dev/md3
|
If you want to (in case of sda failing) be able to boot from sdb you should add another section to it:
| Code: |
title=My example Gentoo Linux booting from sdb
root (hd1,0)
kernel /kernel-2.6.18-gentoo-r4 root=/dev/md3 |
Everything else looks fine to me now. In case it still doesn't work and you again can't start / mount the RAID devices fro the live cd please give me the errors here, maybe we can get you through this without having to reinstall everything
One final note: It's not necessary to mirror your swap space. The best thing would be to make two normal swap partitions and add them both to your fstab. Linux will automatically stripe its swap usage over all partitions and get the best performance out of this. You should also add mdadm to your default runlevel. This isn't necessary for running the raid devces, but it will monitor them and mail you in case of failures.
_________________
Das Schlimme auf dieser Welt ist
daß die Dummen so selbstsicher sind
und die Gescheiten so voller Zweifel. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Sun Dec 10, 2006 3:15 am Post subject: |
|
|
Well thanks  With your help I've done it !!!! I'm one step away from n00b, albeit a small one.
Well the wasted $$ on the board hunting for RAID was stupid tax then ! Though at least I know now.
1) Swap is still mirrored, though seems ok, so just going to leave it now.
2) dsmeg says its coming up with sata in 1.5 G/sec I was expecting 3 G/sec.
3) find out how I can find where the old hd (had) has mounted itself. The 2nd drive from the dead server (reason I'm building this one) is ata, and I pluged it in as master IDE and it found it :
/var/log/dmesg
| Code: |
Probing IDE interface ide0...
hda: ST3160023A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hda: cache flushes supported
hda: hda1
|
And fdisk -l /dev/had gives me :
| Code: |
Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 19457 156288321 83 Linux
|
Though ......
| Code: |
> mkdir /mnt/tmp
> mount /dev/hda /mnt/tmp
mount: /dev/hda already mounted or /mnt/tmp busy
|
Any ideas there ?
I've installed some apps so I'm back to LAMP now
I've just got to "test" the raid, see if mdadm has a "status" etc.
I copied your grub set up to have the choice of which one in case it all goes wrong.
Thanks |
|
| Back to top |
|
|
thedude0001
Arch/Herd Tester
Joined: 16 Jan 2005
Posts: 69
|
| Posted: Sun Dec 10, 2006 3:55 am Post subject: |
|
|
Glad to see it's working. I don't think your tax was too high, since there is nearly no RAID hardware involved this shouldn't make a big difference at all...
The mirrored swap doesn't hurt, it's just a waste of space and performance.
I just checked your hardware, it looks like both the mainboard and the drives should be SATA2. so I don't know why dmesg is telling you it's using SATA1. Don't beat yourself up over it too much though, as the hardware of modern hdds can't handle more than 60-70MB/sec at best (might even be lower), so you won't feel a performance loss.
About the old hdd: Don't mount drives, mount partitions. Try mounting /dev/hda1 instead of hda
_________________
Das Schlimme auf dieser Welt ist
daß die Dummen so selbstsicher sind
und die Gescheiten so voller Zweifel. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Sun Dec 10, 2006 7:49 pm Post subject: |
|
|
| thedude0001 wrote: | Glad to see it's working. I don't think your tax was too high, since there is nearly no RAID hardware involved this shouldn't make a big difference at all...
The mirrored swap doesn't hurt, it's just a waste of space and performance.
I just checked your hardware, it looks like both the mainboard and the drives should be SATA2. so I don't know why dmesg is telling you it's using SATA1. Don't beat yourself up over it too much though, as the hardware of modern hdds can't handle more than 60-70MB/sec at best (might even be lower), so you won't feel a performance loss. |
No idea, maybe something in the kernel. I'm thinking now I've got this far its time to try and compilie a "tunned" kernel and playing with seeing if taking lots of things I don't need out helps ? Then I can boot with the "playing & test" kernel and back to the current working one for work on monday
| thedude0001 wrote: | | About the old hdd: Don't mount drives, mount partitions. Try mounting /dev/hda1 instead of hda |
Makes sense, not sure what I was thinking there !!
Is there a way of "probing" or "querying" a mount or drive to know where it is and what its doing ?
| Quote: |
> ls -l /mnt
total 20
drwx------ 2 root root 4096 Aug 3 02:22 cdrom
drwx------ 2 root root 4096 Aug 3 02:22 floppy
drwxr-xr-x 2 root root 4096 Dec 9 09:16 new
drwxr-xr-x 2 root root 4096 Dec 9 09:02 test
drwxr-xr-x 2 root root 4096 Dec 9 11:14 tmp
> mount /dev/hda1 /mnt/test
mount: /dev/hda1 already mounted or /mnt/test busy
|
Well at least i've gone from frustrated to learning a bunch of things, thanks |
|
| Back to top |
|
|
thedude0001
Arch/Herd Tester
Joined: 16 Jan 2005
Posts: 69
|
| Posted: Sun Dec 10, 2006 10:34 pm Post subject: |
|
|
A simple "mount" without any arguments will show you a list of what is mounted where.
_________________
Das Schlimme auf dieser Welt ist
daß die Dummen so selbstsicher sind
und die Gescheiten so voller Zweifel. |
|
| Back to top |
|
|
JerryH
n00b
Joined: 08 Dec 2006
Posts: 26
|
| Posted: Sun Dec 10, 2006 11:09 pm Post subject: |
|
|
Ahhh ......
| Code: |
/dev/md/3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85)
|
So its hiding some where ...... |
|
| Back to top |
|
|
Circuitsoft
Tux's lil' helper
Joined: 14 Jul 2004
Posts: 97
|
| Posted: Tue Apr 24, 2007 3:56 am Post subject: |
|
|
just typing "mount" will give you the contents of the file /etc/mtab. That file has to be updated when changes are made and it can get out of sync.
/proc/mounts contains a list of all mounts, but lacks information in the cases of loopback and some other mount conditions.
so |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on AMD64
