lacie raid 1

Using PhotoRec to recover lost data
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Message
Author
peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#11 Post by peter1 » 25 May 2012, 01:28

peter@lonovo:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
--------------------------------------------------------------------------------------------------------------------
peter@lonovo:~$ sudo sfdisk -1uS
[sudo] password for peter:

Usage:
sfdisk [options] <device> [...]

Options:
-s, --show-size list size of a partition
-c, --id change or print partition Id
--change-id change Id
--print-id print Id
-l, --list list partitions of each device
-d, --dump idem, but in a format suitable for later input
-i, --increment number cylinders etc. from 1 instead of from 0
-u, --unit <letter> units to be used; <letter> can be one of
S (sectors), C (cylinders), B (blocks), or M (MB)
-1, --one-only reserved option that does nothing currently
-T, --list-types list the known partition types
-D, --DOS for DOS-compatibility: waste a little space
-E, --DOS-extended DOS extended partition compatibility
-R, --re-read make the kernel reread the partition table
-N <number> change only the partition with this <number>
-n do not actually write to disk
-O <file> save the sectors that will be overwritten to <file>
-I <file> restore sectors from <file>
-V, --verify check that the listed partitions are reasonable
-v, --version display version information and exit
-h, --help display this help text and exit

Dangerous options:
-f, --force disable all consistency checking
--no-reread do not check whether the partition is in use
-q, --quiet suppress warning messages
-L, --Linux do not complain about things irrelevant for Linux
-g, --show-geometry print the kernel's idea of the geometry
-G, --show-pt-geometry print geometry guessed from the partition table
-A, --activate[=<device>] activate bootable flag
-U, --unhide[=<dev>] set partition unhidden
-x, --show-extended also list extended partitions in the output,
or expect descriptors for them in the input
--leave-last do not allocate the last cylinder
--IBM same as --leave-last
--in-order partitions are in order
--not-in-order partitions are not in order
--inside-outer all logicals inside outermost extended
--not-inside-outer not all logicals inside outermost extended
--nested every partition is disjoint from all others
--chained like nested, but extended partitions may lie outside
--onesector partitions are mutually disjoint

Override the detected geometry using:
-C, --cylinders <number> set the number of cylinders to use
-H, --heads <number> set the number of heads to use
-S, --sectors <number> set the number of sectors to use

peter@lonovo:~$

Sponsored links

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#12 Post by peter1 » 25 May 2012, 05:37

peter@lonovo:~$ sudo sfdisk -1uS
[sudo] password for peter:

Usage:
sfdisk [options] <device> [...]

Options:
-s, --show-size list size of a partition
-c, --id change or print partition Id
--change-id change Id
--print-id print Id
-l, --list list partitions of each device
-d, --dump idem, but in a format suitable for later input
-i, --increment number cylinders etc. from 1 instead of from 0
-u, --unit <letter> units to be used; <letter> can be one of
S (sectors), C (cylinders), B (blocks), or M (MB)
-1, --one-only reserved option that does nothing currently
-T, --list-types list the known partition types
-D, --DOS for DOS-compatibility: waste a little space
-E, --DOS-extended DOS extended partition compatibility
-R, --re-read make the kernel reread the partition table
-N <number> change only the partition with this <number>
-n do not actually write to disk
-O <file> save the sectors that will be overwritten to <file>
-I <file> restore sectors from <file>
-V, --verify check that the listed partitions are reasonable
-v, --version display version information and exit
-h, --help display this help text and exit

Dangerous options:
-f, --force disable all consistency checking
--no-reread do not check whether the partition is in use
-q, --quiet suppress warning messages
-L, --Linux do not complain about things irrelevant for Linux
-g, --show-geometry print the kernel's idea of the geometry
-G, --show-pt-geometry print geometry guessed from the partition table
-A, --activate[=<device>] activate bootable flag
-U, --unhide[=<dev>] set partition unhidden
-x, --show-extended also list extended partitions in the output,
or expect descriptors for them in the input
--leave-last do not allocate the last cylinder
--IBM same as --leave-last
--in-order partitions are in order
--not-in-order partitions are not in order
--inside-outer all logicals inside outermost extended
--not-inside-outer not all logicals inside outermost extended
--nested every partition is disjoint from all others
--chained like nested, but extended partitions may lie outside
--onesector partitions are mutually disjoint

