Re: asrock, problem with nic after windows-boot - Mount Issues [Resolved]
- From: "iforone" <floydstestemail@xxxxxxxxx>
- Date: 11 Jun 2006 16:36:06 -0700
Bit Twister wrote:
On 11 Jun 2006 15:52:57 -0700, iforone wrote:
Like an idiot, I mounted hda1, when I needed to mount the whole hda
(all 3 win98 partitions)....but I *should* be able to just easily
umount it and remount the whole hda - but n-o-o-o :-( woe is me...
Then try this
mkdir /p1
mkdir /p2
mkdir /p3
mount -t auto /dev/hda1 /p1
mount -t auto /dev/hda2 /p2
mount -t auto /dev/hda3 /p3
ls /p1
ls /p2
ls /p3
Very Nice :-) Thanks a ton!
I did;
~$ sudo mkdir /mnt/p1
~$ sudo mkdir /mnt/p2
~$ sudo mkdir /mnt/p3
then;
$ sudo mount -t auto /dev/hda1 /mnt/p1
$ sudo mount -t auto /dev/hda5 /mnt/p2
$ sudo mount -t auto /dev/hda4 /mnt/p3
Then to verify - I did;
~$ ls -al /mnt/p1
~$ ls -al /mnt/p2
~$ ls -al /mnt/p3
and viewed the partitions within Konquerer -- YES
I think I'm wrong about KDE being the umount culprit though;
I wrote earlier;
Oh - I solved the mount issue it seems...It was stupid KDE - once I
closed it out, right before shutdown/reboot, I successfully umounted
hda1 - no more entry in /etc/mtab.
It seems I need to completely Logout of X (using Kmenu, Logout) and
then choose "Console Login" from kdm's menu, which enters one into text
mode only (runlevel2(?) or is it 1 in Debian(?)) -- anyway - from
there, I Login as 'root', supply passwd, then a 'umount' does the
trick;
# umount /dev/hda1
So ....do I understand that one mounts "partitions' only ?? One at a
time? On separate mount points? I understand that one mounts "file
systems*, not devices, as written in the 'man mount' pages -- nut do
you think because the Superblock is a bit munged, and/or b/c hda
contains multiple file systems - that I need to mount 'partitions'
only? and cannot mount the whole HD in one shot?
~$ sudo fdisk -l /dev/hda
Disk /dev/hda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1275 10241406 c W95 FAT32 (LBA)
/dev/hda2 1276 3188 15366172+ f W95 Ext'd (LBA)
/dev/hda3 3189 5620 19535040 83 Linux
/dev/hda4 5621 10011 35270707+ b W95 FAT32 <--
See Notations below
/dev/hda5 1276 3188 15366141 b W95 FAT32
[Notations]
This hda4 is a copy (and a Primary partition, as most know) of a win98
partition done while Debian installation - using it's "Copy partition"
feature - and note that I canNOT ScanDisk that partition (Scandskw.exe)
while in win98, nor DOS's version(Scandisk.exe) - it won't do it, it
complains of lack of RAM, and something else weird. Here's the thing
though, I can easily access (read / write) that partition's data (hda4)
while in booted into either Debian, -or- win98. I have that part
mounted right now, in Debian (as you can tell from my above 'mount'
commands - thanks to your advise :-))
Regards
.
- Follow-Ups:
- References:
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: iforone
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: Moe Trin
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: iforone
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: iforone
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- From: Bit Twister
- Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Prev by Date: Implementing a captive portal with iptables.
- Next by Date: Re: asrock, problem with nic after windows-boot - Mount Issues [Resolved]
- Previous by thread: Re: asrock, problem with nic after windows-boot - Exact Opposite issue the OP is having
- Next by thread: Re: asrock, problem with nic after windows-boot - Mount Issues [Resolved]
- Index(es):
Relevant Pages
|
