Hello

Since AstLinux only uses 60MB out of the 1GB card, I tried creating a new 
partition next to it:

========
# mount -o rw,remount /
# fdisk /dev/hda

Command (m for help): n
Command action
    e   extended
    p   primary partition (1-4)
p
Partition number (1-4): 2

First cylinder (131-1986, default 131):
Using default value 131
Last cylinder or +size or +sizeM or +sizeK (131-1986, default 1986): 400

Command (m for help): p
Disk /dev/hda: 1024 MB, 1024966656 bytes
16 heads, 63 sectors/track, 1986 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *           1         130       65488+  83  Linux
/dev/hda2             131         400      136080   83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or 
resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.

# fdisk -l /dev/hda

Disk /dev/hda: 1024 MB, 1024966656 bytes
16 heads, 63 sectors/track, 1986 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *           1         130       65488+  83  Linux
/dev/hda2             131         400      136080   83  Linux
======== reboot ===============
# mkdir /tmp/new_part
# ll /tmp/
-rw-r--r--    1 root     root         8192 Jan 21 18:53 astdb
drwxr-xr-x    2 root     root           40 Jan 21 18:52 bin
drwxr-xr-x    5 root     root          360 Jan 21 18:53 etc
-rw-r--r--    1 root     root          119 Jan 21 18:52 mod
-rw-r--r--    1 root     root           12 Jan 21 18:52 mydhcpip
drwxr-xr-x    2 root     root           40 Jan 21 18:57 new_part
drwxr-xr-x    3 root     root           60 Jan 21 18:53 root
drwx------    2 root     root           60 Jan 21 18:57 ssh-SveFmI1132
drwxr-xr-x    2 root     root           40 Jan 21 18:53 tftpboot

# mount /dev/hda2 /tmp/new_part
mount: Mounting /dev/hda2 on /tmp/new_part failed: Invalid argument
======== let's try in the / filesystem ===============
# mount -o rw,remount /
# mkdir /mnt/new_part
# mount /dev/hda2 /mnt/new_part/
mount: Mounting /dev/hda2 on /mnt/new_part/ failed: Invalid argument
# mount -o ro,remount /

# mount -t ext2fs /dev/hda2 /tmp/new_part/
mount: Mounting /dev/hda2 on /tmp/new_part/ failed: No such device
========

Google didn't return much about why mount can fail with "No such device". 
Does someone have a clue why AstLinux ain't happy?

Thank you.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to