[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Disk /dev/md6 doesn't contain valid partition table



On Wed, Oct 29, 2008 at 7:06 AM, Douglas A. Tutty <dtutty@vianet.ca> wrote:
> On Wed, Oct 29, 2008 at 05:44:31AM +0100, Francesco Pietra wrote:
>> Major mistake (shutting down the ups unit) while doing a parallel
>> computation on all 8 processors (UMA-type machine amd64 lenny with
>> raid 1 two disks).
>>
>> On restarting the machine and the computation,
>>
>> "fdisk -l" showed
>>  "Disk /dev/md6 doesn't contain a valid partition table"
>>
>>
>> "df -h" showed
>> 97G 1.1G 91G 2% /home
>> (which should have been ca 70% used).
>>
>> All other partitions were OK, as they should be.
>
> It would help us to follow if you provided a map of device to
> mount-point since, e.g. whe don't know what device is /home.

As from my raid1 setup documantation:

md 6 is /home/francesco/

md5 is /tmp

Any command to check the above from the present status?
====
In present status;

"cat /proc/mdstat:
Personalities : [raid1]
md6 : active raid1 sda8[0] sdb8[1]
      102341952 blocks [2/2] [UU]

md5 : active raid1 sda7[0] sdb7[1]
      1951744 blocks [2/2] [UU]

md4 : active raid1 sda6[0] sdb6[1]
      2931712 blocks [2/2] [UU]

md3 : active raid1 sda5[0] sdb5[1]
      14651136 blocks [2/2] [UU]

md1 : active(auto-read-only) raid1 sda2[0] sdb2[1]
      6835584 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
      2931712 blocks [2/2] [UU]

md2 : active raid1 sda3[0] sdb3[1]
      14651200 blocks [2/2] [UU]

unused devices: <none>
=========
"fdisk -l":
Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009e776

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         365     2931831   fd  Linux raid autodetect
/dev/sda2             366        1216     6835657+  fd  Linux raid autodetect
/dev/sda3            1217        3040    14651280   fd  Linux raid autodetect
/dev/sda4            3041       18213   121877122+   5  Extended
/dev/sda5            3041        4864    14651248+  fd  Linux raid autodetect
/dev/sda6            4865        5229     2931831   fd  Linux raid autodetect
/dev/sda7            5230        5472     1951866   fd  Linux raid autodetect
/dev/sda8            5473       18213   102342051   fd  Linux raid autodetect

Disk /dev/sdb: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b05ba

   Device BootDisk /dev/md2 doesn't contain a valid partition table
Disk /dev/md0 doesn't contain a valid partition table
      Start         End      Blocks   Id  System
/dev/sdb1   *           1         365     2931831   fd  Linux raid autodetect
/dev/sdb2             366        1216     6835657+  fd  Linux raid autodetect
/dev/sdb3            1217        3040    14651280   fd  Linux raid autodetect
/dev/sdb4            3041       18213   121877122+   5  Extended
/dev/sdb5            3041        4864    14651248+  fd  Linux raid autodetect
/dev/sdb6            4865        5229     2931831   fd  Linux raid autodetect
/dev/sdb7            5230        5472     1951866   fd  Linux raid autodetect
/dev/sdb8            5473       18213   102342051   fd  Linux raid autodetect

Disk /dev/md2: 15.0 GB, 15002828800 bytes
2 heads, 4 sectors/track, 3662800 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md0: 3002 MB, 3002073088 bytes
2 heads, 4 sectors/track, 732928 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md1: 6999 MB, 6999638016 bytes
2 heads,Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/md4 doesn't contain a valid partition table
Disk /dev/md5 doesn't contain a valid partition table
Disk /dev/md6 doesn't contain a valid partition table
 4 sectors/track, 1708896 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md3: 15.0 GB, 15002763264 bytes
2 heads, 4 sectors/track, 3662784 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md4: 3002 MB, 3002073088 bytes
2 heads, 4 sectors/track, 732928 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md5: 1998 MB, 1998585856 bytes
2 heads, 4 sectors/track, 487936 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000


Disk /dev/md6: 104.7 GB, 104798158848 bytes
2 heads, 4 sectors/track, 25585488 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000
===================


>
>>  "top -i" showed
>> all 8 instances fo the parallel procedure
>> md6_resync (CPU% 6)
>> md5_resync (CPU% 0)
>> kjournald
>>
>>
>> After some time md6_resync, md5_resync, kjournald disappeared, leaving
>> only the 8 parallel procedures.
>>
>> Commanding "cat density6.out" the parallel procedure seems to work
>> regularly, confirmed by "la -l" which shows all files (some as large
>> as 100MB) for the present computation and the 5 analogous computations
>> already carried out (of these five computations I had scp sent a copy
>> to my desktop).
>>
>> Where are the data for the current 6th computation being stored?
>>
>> The computer was then shutdown and restarted
>>
>> df -h output as above.
>>
>> fdisk -l
>> Neither /dev/md6 nor /dev/md5 have a valid partition table.
>>
>> cd to my home shows all directories and files for work (in my home
>> only data from computations, all applications installed in
>> /usr/local).
>>
>> What could I do to set up the system in order before resuming the computation?
>
>
> I don't suppose that you kept a copy  of your partition table as part of
> your backup script?  e.g. /sbin/sfdisk -d <device>?

Unfortunately not. I take notice of this for the future

Thanks
francesco
>
> If so, you can write it back.
>
> Doug.
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


Reply to: