From: Phil Turmel <philip@turmel.org>
To: William Colls <william.colls@rogers.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid Problem - Unknown File System Type
Date: Wed, 09 Nov 2011 22:57:09 -0500 [thread overview]
Message-ID: <4EBB4B95.6040309@turmel.org> (raw)
In-Reply-To: <4EBB46A5.8080305@rogers.com>
On 11/09/2011 10:36 PM, William Colls wrote:
> [ .... ]
>>
>> OK. So that wasn't it. GRUB is in the first sector, with a MBR partition table identifying a single 750G partition starting at sector 63.
>
> The array was not bootable in its original configuration, so I am surprised that GRUB would be on the disk, but the single partition of 750G is correct.
>
>> So something else is wrong. Maybe your kernel is different, and just doesn't have the module for the FS. Or one of the BIOSes messes with the apparent disk capacity. Or something else is interfering.
>>
>> Please show:
>>
>> cat /proc/filesystems >
>
> nodev sysfs
> nodev rootfs
> nodev bdev
> nodev proc
> nodev cgroup
> nodev cpuset
> nodev tmpfs
> nodev devtmpfs
> nodev debugfs
> nodev securityfs
> odev sockfs
> nodev pipefs
> nodev anon_inodefs
> nodev inotifyfs
> nodev devpts
> ext3
> ext2
> ext4
> nodev ramfs
> nodev hugetlbfs
> nodev ecryptfs
> nodev fuse
> fuseblk
> nodev fusectl
> nodev mqueue
> vfat
> iso9660
Hmmm. None of the common extras, like reiserfs, xfs, or jfs. Nor support for DVDs w/ udf.
>> cat /proc/partitions
>
> major minor #blocks name
>
> 8 0 312571224 sda
> 8 1 306929664 sda1
> 8 2 1 sda2
> 8 5 5639168 sda5
> 8 16 732574584 sdb
> 8 32 732574584 sdc
> 9 0 732574464 md0
> 259 0 732572001 md0p1
OK.
>> fdisk -l
>
> Disk /dev/sda: 320.1 GB, 320072933376 bytes
> 255 heads, 63 sectors/track, 38913 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000b9f04
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 38212 306929664 83 Linux
> /dev/sda2 38212 38914 5639169 5 Extended
> /dev/sda5 38212 38914 5639168 82 Linux swap / Solaris
>
> Disk /dev/sdb: 750.2 GB, 750156374016 bytes
> 255 heads, 63 sectors/track, 91201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000bb73e
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 91201 732572001 83 Linux
>
> Disk /dev/sdc: 750.2 GB, 750156374016 bytes
> 255 heads, 63 sectors/track, 91201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000bb73e
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 * 1 91201 732572001 83 Linux
>
> Disk /dev/md0: 750.2 GB, 750156251136 bytes
> 255 heads, 63 sectors/track, 91201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000bb73e
>
> Device Boot Start End Blocks Id System
> /dev/md0p1 * 1 91201 732572001 83 Linux
OK.
>> lsdrv
>
> **Warning** The following utility(ies) failed to execute:
> sginfo
> pvs
> lvs
> Some information may be missing.
Missing pvs and lvs means LVM is not installed. Do you recall if the array was mounted directly?
> PCI [pata_atiixp] 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
> ├─scsi 0:0:0:0 ATA WDC WD3200AAJB-0
> │ └─sda: [8:0] Empty/Unknown 298.09g
> │ ├─sda1: [8:1] Empty/Unknown 292.71g
> │ │ └─Mounted as /dev/disk/by-uuid/0a85841d-6b71-43ba-8558-3f86dce72359 @ /
> │ ├─sda2: [8:2] Empty/Unknown 1.00k
> │ └─sda5: [8:5] Empty/Unknown 5.38g
> └─scsi 1:x:x:x [Empty]
> PCI [ahci] 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
> ├─scsi 2:0:0:0 ATA WDC WD7500AAKS-0
> │ └─sdb: [8:16] Empty/Unknown 698.64g
> │ └─md0: [9:0] Empty/Unknown 698.64g
> │ └─md0p1: [259:0] Empty/Unknown 698.64g
> ├─scsi 3:0:0:0 ASUS DRW-24B1ST a {B2D0CL124266}
> │ └─sr0: [11:0] Empty/Unknown 1.00g
> ├─scsi 4:0:0:0 ATA WDC WD7500AAKS-0
> │ └─sdc: [8:32] Empty/Unknown 698.64g
> └─scsi 5:x:x:x [Empty]
> Other Block Devices
> ├─ram0: [1:0] Empty/Unknown 64.00m
> ├─ram1: [1:1] Empty/Unknown 64.00m
> ├─ram2: [1:2] Empty/Unknown 64.00m
> ├─ram3: [1:3] Empty/Unknown 64.00m
> ├─ram4: [1:4] Empty/Unknown 64.00m
> ├─ram5: [1:5] Empty/Unknown 64.00m
> ├─ram6: [1:6] Empty/Unknown 64.00m
> ├─ram7: [1:7] Empty/Unknown 64.00m
> ├─ram8: [1:8] Empty/Unknown 64.00m
> ├─ram9: [1:9] Empty/Unknown 64.00m
> ├─ram10: [1:10] Empty/Unknown 64.00m
> ├─ram11: [1:11] Empty/Unknown 64.00m
> ├─ram12: [1:12] Empty/Unknown 64.00m
> ├─ram13: [1:13] Empty/Unknown 64.00m
> ├─ram14: [1:14] Empty/Unknown 64.00m
> └─ram15: [1:15] Empty/Unknown 64.00m
No surprises, but not enough information.
>> ... and repeat on the old system if at all possible. Preferably with one of the disks plugged back into it.
>
> The old system is not available
Unfortunate.
Please show a hexdump of the first 8k of /dev/md0p1. That should give us a signature to hunt down.
In the meantime, consider installing some FS support packages:
xfsprogs
reiserfsprogs
jfsutils
btrfs-tools
udftools
lvm2
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-10 3:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 16:12 Raid Problem - Unknown File System Type William Colls
2011-11-09 16:39 ` Robin Hill
2011-11-09 17:12 ` William Colls
2011-11-09 18:55 ` Phil Turmel
2011-11-09 19:57 ` William Colls
2011-11-09 20:05 ` Phil Turmel
[not found] ` <4EBAE90F.2030104@rogers.com>
2011-11-09 21:45 ` Phil Turmel
2011-11-10 3:36 ` William Colls
2011-11-10 3:57 ` Phil Turmel [this message]
2011-11-10 15:23 ` William Colls
2011-11-10 15:48 ` Phil Turmel
2011-11-10 16:12 ` John Robinson
2011-11-10 16:32 ` Phil Turmel
2011-11-14 15:01 ` William Colls
2011-11-10 8:53 ` Robin Hill
2011-11-09 17:07 ` Gordon Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBB4B95.6040309@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=william.colls@rogers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).