[conspire] having trouble getting 2nd partition formatted with GNU parted

Darlene Wallach freepalestin at dslextreme.com
Thu Apr 1 18:09:06 PDT 2010


I unmounted /dev/sdb:
# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                       36G   34G  600M  99% /
/dev/sda1             190M   49M  132M  28% /boot
tmpfs                 243M  2.8M  241M   2% /dev/shm

# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

Here is my attempt to set up two partitions on the Seagate FreeAgent
Go 1T drive.
Partiton 1 gets setup - notice even though I said to start at "0",
parted started at "17.4kB".
Partition 2 - I get errors - I don't understand what I'm doing wrong.
Should I shutdown, reboot and try again for partition 2?
Does someone see what I'm doing wrong for partition 2?

# parted /dev/sdb
GNU Parted 1.8.8
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
parted: invalid token: gpt
Yes/No? yes
New disk label type?  [gpt]?
(parted) print
Model: Seagate FreeAgent Go (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End  Size  File system  Name  Flags

(parted) mkpart primary ext3 0 960GB
(parted) name 1 Wallach1TData
(parted) print
Model: Seagate FreeAgent Go (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End    Size   File system  Name           Flags
 1      17.4kB  960GB  960GB               Wallach1TData  msftres

(parted) mkpart primary ext3 960GB 1000GB
Error: Error informing the kernel about modifications to partition /dev/sdb2 --
Device or resource busy.  This means Linux won't know about any changes you made
to /dev/sdb2 until you reboot -- so you shouldn't mount it or use it in any way
before rebooting.
Ignore/Cancel? c
Warning: The kernel was unable to re-read the partition table on /dev/sdb
(Device or resource busy).  This means Linux won't know anything about the
modifications you made until you reboot.  You should reboot your computer before
doing anything with /dev/sdb.
(parted)

Thank you

Darlene Wallach
-- 
equal justice under law




More information about the conspire mailing list