Re: Disk partitioning - Suse 10.2

Odie Ferrous wrote:


I own a data recovery company; it's not the concept of partitions and
filesystems that's baffling me - it's the foreign language that is
Linux! And recovering Linux partitions is very, very different (to me)
from working with the Linux OS itself.

I really should spend more time with a decent manual. The book I have
(Linux for Dummies) doesn't have much to say about partitioning, other
than at original setup.

Anyway, I did set the mount point to /mnt as you suggested. Then I
pressed the "apply" button.

It screamed all the way to 0% and now the system has hung. Again.


Odie

Hi Odie,

Forget the GUI tools - they seem to be adding inexplicable complications.

Ian proffered nearly the easiest way to do it - though we can remove a step
at a pinch:

1) Add drive to your system. Ascertain what it's called (eg /dev/sdb
or /dev/hdb or whatever. To verify this do:

cat /sys/block/sda/device/model

and see if you get back the drives model number, eg "ST380013AS" in my case.
Change "sda" to sdb, sdc, sdd (These for SATA and SCSI) or hda, hdb, hdc,
hdd (for PATA IDE) until the model number matches the 500GB disk.

2) Become root in a terminal window, and change "sda" in all following code
to be whatever you just found in step 1.

Then:

mkfs.ext3 /dev/sda
mkdir /mnt/newdisk
mount /dev/sda /mnt/newdisk
cp -av /data/clients-recovered-raid/. /mnt/newdisk/
umount /mnt/newdisk

job done...

You do not *need* to partition a block device - you may put a filesystem
onto the whole device, so that cuts out a degree of explanation.

On a previous question, yes, you always need a mount point (with one
exception) to make a filesystem useful. Unix has no drive letters -
everything appears under /

In the above, we made a temporary mount point (any directory can be a mount
point, generally). Some tools like "pmount" or KDE or some other
automounting subsytems may make their own mount points on demand, but there
will always be one.

HTH

Tim
.

Quantcast