[ubuntu-za] Fwd: HEEEELLLPPP!!! raid 5
frans
dormakorp at vodamail.co.za
Fri Apr 30 14:54:16 BST 2010
-------- Original Message --------
Subject: HEEEELLLPPP!!! raid 5
Date: Fri, 30 Apr 2010 15:13:52 +0200
From: frans <dormakorp at vodamail.co.za>
To: glug-tech at linux.org.za
a quick update runing
dumpe2fs /dev/md0
give some feed back like
*Group 1116: (Blocks 36569088-36601855)
Block bitmap at 36569088 (+0), Inode bitmap at 36569089 (+1)
Inode table at 36569090-36569345 (+2)
2 free blocks, 7844 free inodes, 89 directories
Free blocks: 36569346-36569347
Free inodes: 9142621-9150464
Group 1117: (Blocks 36601856-36624127)
Block bitmap at 36601856 (+0), Inode bitmap at 36601857 (+1)
Inode table at 36601858-36602113 (+2)
6 free blocks, 7362 free inodes, 230 directories
Free blocks: 36601856-36634623
Free inodes: 9150465-9158656*
it would seem all is not lost... the filesystem does however seem to be
corupted is was still ext3
I try being more complete this time.
some backgorund
Ive added a few disks to my raid5 array this monday, and totld the
system to grow the array, to include these
yesterday there was an update to mdadm which i installed...
this morning, after a reboot lastnight, my raid server (ubuntu 8.04) did
not show the /dev/md0 device,
so being hasty and not thinking clearly that early in the morning I
created a new device (using webmin)
imediatly after realizing my error i go on to remove them one by one...
now the system will not create the raid...
this i got fixed after leaving the culprit drive out, finding a site
saying that the error on the drive can be fixed via fsdisk, by writing
to the disk (no changes made)
at the moment what i get with mount is:
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
and e2fsck
*root at raidserver:/home/frans# e2fsck /dev/md0
e2fsck 1.40.8 (13-Mar-2008)
e2fsck: Group descriptors look bad... trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/md0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>*
and
*root at raidserver:/home/frans# e2fsck -f -b 32768 /dev/md0
e2fsck 1.40.8 (13-Mar-2008)
e2fsck: Device or resource busy while trying to open /dev/md0
Filesystem mounted or opened exclusively by another program?*
log files
*kernel and message seems the same
*
*Apr 29 20:00:49 raidserver kernel: [ 23.784304] ata1: SATA max UDMA/100 mmio m1024 at 0xfebffc00 tf 0xfebffc80 irq 16
Apr 29 20:00:49 raidserver kernel: [ 23.784308] ata2: SATA max UDMA/100 mmio m1024 at 0xfebffc00 tf 0xfebffcc0 irq 16
Apr 29 20:00:49 raidserver kernel: [ 23.784311] ata3: SATA max UDMA/100 mmio m1024 at 0xfebffc00 tf 0xfebffe80 irq 16
Apr 29 20:00:49 raidserver kernel: [ 23.784313] ata4: SATA max UDMA/100 mmio m1024 at 0xfebffc00 tf 0xfebffec0 irq 16
Apr 29 20:00:49 raidserver kernel: [ 24.267025] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 29 20:00:49 raidserver kernel: [ 24.334793] ata1.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 24.334797] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 24.418065] ata1.00: configured for UDMA/100
Apr 29 20:00:49 raidserver kernel: [ 24.906749] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 29 20:00:49 raidserver kernel: [ 24.970022] ata2.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 24.970027] ata2.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 25.061625] ata2.00: configured for UDMA/100
Apr 29 20:00:49 raidserver kernel: [ 25.546485] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 29 20:00:49 raidserver kernel: [ 25.610418] ata3.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 25.610423] ata3.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 25.693691] ata3.00: configured for UDMA/100
Apr 29 20:00:49 raidserver kernel: [ 26.176224] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 29 20:00:49 raidserver kernel: [ 26.247457] ata4.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 26.247461] ata4.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 26.339056] ata4.00: configured for UDMA/100
Apr 29 20:00:49 raidserver kernel: [ 26.339194] scsi 0:0:0:0: Direct-Access ATA ST380815AS 4.AA PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 26.339643] scsi 1:0:0:0: Direct-Access ATA ST380815AS 4.AA PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 26.340016] scsi 2:0:0:0: Direct-Access ATA ST380815AS 4.AA PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 26.340394] scsi 3:0:0:0: Direct-Access ATA ST380815AS 4.AA PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 26.340807] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 20
Apr 29 20:00:49 raidserver kernel: [ 26.340836] PCI: Setting latency timer of device 0000:00:1f.1 to 64
Apr 29 20:00:49 raidserver kernel: [ 26.340846] ACPI: PCI interrupt for device 0000:00:1f.1 disabled
Apr 29 20:00:49 raidserver kernel: [ 26.340868] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
Apr 29 20:00:49 raidserver kernel: [ 26.340885] PCI: Setting latency timer of device 0000:00:1f.2 to 64
Apr 29 20:00:49 raidserver kernel: [ 26.340893] ACPI: PCI interrupt for device 0000:00:1f.2 disabled
Apr 29 20:00:49 raidserver kernel: [ 26.344219] ata_piix 0000:00:1f.1: version 2.12
Apr 29 20:00:49 raidserver kernel: [ 26.344235] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 20
Apr 29 20:00:49 raidserver kernel: [ 26.344265] PCI: Setting latency timer of device 0000:00:1f.1 to 64
Apr 29 20:00:49 raidserver kernel: [ 26.345361] scsi4 : ata_piix
Apr 29 20:00:49 raidserver kernel: [ 26.345864] scsi5 : ata_piix
Apr 29 20:00:49 raidserver kernel: [ 26.346839] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
Apr 29 20:00:49 raidserver kernel: [ 26.346842] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
Apr 29 20:00:49 raidserver kernel: [ 26.355134] Driver 'sd' needs updating - please use bus_type methods
Apr 29 20:00:49 raidserver kernel: [ 26.355204] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.355215] sd 0:0:0:0: [sda] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.355217] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.355231] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.355276] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.355285] sd 0:0:0:0: [sda] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.355287] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.355301] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.355304] sda: sda1
Apr 29 20:00:49 raidserver kernel: [ 26.372830] sd 0:0:0:0: [sda] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 26.372905] sd 1:0:0:0: [sdb] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.372920] sd 1:0:0:0: [sdb] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.372924] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.372944] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.372996] sd 1:0:0:0: [sdb] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.373008] sd 1:0:0:0: [sdb] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.373012] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.373041] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.373044] sdb: sdb1
Apr 29 20:00:49 raidserver kernel: [ 26.391919] sd 1:0:0:0: [sdb] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 26.391985] sd 2:0:0:0: [sdc] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.391999] sd 2:0:0:0: [sdc] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.392002] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.392023] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.392077] sd 2:0:0:0: [sdc] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.392090] sd 2:0:0:0: [sdc] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.392093] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.392113] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.392117] sdc: sdc1
Apr 29 20:00:49 raidserver kernel: [ 26.416177] sd 2:0:0:0: [sdc] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 26.416239] sd 3:0:0:0: [sdd] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.416253] sd 3:0:0:0: [sdd] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.416257] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.416277] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.416327] sd 3:0:0:0: [sdd] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 26.416340] sd 3:0:0:0: [sdd] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 26.416343] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 26.416363] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 26.416368] sdd: sdd1
Apr 29 20:00:49 raidserver kernel: [ 26.437052] sd 3:0:0:0: [sdd] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 26.449688] sd 0:0:0:0: Attached scsi generic sg0 type 0
Apr 29 20:00:49 raidserver kernel: [ 26.449707] sd 1:0:0:0: Attached scsi generic sg1 type 0
Apr 29 20:00:49 raidserver kernel: [ 26.449724] sd 2:0:0:0: Attached scsi generic sg2 type 0
Apr 29 20:00:49 raidserver kernel: [ 26.449740] sd 3:0:0:0: Attached scsi generic sg3 type 0
Apr 29 20:00:49 raidserver kernel: [ 26.661676] md: md0 stopped.
Apr 29 20:00:49 raidserver kernel: [ 26.677346] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
Apr 29 20:00:49 raidserver kernel: [ 26.677366] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
Apr 29 20:00:49 raidserver kernel: [ 26.677396] PCI: Setting latency timer of device 0000:00:1f.2 to 64
Apr 29 20:00:49 raidserver kernel: [ 26.687374] scsi6 : ata_piix
Apr 29 20:00:49 raidserver kernel: [ 26.690184] scsi7 : ata_piix
Apr 29 20:00:49 raidserver kernel: [ 26.691354] ata7: SATA max UDMA/133 cmd 0xc080 ctl 0xc000 bmdma 0xb800 irq 19
Apr 29 20:00:49 raidserver kernel: [ 26.691357] ata8: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb808 irq 19
Apr 29 20:00:49 raidserver kernel: [ 26.710372] md: md0 stopped.
Apr 29 20:00:49 raidserver kernel: [ 26.725888] md: md0 stopped.
Apr 29 20:00:49 raidserver kernel: [ 26.913663] ata7.00: ATA-7: ST380815AS, 4.AAB, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 26.913668] ata7.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 26.996947] ata7.00: configured for UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 27.176357] ata8.00: ATA-8: WDC WD1600AAJS-00L7A0, 01.03E01, max UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 27.176362] ata8.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 29 20:00:49 raidserver kernel: [ 27.196383] ata8.00: configured for UDMA/133
Apr 29 20:00:49 raidserver kernel: [ 27.196521] scsi 6:0:0:0: Direct-Access ATA ST380815AS 4.AA PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 27.196924] sd 6:0:0:0: [sde] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 27.196935] sd 6:0:0:0: [sde] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 27.196937] sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 27.196951] sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 27.196996] sd 6:0:0:0: [sde] 156301488 512-byte hardware sectors (80026 MB)
Apr 29 20:00:49 raidserver kernel: [ 27.197005] sd 6:0:0:0: [sde] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 27.197007] sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 27.197020] sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 27.197024] sde: sde1 sde2< sde5>
Apr 29 20:00:49 raidserver kernel: [ 27.242646] sd 6:0:0:0: [sde] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 27.242692] sd 6:0:0:0: Attached scsi generic sg4 type 0
Apr 29 20:00:49 raidserver kernel: [ 27.243488] scsi 7:0:0:0: Direct-Access ATA WDC WD1600AAJS-0 01.0 PQ: 0 ANSI: 5
Apr 29 20:00:49 raidserver kernel: [ 27.243810] sd 7:0:0:0: [sdf] 312581808 512-byte hardware sectors (160042 MB)
Apr 29 20:00:49 raidserver kernel: [ 27.243821] sd 7:0:0:0: [sdf] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 27.243823] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 27.243838] sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 27.243885] sd 7:0:0:0: [sdf] 312581808 512-byte hardware sectors (160042 MB)
Apr 29 20:00:49 raidserver kernel: [ 27.243894] sd 7:0:0:0: [sdf] Write Protect is off
Apr 29 20:00:49 raidserver kernel: [ 27.243896] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Apr 29 20:00:49 raidserver kernel: [ 27.243910] sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 29 20:00:49 raidserver kernel: [ 27.243913] sdf: sdf1 sdf2
Apr 29 20:00:49 raidserver kernel: [ 27.266592] sd 7:0:0:0: [sdf] Attached SCSI disk
Apr 29 20:00:49 raidserver kernel: [ 27.266638] sd 7:0:0:0: Attached scsi generic sg5 type 0
Apr 29 20:00:49 raidserver kernel: [ 27.440341] md: md0 stopped.
Apr 29 20:00:49 raidserver kernel: [ 27.477069] md: md0 stopped.
Apr 29 20:00:49 raidserver kernel: [ 27.634005] Attempting manual resume
Apr 29 20:00:49 raidserver kernel: [ 27.634009] swsusp: Resume From Partition 8:69
Apr 29 20:00:49 raidserver kernel: [ 27.634011] PM: Checking swsusp image.
Apr 29 20:00:49 raidserver kernel: [ 27.634173] PM: Resume from disk failed.
Apr 29 20:00:49 raidserver kernel: [ 27.676992] kjournald starting. Commit interval 5 seconds
Apr 29 20:00:49 raidserver kernel: [ 27.677005] EXT3-fs: mounted filesystem with ordered data mode.
Apr 29 20:00:49 raidserver kernel: [ 31.705606] md: md0 stopped.*
*Apr 29 20:00:49 raidserver kernel: [ 31.954956] md: md0 stopped.*
any pointers on recovering the data would be much apreciated.
Frans
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-za/attachments/20100430/c8895556/attachment-0001.htm
More information about the ubuntu-za
mailing list