Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Mount Secondary H.D.D

[persianwhois]

Hi,

I wish to mount secondary H.D.D to /backup, but i have following error after run "mount /dev/sdb1 backup"

mount: unknown filesystem type 'ntfs'

How can change secondary hard disk file system to linux?

Thanks

[Patrick]

What file system is /dev/sdb1 currently using? (I know it says ntfs, but I figured I would ask first...)

[RoseHosting]

Try "mount -t ntfs /dev/sdb1 /backup"

Also, check if you have "ntfs" modules installed.

Finaly, you can install QtParted (http://qtparted.sourceforge.net/) it is a GUI partition manager, and after that you will be able to do whatever you want with your HDD, like, change size, number of partitions, size of partitions, type of partitions etc....

Originally Posted by persianwhois

Hi,

I wish to mount secondary H.D.D to /backup, but i have following error after run "mount /dev/sdb1 backup"

mount: unknown filesystem type 'ntfs'

How can change secondary hard disk file system to linux?

Thanks

[persianwhois]

We have "mount: unknown filesystem type 'ntfs'" when try to mount by "mount -t ntfs /dev/sdb1 /backup"

How can fix this issue?

[Xous]

Depending on you distribution you may either need recompile your kernel or download the correct module binary for your kernel.

I suggest try searching google for something like "[distribution] ntfs module" for instructions.

If you do not need to get any data off of the device you can simply change the partition type with fdisk or cfdisk and then format it with the appropriate linux file system such i.e. mkfs.ext3 /dev/sdb1.

[gigatux]

From memory, I believe the standard ntfs module only allows read only access to the filesystem in question. I think something like ntfs-3g (supplied with many modern distributions) will handle read/write access to NTFS partitions.

[persianwhois]

How can chage /dev/sdb1 file system to linux?

[gigatux]

Run fdisk (as root - BE VERY CAREFUL) on /dev/sdb. Change the filesystem type to Linux (83) and then rewrite the partition table. You will lose all data on that partition.

Then, choose your filesystem. To keep things simple, let's say you choose ext3. Type mkfs.ext3 /dev/sdb1. It will then start creating the file system.

Et viola. I recommend you read up a lot more on this subject before as you run a big risk of destroying data.

[persianwhois]

We have:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        6540    52428127+  83  Linux
/dev/sda3            6541        7062     4192965   82  Linux swap / Solaris
/dev/sda4            7063       60801   431658517+   5  Extended
/dev/sda5            7063        8368    10490413+  83  Linux
/dev/sda6            8369       10322    15695473+  83  Linux
/dev/sda7           10323       10710     3116578+  83  Linux
/dev/sda8           10711       23800   105145393+  83  Linux
/dev/sda9           23801       60801   297210501   83  Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       30400   244187968+   7  HPFS/NTFS

250.0GB do not have any useful data and its not problem to loss data.
But we have many important data on 500.1GB and need to save this.

Is it possibility to loss 500gb H.D.D after i run "fdisk /dev/sdb"?
Help me please.

[gigatux]

Originally Posted by persianwhois

Is it possibility to loss 500gb H.D.D after i run "fdisk /dev/sdb"?

If you're definitely typing in fdisk /dev/sdb, no, there is no way to lose data from /dev/sda using this. Usual disclaimer applies though.

[persianwhois]

What i must doing now?

root@server [~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 30401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

[gigatux]

I'm sure you'll be able to figure it out with a little Googling now. Try sites such as http://tldp.org/HOWTO/Partition/fdisk_partitioning.html