So it is fully ok
Why it is important as you already have one faulty disk, if you format the wrong disk, mdadm won't be able to build the raid
Jocko wrote:So it is fully ok
Why it is important as you already have one faulty disk, if you format the wrong disk, mdadm won't be able to build the raid
fdisk /dev/sde
enter: n -> 1 -> p -> 1 -> enter -> enter
then if you enter p you must see the new partition partition if it is ok enter w to save it.
enter again p you still must see the partition with type 83 and quit fdisk with q
mke2fs-ext3 -j -m 1 /dev/sde1
run udevstart again!
If you put the disk in an USB enclosure, you can connect it directly to the other Lacie, I guess. But I don't know if it has an interface to easy move/copy the files.pacco wrote:And 2 more questions. I have more than 1TB of data so I need to repeat the steps and how do I get the data to the other Lacie?
Mijzelf wrote:If you put the disk in an USB enclosure, you can connect it directly to the other Lacie, I guess. But I don't know if it has an interface to easy move/copy the files.pacco wrote:And 2 more questions. I have more than 1TB of data so I need to repeat the steps and how do I get the data to the other Lacie?
Command (m for help): n
Command action
e extended
p primary partition (1-4)
maybeyou don't need to backup all data? otherwise you need another disk and indeed repeat the sequence to save the remaining datapacco wrote:After that? And 2 more questions. I have more than 1TB of data so I need to repeat the steps and how do I get the data to the other Lacie?
mkdir /bckp
mount /dev/sde1 /bckp
ls /bckp
cp -r /pathtothefolder/foldername /
cp -r /pathtothefolder/foldername /pathto/destinationfolder/
I swapped the sequence:After fdisk /dev/sde I enter n and get this:
Code:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
root@fvdw-sta-kirkwood:/ # fdisk /dev/sde
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 121601.
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)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-121601, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-121601, default 121601): Using default value 121601
Command (m for help): p
Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 121601 976760001 83 Linux
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
root@fvdw-sta-kirkwood:/ # mke2fs-ext3 -j -m 1 /dev/sde1
mke2fs 1.41.14 (22-Dec-2010)
mke2fs-ext3: inode_size (128) * inodes_count (0) too big for a
filesystem with 0 blocks, specify higher inode_ratio (-i)
or lower inode count (-N).
fdisk -l /dev/sde1
Jocko wrote:check if you have really a partition sde1
- Code: Select all
fdisk -l /dev/sde1
root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sde1
Unknown value(s) for: cylinders (settable in the extra functions menu)
rm /dev/sde1
mknod -m 666 /dev/sde1 b 8 49
and check it
ls -l /dev/sde1
brw-rw-rw- 1 root root 8, 49 2015-05-18 17:13 /dev/sde1
Return to Lacie 5big Network vs2
Users browsing this forum: No registered users and 6 guests