Override the detected geometry using:
-C, --cylinders <number> set the number of cylinders to use
-H, --heads <number> set the number of heads to use
-S, --sectors <number> set the number of sectors to use

peter@lonovo:~$ cat /proc/stat
cpu 2035 383 999 16516 2563 0 15 0 0 0
cpu0 2035 383 999 16516 2563 0 15 0 0 0
intr 39620 47 118 0 0 0 0 3 1 1 2 0 0 0 0 0 0 881 568 7988 2 0 0 16098 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 161 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 126479
btime 1337920023
processes 2189
procs_running 1
procs_blocked 0
softirq 49920 0 10384 39 244 16190 0 110 0 8 22945
peter@lonovo:~$

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#13 Post by peter1 » 25 May 2012, 05:40

raid 1 disk 2
------------------------------------------------------------------------------------

Thu May 24 17:42:30 2012
Command line: TestDisk

TestDisk 6.13, Data Recovery Utility, November 2011
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 3.2.0-23-generic-pae (#36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012) i686
Compiler: GCC 4.6
Compilation date: 2012-02-05T07:16:54
ext2fs lib: 1.42, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: none
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 156312576 sectors
/dev/sda: user_max 156312576 sectors
/dev/sda: native_max 156312576 sectors
/dev/sda: dco 156312576 sectors
/dev/sdb: LBA, HPA, LBA48, DCO support
/dev/sdb: size 976773168 sectors
/dev/sdb: user_max 976773168 sectors
/dev/sdb: native_max 976773168 sectors
/dev/sdb: dco 976773168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - CHS 1 1 1, sector size=512
Warning: can't get size for Disk /dev/md - 0 B - CHS 1 1 1 (RO), sector size=512
Hard disk list
Disk /dev/sda - 80 GB / 74 GiB - CHS 9730 255 63, sector size=512 - WDC WD800JD-08MSA1, S/N:WD-WMAM9WJ42031, FW:10.01E01
Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - ST3500620AS, S/N:9QM5Y4GD, FW:LC11

Partition table type (auto): Intel
Disk /dev/sdb - 500 GB / 465 GiB - ST3500620AS
Partition table type: Intel

Analyse Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63
Geometry from i386 MBR: head=255 sector=63

XFS Marker at 125/0/1
check_part_i386 failed for partition type 83
check_part_i386 failed for partition type 83
get_geometry_from_list_part_aux head=255 nbr=24
get_geometry_from_list_part_aux head=8 nbr=6
get_geometry_from_list_part_aux head=16 nbr=4
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=3
get_geometry_from_list_part_aux head=255 nbr=24
Current partition structure:
1 E extended 0 1 1 124 254 63 2008062
2 P Linux 125 0 1 60800 254 63 974759940
No partition is bootable
5 L Linux Swap 0 2 1 15 254 63 256914
X extended 16 0 1 16 254 63 16065
No ext2, JFS, Reiser, cramfs or XFS marker
6 L Linux 16 1 1 16 254 63 16002
6 L Linux 16 1 1 16 254 63 16002
X extended 17 0 1 17 254 63 16065
7 L Linux 17 1 1 17 254 63 16002
X extended 18 0 1 39 254 63 353430
8 L Linux 18 1 1 39 254 63 353367
X extended 40 0 1 123 254 63 1349460
9 L Linux 40 1 1 123 254 63 1349397
X extended 124 0 1 124 254 63 16065
No ext2, JFS, Reiser, cramfs or XFS marker
10 L Linux 124 1 1 124 254 63 16002
10 L Linux 124 1 1 124 254 63 16002
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0

search_part()
Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63
Linux Swap 0 2 1 15 252 27 256752
SWAP2 version 1, 131 MB / 125 MiB

Raid magic value at 15/252/44
Raid apparent size: 256768 sectors
Raid chunk size: 0 bytes
md126 md 0.90.0 Raid 4293967296: devices 0(8,21)*
Linux RAID 0 2 1 15 254 45 256896 [md126]
md 0.90.0 Raid 4293967296: devices 0(8,21)*, 131 MB / 125 MiB

recover_EXT2: s_block_group_nr=0/0, s_mnt_count=1/34, s_blocks_per_group=8192, s_inodes_per_group=1984
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 7936
recover_EXT2: part_size 15872
Linux 17 1 1 17 252 59 15872
EXT3 Sparse superblock, 8126 KB / 7936 KiB

Raid magic value at 17/252/60
Raid apparent size: 15872 sectors
Raid chunk size: 0 bytes
md124 md 0.90.0 Raid 4293967296: devices 0(8,23)*
Linux RAID 17 1 1 17 254 61 16000 [md124]
md 0.90.0 Raid 4293967296: devices 0(8,23)*, 8192 KB / 8000 KiB

recover_EXT2: s_block_group_nr=0/21, s_mnt_count=3/34, s_blocks_per_group=8192, s_inodes_per_group=2008
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 176576
recover_EXT2: part_size 353152
Linux 18 1 1 39 251 37 353152
EXT3 Sparse superblock, 180 MB / 172 MiB

Raid magic value at 39/251/38
Raid apparent size: 353152 sectors
Raid chunk size: 0 bytes
md125 md 0.90.0 Raid 4293967296: devices 0(8,24)*
Linux RAID 18 1 1 39 253 39 353280 [md125]
md 0.90.0 Raid 4293967296: devices 0(8,24)*, 180 MB / 172 MiB

recover_EXT2: s_block_group_nr=0/5, s_mnt_count=10/35, s_blocks_per_group=32768, s_inodes_per_group=14080
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 168656
recover_EXT2: part_size 1349248
Linux 40 1 1 123 252 40 1349248
EXT3 Sparse superblock Recover, 690 MB / 658 MiB

Raid magic value at 123/252/41
Raid apparent size: 1349248 sectors
Raid chunk size: 0 bytes
md2 md 0.90.0 Raid 4293967296: devices 0(8,25)*
Linux RAID 40 1 1 123 254 42 1349376 [md2]
md 0.90.0 Raid 4293967296: devices 0(8,25)*, 690 MB / 658 MiB

XFS Marker at 125/0/1

recover_xfs
Linux 125 0 1 121476 250 51 1949519616
XFS 6.2+ - bitmap version, 998 GB / 929 GiB
This partition ends after the disk limits. (start=2008125, size=1949519616, end=1951527740, disk end=976773168)

Raid magic value at 60800/252/58
Raid apparent size: 974759808 sectors
Raid chunk size: 0 bytes
md127 md 0.90.0 Raid 4293967296: devices 0(8,18)*
Linux RAID 125 0 1 60800 254 59 974759936 [md127]
md 0.90.0 Raid 4293967296: devices 0(8,18)*, 499 GB / 464 GiB
Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (500 GB / 465 GiB) seems too small! (< 999 GB / 930 GiB)
The following partition can't be recovered:
Linux 125 0 1 121476 250 51 1949519616
XFS 6.2+ - bitmap version, 998 GB / 929 GiB
get_geometry_from_list_part_aux head=255 nbr=10
get_geometry_from_list_part_aux head=8 nbr=4
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=255 nbr=10

Results
Linux Swap 0 2 1 15 254 63 256914
SWAP2 version 1, 131 MB / 125 MiB
Linux RAID 0 2 1 15 254 63 256914 [md126]
md 0.90.0 Raid 4293967296: devices 0(8,21)*, 131 MB / 125 MiB
Linux 17 1 1 17 254 63 16002
EXT3 Sparse superblock, 8193 KB / 8001 KiB
Linux RAID 17 1 1 17 254 63 16002 [md124]
md 0.90.0 Raid 4293967296: devices 0(8,23)*, 8193 KB / 8001 KiB
Linux 18 1 1 39 254 63 353367
EXT3 Sparse superblock, 180 MB / 172 MiB
Linux RAID 18 1 1 39 254 63 353367 [md125]
md 0.90.0 Raid 4293967296: devices 0(8,24)*, 180 MB / 172 MiB
Linux 40 1 1 123 254 63 1349397
EXT3 Sparse superblock Recover, 690 MB / 658 MiB
Linux RAID 40 1 1 123 254 63 1349397 [md2]
md 0.90.0 Raid 4293967296: devices 0(8,25)*, 690 MB / 658 MiB
* Linux RAID 125 0 1 60800 254 63 974759940 [md127]
md 0.90.0 Raid 4293967296: devices 0(8,18)*, 499 GB / 464 GiB

interface_write()
1 * Linux RAID 125 0 1 60800 254 63 974759940 [md127]

search_part()
Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63
Linux Swap 0 2 1 15 252 27 256752
SWAP2 version 1, 131 MB / 125 MiB

Raid magic value at 15/252/44
Raid apparent size: 256768 sectors
Raid chunk size: 0 bytes
md126 md 0.90.0 Raid 4293967296: devices 0(8,21)*
Linux RAID 0 2 1 15 254 45 256896 [md126]
md 0.90.0 Raid 4293967296: devices 0(8,21)*, 131 MB / 125 MiB

recover_EXT2: s_block_group_nr=0/0, s_mnt_count=1/34, s_blocks_per_group=8192, s_inodes_per_group=1984
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 7936
recover_EXT2: part_size 15872
Linux 17 1 1 17 252 59 15872
EXT3 Sparse superblock, 8126 KB / 7936 KiB

Raid magic value at 17/252/60
Raid apparent size: 15872 sectors
Raid chunk size: 0 bytes
md124 md 0.90.0 Raid 4293967296: devices 0(8,23)*
Linux RAID 17 1 1 17 254 61 16000 [md124]
md 0.90.0 Raid 4293967296: devices 0(8,23)*, 8192 KB / 8000 KiB

recover_EXT2: s_block_group_nr=0/21, s_mnt_count=3/34, s_blocks_per_group=8192, s_inodes_per_group=2008
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 176576
recover_EXT2: part_size 353152
Linux 18 1 1 39 251 37 353152
EXT3 Sparse superblock, 180 MB / 172 MiB

block_group_nr 3

recover_EXT2: "e2fsck -b 24577 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=3/21, s_mnt_count=0/34, s_blocks_per_group=8192, s_inodes_per_group=2008
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 176576
recover_EXT2: part_size 353152
Linux 18 1 1 39 251 37 353152
EXT3 Sparse superblock Backup superblock, 180 MB / 172 MiB

Raid magic value at 39/251/38
Raid apparent size: 353152 sectors
Raid chunk size: 0 bytes
md125 md 0.90.0 Raid 4293967296: devices 0(8,24)*
Linux RAID 18 1 1 39 253 39 353280 [md125]
md 0.90.0 Raid 4293967296: devices 0(8,24)*, 180 MB / 172 MiB

recover_EXT2: s_block_group_nr=0/5, s_mnt_count=10/35, s_blocks_per_group=32768, s_inodes_per_group=14080
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 168656
recover_EXT2: part_size 1349248
Linux 40 1 1 123 252 40 1349248
EXT3 Sparse superblock Recover, 690 MB / 658 MiB

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/5, s_mnt_count=9/35, s_blocks_per_group=32768, s_inodes_per_group=14080
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 168656
recover_EXT2: part_size 1349248
Linux 40 1 1 123 252 40 1349248
EXT3 Sparse superblock Backup superblock, 690 MB / 658 MiB

Raid magic value at 123/252/41
Raid apparent size: 1349248 sectors
Raid chunk size: 0 bytes
md2 md 0.90.0 Raid 4293967296: devices 0(8,25)*
Linux RAID 40 1 1 123 254 42 1349376 [md2]
md 0.90.0 Raid 4293967296: devices 0(8,25)*, 690 MB / 658 MiB

XFS Marker at 125/0/1

recover_xfs
Linux 125 0 1 121476 250 51 1949519616
XFS 6.2+ - bitmap version, 998 GB / 929 GiB
This partition ends after the disk limits. (start=2008125, size=1949519616, end=1951527740, disk end=976773168)

Raid magic value at 60800/252/58
Raid apparent size: 974759808 sectors
Raid chunk size: 0 bytes
md127 md 0.90.0 Raid 4293967296: devices 0(8,18)*
Linux RAID 125 0 1 60800 254 59 974759936 [md127]
md 0.90.0 Raid 4293967296: devices 0(8,18)*, 499 GB / 464 GiB
Disk /dev/sdb - 500 GB / 465 GiB - CHS 60801 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (500 GB / 465 GiB) seems too small! (< 999 GB / 930 GiB)
The following partition can't be recovered:
Linux 125 0 1 121476 250 51 1949519616
XFS 6.2+ - bitmap version, 998 GB / 929 GiB
get_geometry_from_list_part_aux head=255 nbr=10
get_geometry_from_list_part_aux head=8 nbr=4
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=255 nbr=10

Results
Linux Swap 0 2 1 15 254 63 256914
SWAP2 version 1, 131 MB / 125 MiB
Linux RAID 0 2 1 15 254 63 256914 [md126]
md 0.90.0 Raid 4293967296: devices 0(8,21)*, 131 MB / 125 MiB
Linux 17 1 1 17 254 63 16002
EXT3 Sparse superblock, 8193 KB / 8001 KiB
Linux RAID 17 1 1 17 254 63 16002 [md124]
md 0.90.0 Raid 4293967296: devices 0(8,23)*, 8193 KB / 8001 KiB
Linux 18 1 1 39 254 63 353367
EXT3 Sparse superblock, 180 MB / 172 MiB
Linux RAID 18 1 1 39 254 63 353367 [md125]
md 0.90.0 Raid 4293967296: devices 0(8,24)*, 180 MB / 172 MiB
Linux 40 1 1 123 254 63 1349397
EXT3 Sparse superblock Recover, 690 MB / 658 MiB
Linux RAID 40 1 1 123 254 63 1349397 [md2]
md 0.90.0 Raid 4293967296: devices 0(8,25)*, 690 MB / 658 MiB
* Linux RAID 125 0 1 60800 254 63 974759940 [md127]
md 0.90.0 Raid 4293967296: devices 0(8,18)*, 499 GB / 464 GiB

interface_write()
1 * Linux RAID 125 0 1 60800 254 63 974759940 [md127]
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

TestDisk exited normally.

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#14 Post by peter1 » 25 May 2012, 05:45

raid 1 disk 2
--------------------------------------------------------------------------------------------------------------
peter@lonovo:~$ sudo mdadm --examine /dev/sdb1
[sudo] password for peter:
/dev/sdb1:
MBR Magic : aa55
Partition[0] : 256914 sectors at 63 (type 82)
Partition[1] : 16065 sectors at 256977 (type 05)
peter@lonovo:~$

-----------------------------------------------------------------------------------------------------------
peter@lonovo:~$ sudo sfdisk -1uS

Usage:
sfdisk [options] <device> [...]

Options:
-s, --show-size list size of a partition
-c, --id change or print partition Id
--change-id change Id
--print-id print Id
-l, --list list partitions of each device
-d, --dump idem, but in a format suitable for later input
-i, --increment number cylinders etc. from 1 instead of from 0
-u, --unit <letter> units to be used; <letter> can be one of
S (sectors), C (cylinders), B (blocks), or M (MB)
-1, --one-only reserved option that does nothing currently
-T, --list-types list the known partition types
-D, --DOS for DOS-compatibility: waste a little space
-E, --DOS-extended DOS extended partition compatibility
-R, --re-read make the kernel reread the partition table
-N <number> change only the partition with this <number>
-n do not actually write to disk
-O <file> save the sectors that will be overwritten to <file>
-I <file> restore sectors from <file>
-V, --verify check that the listed partitions are reasonable
-v, --version display version information and exit
-h, --help display this help text and exit

Dangerous options:
-f, --force disable all consistency checking
--no-reread do not check whether the partition is in use
-q, --quiet suppress warning messages
-L, --Linux do not complain about things irrelevant for Linux
-g, --show-geometry print the kernel's idea of the geometry
-G, --show-pt-geometry print geometry guessed from the partition table
-A, --activate[=<device>] activate bootable flag
-U, --unhide[=<dev>] set partition unhidden
-x, --show-extended also list extended partitions in the output,
or expect descriptors for them in the input
--leave-last do not allocate the last cylinder
--IBM same as --leave-last
--in-order partitions are in order
--not-in-order partitions are not in order
--inside-outer all logicals inside outermost extended
--not-inside-outer not all logicals inside outermost extended
--nested every partition is disjoint from all others
--chained like nested, but extended partitions may lie outside
--onesector partitions are mutually disjoint

-------------------------------------------------------------------------------------------------------------------------
Override the detected geometry using:
-C, --cylinders <number> set the number of cylinders to use
-H, --heads <number> set the number of heads to use
-S, --sectors <number> set the number of sectors to use

peter@lonovo:~$ cat /proc/stat
cpu 81662 636 47255 946538 242795 3 5536 0 0 0
cpu0 81662 636 47255 946538 242795 3 5536 0 0 0
intr 3125439 91 352 0 0 0 0 3 1 1 2 0 0 0 0 0 0 879 10062 516868 2 0 0 1685650 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2155 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 8447099
btime 1337906261
processes 2439
procs_running 3
procs_blocked 0
softirq 3161630 0 531816 2670 2333 1685805 0 323 0 1120 937563
peter@lonovo:~$

User avatar
remy
Posts: 457
Joined: 25 Mar 2012, 10:21
Location: Strasbourg, France.
Contact:

Re: lacie raid 1

#15 Post by remy » 25 May 2012, 17:29

Code: Select all

sudo sfdisk -luS
with "L" in "luS", not 1.

Code: Select all

cat /proc/mdstat
not proc/stat.

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#16 Post by peter1 » 27 May 2012, 04:50

i installed both drives in the computer so sdb and sdc are the raid drives, i notice there is a difference has sdb failed and sdc the good drive since there is more on it? i hope this helps?
-----------------------------------------------------------------------------------------------------------------

Code: Select all

peter@lonovo:~$ sudo sfdisk -luS
[sudo] password for peter: 

Disk /dev/sda: 9730 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sda1          2048  10065919   10063872  27  Hidden NTFS WinRE
/dev/sda2   *  10065920 140980856  130914937   7  HPFS/NTFS/exFAT
/dev/sda3     140982270 156311551   15329282   5  Extended
/dev/sda4             0         -          0   0  Empty
/dev/sda5     140982272 155396095   14413824  83  Linux
/dev/sda6     155398144 156311551     913408  82  Linux swap / Solaris

Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sdb1   *    642663   1992059    1349397  fd  Linux raid autodetect
/dev/sdb2             0         -          0   0  Empty
/dev/sdb3             0         -          0   0  Empty
/dev/sdb4             0         -          0   0  Empty

Disk /dev/sdc: 60801 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sdc1            63   2008124    2008062   5  Extended
/dev/sdc2       2008125 976768064  974759940  83  Linux
/dev/sdc3             0         -          0   0  Empty
/dev/sdc4             0         -          0   0  Empty
/dev/sdc5           126    257039     256914  82  Linux swap / Solaris
/dev/sdc6        257103    273104      16002  83  Linux
/dev/sdc7        273168    289169      16002  83  Linux
/dev/sdc8        289233    642599     353367  83  Linux
/dev/sdc9        642663   1992059    1349397  83  Linux
/dev/sdc10      1992123   2008124      16002  83  Linux
peter@lonovo:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
unused devices: <none>
peter@lonovo:~$ 

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#17 Post by peter1 » 27 May 2012, 04:54

i also tried this

Code: Select all

peter@lonovo:~$ sudo mdadm --assemble -scan
[sudo] password for peter: 
mdadm: WARNING /dev/sdc9 and /dev/sdc8 appear to have very similar superblocks.
      If they are really different, please --zero the superblock on one
      If they are the same or overlap, please remove one from the
      DEVICE list in mdadm.conf.
mdadm: No arrays found in config file or automatically

User avatar
remy
Posts: 457
Joined: 25 Mar 2012, 10:21
Location: Strasbourg, France.
Contact:

Re: lacie raid 1

#18 Post by remy » 27 May 2012, 13:16

As far as it should have been a raid1, either you've made deep transformations, or a drive is really corrupted. sdc and sdb must be equal.

I don't know why you have so much partition on sdc.

Please give feedback :

Code: Select all

sudo blkid

peter1
Posts: 13
Joined: 21 May 2012, 15:50

Re: lacie raid 1

#19 Post by peter1 » 30 May 2012, 03:45

The 2big Network is running a Linux operating system with XFS file system

User avatar
remy
Posts: 457
Joined: 25 Mar 2012, 10:21
Location: Strasbourg, France.
Contact:

Re: lacie raid 1

#20 Post by remy » 30 May 2012, 23:18

I know that. mdadm based. What's the return of blkid ?

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 3 guests