FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Server Development

 
 
LinkBack Thread Tools
 
Old 03-12-2012, 07:54 PM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Mon, Mar 12, 2012 at 4:13 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> I am failing to boot this server x4270 pass the mdadm --monitor.
> Installed lucid amd64. This is a first install.
>
> details: http://paste.ubuntu.com/880895/
>
> It boots all the way in recovery mode. what gives?

here is the dmesg from recovery mode (single user mode)

http://paste.ubuntu.com/880960/

boots just fine

>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-12-2012, 08:11 PM
"Peter M. Petrakis"
 
Default failing to boot pass mdadm monitor

On 03/12/2012 04:13 PM, Asif Iqbal wrote:

I am failing to boot this server x4270 pass the mdadm --monitor.
Installed lucid amd64. This is a first install.

details: http://paste.ubuntu.com/880895/

It boots all the way in recovery mode. what gives?



I would say your problems began once your partition detection went
inconsistent.

[ 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300 GB/279 GiB)
[ 26.603599] GPT:Primary header thinks Alt. header is not at the end of the disk.
[ 26.603600] GPT:585937498 != 585937499
[ 26.603602] GPT:Alternate GPT header not at the end of the disk.
[ 26.603603] GPT:585937498 != 585937499

which is coming from fs/partitions/efi.c
http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487

494 if (le64_to_cpu(agpt->my_lba) != lastlba) {
495 printk(KERN_WARNING
496 "GPT:Alternate GPT header not at the end of the disk.
");
497 printk(KERN_WARNING "GPT:%lld != %lld
",
498 (unsigned long long)le64_to_cpu(agpt->my_lba),
499 (unsigned long long)lastlba);
500 error_found++;
501 }

The math for lastlba seems correct, 585937500 - 1ULL, a quick google shows
the raw size is consistent with what you have. So the question is how
did 585937498 get computed? Would someone with some more experience with
GPT partitions care to comment?

It doesn't look like your system successfully recovered from find_valid_gpt
or we would have seen "Alternate GPT is invalid, using primary GPT." or
"Primary GPT is invalid, using alternate GPT." in the logs. Those partitions,
or what's left of them, is being presented to mdadm for assembly.

This part is really weird.

[ 27.929744] mdadm: sending ioctl 1261 to a partition!
[ 27.935401] mdadm: sending ioctl 1261 to a partition!
[ 27.941905] mdadm: sending ioctl 1261 to a partition!

Where 1261 is #define __NR_set_mempolicy 1261

I don't think that has any business being sent to a partition. At the moment,
I can't explain how this event, and the GPT fault could be related.

[ 28.679619] md1: detected capacity change from 0 to 146360172544
[ 28.684287] md1: unknown partition table
[ 28.709647] mdadm: sending ioctl 1261 to a partition!
[ 28.713255] mdadm: sending ioctl 1261 to a partition!
Begin: Running /scripts/local-premount ...
Done.
[ 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 29.088849] EXT3-fs: write access will be enabled during recovery.
[ 29.252295] kjournald starting. Commit interval 5 seconds
[ 29.252387] EXT3-fs: recovery complete.
[ 29.265115] EXT3-fs: mounted filesystem with ordered data mode.

I really don't know what shape your backing store is in, noting your
second post, I'm surprised your disks are readable.

So... what changed? Have you upgraded system firmware recently,
kernel upgrades, or anything at all really? I see you have an external
storage enclosure, has that seen any changes either?

Peter

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-12-2012, 08:22 PM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Mon, Mar 12, 2012 at 5:11 PM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:
>
>
> On 03/12/2012 04:13 PM, Asif Iqbal wrote:
>>
>> I am failing to boot this server x4270 pass the mdadm --monitor.
>> Installed lucid amd64. This is a first install.
>>
>> details: http://paste.ubuntu.com/880895/
>>
>> It boots all the way in recovery mode. what gives?
>>
>
> I would say your problems began once your partition detection went
> inconsistent.
>
> [ * 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300
> GB/279 GiB)
> [ * 26.603599] GPT:Primary header thinks Alt. header is not at the end of
> the disk.
> [ * 26.603600] GPT:585937498 != 585937499
> [ * 26.603602] GPT:Alternate GPT header not at the end of the disk.
> [ * 26.603603] GPT:585937498 != 585937499
>
> which is coming from fs/partitions/efi.c
> http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487
>
> *494 * * * *if (le64_to_cpu(agpt->my_lba) != lastlba) {
> *495 * * * * * * * *printk(KERN_WARNING
> *496 * * * * * * * * * * * "GPT:Alternate GPT header not at the end of the
> disk.
");
> *497 * * * * * * * *printk(KERN_WARNING "GPT:%lld != %lld
",
> *498 * * * * * * * * * * * *(unsigned long long)le64_to_cpu(agpt->my_lba),
> *499 * * * * * * * * * * * *(unsigned long long)lastlba);
> *500 * * * * * * * *error_found++;
> *501 * * * *}
>
> The math for lastlba seems correct, 585937500 - 1ULL, a quick google shows
> the raw size is consistent with what you have. So the question is how
> did 585937498 get computed? Would someone with some more experience with
> GPT partitions care to comment?
>
> It doesn't look like your system successfully recovered from find_valid_gpt
> or we would have seen "Alternate GPT is invalid, using primary GPT." or
> "Primary GPT is invalid, using alternate GPT." in the logs. Those
> partitions,
> or what's left of them, is being presented to mdadm for assembly.
>
> This part is really weird.
>
> [ * 27.929744] mdadm: sending ioctl 1261 to a partition!
> [ * 27.935401] mdadm: sending ioctl 1261 to a partition!
> [ * 27.941905] mdadm: sending ioctl 1261 to a partition!
>
> Where 1261 is #define __NR_set_mempolicy * * * * * * *1261
>
> I don't think that has any business being sent to a partition. At the
> moment,
> I can't explain how this event, and the GPT fault could be related.
>
> [ * 28.679619] md1: detected capacity change from 0 to 146360172544
> [ * 28.684287] *md1: unknown partition table
> [ * 28.709647] mdadm: sending ioctl 1261 to a partition!
> [ * 28.713255] mdadm: sending ioctl 1261 to a partition!
> Begin: Running /scripts/local-premount ...
> Done.
> [ * 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
> [ * 29.088849] EXT3-fs: write access will be enabled during recovery.
> [ * 29.252295] kjournald starting. *Commit interval 5 seconds
> [ * 29.252387] EXT3-fs: recovery complete.
> [ * 29.265115] EXT3-fs: mounted filesystem with ordered data mode.
>
> I really don't know what shape your backing store is in, noting your
> second post, I'm surprised your disks are readable.
>
> So... what changed? Have you upgraded system firmware recently,
> kernel upgrades, or anything at all really? I see you have an external
> storage enclosure, has that seen any changes either?

This is a new box. This is the first install. There is nothing attached to it.


>
> Peter
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-12-2012, 08:29 PM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Mon, Mar 12, 2012 at 5:22 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> On Mon, Mar 12, 2012 at 5:11 PM, Peter M. Petrakis
> <peter.petrakis@canonical.com> wrote:
>>
>>
>> On 03/12/2012 04:13 PM, Asif Iqbal wrote:
>>>
>>> I am failing to boot this server x4270 pass the mdadm --monitor.
>>> Installed lucid amd64. This is a first install.
>>>
>>> details: http://paste.ubuntu.com/880895/
>>>
>>> It boots all the way in recovery mode. what gives?
>>>
>>
>> I would say your problems began once your partition detection went
>> inconsistent.
>>
>> [ * 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300
>> GB/279 GiB)
>> [ * 26.603599] GPT:Primary header thinks Alt. header is not at the end of
>> the disk.
>> [ * 26.603600] GPT:585937498 != 585937499
>> [ * 26.603602] GPT:Alternate GPT header not at the end of the disk.
>> [ * 26.603603] GPT:585937498 != 585937499
>>
>> which is coming from fs/partitions/efi.c
>> http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487
>>
>> *494 * * * *if (le64_to_cpu(agpt->my_lba) != lastlba) {
>> *495 * * * * * * * *printk(KERN_WARNING
>> *496 * * * * * * * * * * * "GPT:Alternate GPT header not at the end of the
>> disk.
");
>> *497 * * * * * * * *printk(KERN_WARNING "GPT:%lld != %lld
",
>> *498 * * * * * * * * * * * *(unsigned long long)le64_to_cpu(agpt->my_lba),
>> *499 * * * * * * * * * * * *(unsigned long long)lastlba);
>> *500 * * * * * * * *error_found++;
>> *501 * * * *}
>>
>> The math for lastlba seems correct, 585937500 - 1ULL, a quick google shows
>> the raw size is consistent with what you have. So the question is how
>> did 585937498 get computed? Would someone with some more experience with
>> GPT partitions care to comment?
>>
>> It doesn't look like your system successfully recovered from find_valid_gpt
>> or we would have seen "Alternate GPT is invalid, using primary GPT." or
>> "Primary GPT is invalid, using alternate GPT." in the logs. Those
>> partitions,
>> or what's left of them, is being presented to mdadm for assembly.
>>
>> This part is really weird.
>>
>> [ * 27.929744] mdadm: sending ioctl 1261 to a partition!
>> [ * 27.935401] mdadm: sending ioctl 1261 to a partition!
>> [ * 27.941905] mdadm: sending ioctl 1261 to a partition!
>>
>> Where 1261 is #define __NR_set_mempolicy * * * * * * *1261
>>
>> I don't think that has any business being sent to a partition. At the
>> moment,
>> I can't explain how this event, and the GPT fault could be related.
>>
>> [ * 28.679619] md1: detected capacity change from 0 to 146360172544
>> [ * 28.684287] *md1: unknown partition table
>> [ * 28.709647] mdadm: sending ioctl 1261 to a partition!
>> [ * 28.713255] mdadm: sending ioctl 1261 to a partition!
>> Begin: Running /scripts/local-premount ...
>> Done.
>> [ * 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
>> [ * 29.088849] EXT3-fs: write access will be enabled during recovery.
>> [ * 29.252295] kjournald starting. *Commit interval 5 seconds
>> [ * 29.252387] EXT3-fs: recovery complete.
>> [ * 29.265115] EXT3-fs: mounted filesystem with ordered data mode.
>>
>> I really don't know what shape your backing store is in, noting your
>> second post, I'm surprised your disks are readable.
>>
>> So... what changed? Have you upgraded system firmware recently,
>> kernel upgrades, or anything at all really? I see you have an external
>> storage enclosure, has that seen any changes either?
>
> This is a new box. This is the first install. There is nothing attached to it.
>

I am going to reinstall the OS. Should I reformat the disks maybe?

>
>>
>> Peter
>>


--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-12-2012, 08:43 PM
"Peter M. Petrakis"
 
Default failing to boot pass mdadm monitor

On 03/12/2012 05:22 PM, Asif Iqbal wrote:

On Mon, Mar 12, 2012 at 5:11 PM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:



On 03/12/2012 04:13 PM, Asif Iqbal wrote:


I am failing to boot this server x4270 pass the mdadm --monitor.
Installed lucid amd64. This is a first install.

details: http://paste.ubuntu.com/880895/

It boots all the way in recovery mode. what gives?



I would say your problems began once your partition detection went
inconsistent.

[ 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300
GB/279 GiB)
[ 26.603599] GPT:Primary header thinks Alt. header is not at the end of
the disk.
[ 26.603600] GPT:585937498 != 585937499
[ 26.603602] GPT:Alternate GPT header not at the end of the disk.
[ 26.603603] GPT:585937498 != 585937499

which is coming from fs/partitions/efi.c
http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487

494 if (le64_to_cpu(agpt->my_lba) != lastlba) {
495 printk(KERN_WARNING
496 "GPT:Alternate GPT header not at the end of the
disk.
");
497 printk(KERN_WARNING "GPT:%lld != %lld
",
498 (unsigned long long)le64_to_cpu(agpt->my_lba),
499 (unsigned long long)lastlba);
500 error_found++;
501 }

The math for lastlba seems correct, 585937500 - 1ULL, a quick google shows
the raw size is consistent with what you have. So the question is how
did 585937498 get computed? Would someone with some more experience with
GPT partitions care to comment?

It doesn't look like your system successfully recovered from find_valid_gpt
or we would have seen "Alternate GPT is invalid, using primary GPT." or
"Primary GPT is invalid, using alternate GPT." in the logs. Those
partitions,
or what's left of them, is being presented to mdadm for assembly.

This part is really weird.

[ 27.929744] mdadm: sending ioctl 1261 to a partition!
[ 27.935401] mdadm: sending ioctl 1261 to a partition!
[ 27.941905] mdadm: sending ioctl 1261 to a partition!

Where 1261 is #define __NR_set_mempolicy 1261

I don't think that has any business being sent to a partition. At the
moment,
I can't explain how this event, and the GPT fault could be related.

[ 28.679619] md1: detected capacity change from 0 to 146360172544
[ 28.684287] md1: unknown partition table
[ 28.709647] mdadm: sending ioctl 1261 to a partition!
[ 28.713255] mdadm: sending ioctl 1261 to a partition!
Begin: Running /scripts/local-premount ...
Done.
[ 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 29.088849] EXT3-fs: write access will be enabled during recovery.
[ 29.252295] kjournald starting. Commit interval 5 seconds
[ 29.252387] EXT3-fs: recovery complete.
[ 29.265115] EXT3-fs: mounted filesystem with ordered data mode.

I really don't know what shape your backing store is in, noting your
second post, I'm surprised your disks are readable.

So... what changed? Have you upgraded system firmware recently,
kernel upgrades, or anything at all really? I see you have an external
storage enclosure, has that seen any changes either?


This is a new box. This is the first install. There is nothing attached to it.


Then you either have questionable equipment, bad install medium, or this platform isn't fully supported
on this release of Ubuntu. I misspoke when I said "external" storage enclosure. there
is a SES enclosure.

[ 26.628621] scsi 6:0:10:0: Enclosure LSILOGIC SASX28 A.0 502E PQ: 0 ANSI: 5
[ 26.633357] scsi 6:0:10:0: Attached scsi generic sg10 type 13
[ 27.380344] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA

Not knowing what the platform was, I assumed it was external.

Looking back on your post, you called this a x4270. Is that a Sun x4270?

Peter






Peter

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam






--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-12-2012, 10:00 PM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Mon, Mar 12, 2012 at 5:43 PM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:
>
>
> On 03/12/2012 05:22 PM, Asif Iqbal wrote:
>>
>> On Mon, Mar 12, 2012 at 5:11 PM, Peter M. Petrakis
>> <peter.petrakis@canonical.com> *wrote:
>>>
>>>
>>>
>>> On 03/12/2012 04:13 PM, Asif Iqbal wrote:
>>>>
>>>>
>>>> I am failing to boot this server x4270 pass the mdadm --monitor.
>>>> Installed lucid amd64. This is a first install.
>>>>
>>>> details: http://paste.ubuntu.com/880895/
>>>>
>>>> It boots all the way in recovery mode. what gives?
>>>>
>>>
>>> I would say your problems began once your partition detection went
>>> inconsistent.
>>>
>>> [ * 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300
>>> GB/279 GiB)
>>> [ * 26.603599] GPT:Primary header thinks Alt. header is not at the end of
>>> the disk.
>>> [ * 26.603600] GPT:585937498 != 585937499
>>> [ * 26.603602] GPT:Alternate GPT header not at the end of the disk.
>>> [ * 26.603603] GPT:585937498 != 585937499
>>>
>>> which is coming from fs/partitions/efi.c
>>> http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487
>>>
>>> *494 * * * *if (le64_to_cpu(agpt->my_lba) != lastlba) {
>>> *495 * * * * * * * *printk(KERN_WARNING
>>> *496 * * * * * * * * * * * "GPT:Alternate GPT header not at the end of
>>> the
>>> disk.
");
>>> *497 * * * * * * * *printk(KERN_WARNING "GPT:%lld != %lld
",
>>> *498 * * * * * * * * * * * *(unsigned long
>>> long)le64_to_cpu(agpt->my_lba),
>>> *499 * * * * * * * * * * * *(unsigned long long)lastlba);
>>> *500 * * * * * * * *error_found++;
>>> *501 * * * *}
>>>
>>> The math for lastlba seems correct, 585937500 - 1ULL, a quick google
>>> shows
>>> the raw size is consistent with what you have. So the question is how
>>> did 585937498 get computed? Would someone with some more experience with
>>> GPT partitions care to comment?
>>>
>>> It doesn't look like your system successfully recovered from
>>> find_valid_gpt
>>> or we would have seen "Alternate GPT is invalid, using primary GPT." or
>>> "Primary GPT is invalid, using alternate GPT." in the logs. Those
>>> partitions,
>>> or what's left of them, is being presented to mdadm for assembly.
>>>
>>> This part is really weird.
>>>
>>> [ * 27.929744] mdadm: sending ioctl 1261 to a partition!
>>> [ * 27.935401] mdadm: sending ioctl 1261 to a partition!
>>> [ * 27.941905] mdadm: sending ioctl 1261 to a partition!
>>>
>>> Where 1261 is #define __NR_set_mempolicy * * * * * * *1261
>>>
>>> I don't think that has any business being sent to a partition. At the
>>> moment,
>>> I can't explain how this event, and the GPT fault could be related.
>>>
>>> [ * 28.679619] md1: detected capacity change from 0 to 146360172544
>>> [ * 28.684287] *md1: unknown partition table
>>> [ * 28.709647] mdadm: sending ioctl 1261 to a partition!
>>> [ * 28.713255] mdadm: sending ioctl 1261 to a partition!
>>> Begin: Running /scripts/local-premount ...
>>> Done.
>>> [ * 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
>>> [ * 29.088849] EXT3-fs: write access will be enabled during recovery.
>>> [ * 29.252295] kjournald starting. *Commit interval 5 seconds
>>> [ * 29.252387] EXT3-fs: recovery complete.
>>> [ * 29.265115] EXT3-fs: mounted filesystem with ordered data mode.
>>>
>>> I really don't know what shape your backing store is in, noting your
>>> second post, I'm surprised your disks are readable.
>>>
>>> So... what changed? Have you upgraded system firmware recently,
>>> kernel upgrades, or anything at all really? I see you have an external
>>> storage enclosure, has that seen any changes either?
>>
>>
>> This is a new box. This is the first install. There is nothing attached to
>> it.
>
>
> Then you either have questionable equipment, bad install medium, or this
> platform isn't fully supported
> on this release of Ubuntu. I misspoke when I said "external" storage
> enclosure. there
> is a SES enclosure.
>
> [ * 26.628621] scsi 6:0:10:0: Enclosure * * * * LSILOGIC SASX28 A.0
> 502E PQ: 0 ANSI: 5
> [ * 26.633357] scsi 6:0:10:0: Attached scsi generic sg10 type 13
> [ * 27.380344] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled,
> supports DPO and FUA
>
> Not knowing what the platform was, I assumed it was external.
>
> Looking back on your post, you called this a x4270. Is that a Sun x4270?

yes


>
> Peter
>
>
>>
>>
>>>
>>> Peter
>>>
>>> --
>>> ubuntu-server mailing list
>>> ubuntu-server@lists.ubuntu.com
>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
>>> More info: https://wiki.ubuntu.com/ServerTeam
>>
>>
>>
>>
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-13-2012, 02:30 AM
"Peter M. Petrakis"
 
Default failing to boot pass mdadm monitor

On 03/12/2012 07:00 PM, Asif Iqbal wrote:

On Mon, Mar 12, 2012 at 5:43 PM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:



On 03/12/2012 05:22 PM, Asif Iqbal wrote:


On Mon, Mar 12, 2012 at 5:11 PM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:




On 03/12/2012 04:13 PM, Asif Iqbal wrote:



I am failing to boot this server x4270 pass the mdadm --monitor.
Installed lucid amd64. This is a first install.

details: http://paste.ubuntu.com/880895/

It boots all the way in recovery mode. what gives?



I would say your problems began once your partition detection went
inconsistent.

[ 26.603469] sd 6:0:3:0: [sdd] 585937500 512-byte logical blocks: (300
GB/279 GiB)
[ 26.603599] GPT:Primary header thinks Alt. header is not at the end of
the disk.
[ 26.603600] GPT:585937498 != 585937499
[ 26.603602] GPT:Alternate GPT header not at the end of the disk.
[ 26.603603] GPT:585937498 != 585937499

which is coming from fs/partitions/efi.c
http://lxr.linux.no/linux+v3.2.9/fs/partitions/efi.c#L487

494 if (le64_to_cpu(agpt->my_lba) != lastlba) {
495 printk(KERN_WARNING
496 "GPT:Alternate GPT header not at the end of
the
disk.
");
497 printk(KERN_WARNING "GPT:%lld != %lld
",
498 (unsigned long
long)le64_to_cpu(agpt->my_lba),
499 (unsigned long long)lastlba);
500 error_found++;
501 }

The math for lastlba seems correct, 585937500 - 1ULL, a quick google
shows
the raw size is consistent with what you have. So the question is how
did 585937498 get computed? Would someone with some more experience with
GPT partitions care to comment?

It doesn't look like your system successfully recovered from
find_valid_gpt
or we would have seen "Alternate GPT is invalid, using primary GPT." or
"Primary GPT is invalid, using alternate GPT." in the logs. Those
partitions,
or what's left of them, is being presented to mdadm for assembly.

This part is really weird.

[ 27.929744] mdadm: sending ioctl 1261 to a partition!
[ 27.935401] mdadm: sending ioctl 1261 to a partition!
[ 27.941905] mdadm: sending ioctl 1261 to a partition!

Where 1261 is #define __NR_set_mempolicy 1261

I don't think that has any business being sent to a partition. At the
moment,
I can't explain how this event, and the GPT fault could be related.

[ 28.679619] md1: detected capacity change from 0 to 146360172544
[ 28.684287] md1: unknown partition table
[ 28.709647] mdadm: sending ioctl 1261 to a partition!
[ 28.713255] mdadm: sending ioctl 1261 to a partition!
Begin: Running /scripts/local-premount ...
Done.
[ 29.082318] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 29.088849] EXT3-fs: write access will be enabled during recovery.
[ 29.252295] kjournald starting. Commit interval 5 seconds
[ 29.252387] EXT3-fs: recovery complete.
[ 29.265115] EXT3-fs: mounted filesystem with ordered data mode.

I really don't know what shape your backing store is in, noting your
second post, I'm surprised your disks are readable.

So... what changed? Have you upgraded system firmware recently,
kernel upgrades, or anything at all really? I see you have an external
storage enclosure, has that seen any changes either?



This is a new box. This is the first install. There is nothing attached to
it.



Then you either have questionable equipment, bad install medium, or this
platform isn't fully supported
on this release of Ubuntu. I misspoke when I said "external" storage
enclosure. there
is a SES enclosure.

[ 26.628621] scsi 6:0:10:0: Enclosure LSILOGIC SASX28 A.0
502E PQ: 0 ANSI: 5
[ 26.633357] scsi 6:0:10:0: Attached scsi generic sg10 type 13
[ 27.380344] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled,
supports DPO and FUA

Not knowing what the platform was, I assumed it was external.

Looking back on your post, you called this a x4270. Is that a Sun x4270?


yes


Well, I can tell you we have an X4150 and it never fully completed certification
for 10.04 LTS. I assume they're in the same ball park? Most cost effective
thing you can do is make sure all your firmware bits are up to date and try
installing with our latest stable release. Should you find that the new kernel
alleviates your issues you could stick with oneiric, since precise (the next LTS)
is just around the corner. Failing that, there's always commercial support.

Peter





Peter







Peter

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam







--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam






--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-13-2012, 03:09 AM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Mon, Mar 12, 2012 at 4:13 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> I am failing to boot this server x4270 pass the mdadm --monitor.
> Installed lucid amd64. This is a first install.
>
> details: http://paste.ubuntu.com/880895/
>
> It boots all the way in recovery mode. what gives?

ok. I reinstalled lucid 64bit. No more GPT error. But it hangs right
after mdadm --monitor

http://paste.ubuntu.com/881409/


>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-13-2012, 03:35 AM
"Peter M. Petrakis"
 
Default failing to boot pass mdadm monitor

On 03/13/2012 12:09 AM, Asif Iqbal wrote:

On Mon, Mar 12, 2012 at 4:13 PM, Asif Iqbal<vadud3@gmail.com> wrote:

I am failing to boot this server x4270 pass the mdadm --monitor.
Installed lucid amd64. This is a first install.

details: http://paste.ubuntu.com/880895/

It boots all the way in recovery mode. what gives?


ok. I reinstalled lucid 64bit. No more GPT error. But it hangs right
after mdadm --monitor


At least that's an improvement.



http://paste.ubuntu.com/881409/


...
mdadm: sending ioctl 1261 to a partition!

(I confused syscall with storage ioctl earlier, whoops

Now that we're just down to this problem, a little google...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656899:
https://bugzilla.redhat.com/show_bug.cgi?id=783823
https://bugzilla.redhat.com/show_bug.cgi?id=783955

http://www.serverphorums.com/read.php?12,436266

and ... I think there's a fix:
https://lkml.org/lkml/2012/1/24/136

Probably worth filing a bug at this point, also please try and
reproduce this issue with oneiric, and the latest mainline
kernel [1] if possible. Thanks.

Peter

1. https://wiki.ubuntu.com/Kernel/MainlineBuilds
http://kernel.ubuntu.com/~kernel-ppa/mainline/






--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?






--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 
Old 03-13-2012, 05:47 PM
Asif Iqbal
 
Default failing to boot pass mdadm monitor

On Tue, Mar 13, 2012 at 12:35 AM, Peter M. Petrakis
<peter.petrakis@canonical.com> wrote:
>
>
> On 03/13/2012 12:09 AM, Asif Iqbal wrote:
>>
>> On Mon, Mar 12, 2012 at 4:13 PM, Asif Iqbal<vadud3@gmail.com> *wrote:
>>>
>>> I am failing to boot this server x4270 pass the mdadm --monitor.
>>> Installed lucid amd64. This is a first install.
>>>
>>> details: http://paste.ubuntu.com/880895/
>>>
>>> It boots all the way in recovery mode. what gives?
>>
>>
>> ok. I reinstalled lucid 64bit. No more GPT error. But it hangs right
>> after mdadm --monitor
>
>
> At least that's an improvement.
>
>>
>> http://paste.ubuntu.com/881409/
>
>
> ...
>
> mdadm: sending ioctl 1261 to a partition!
>
> (I confused syscall with storage ioctl earlier, whoops
>
> Now that we're just down to this problem, a little google...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656899:
> https://bugzilla.redhat.com/show_bug.cgi?id=783823
> https://bugzilla.redhat.com/show_bug.cgi?id=783955
>
> http://www.serverphorums.com/read.php?12,436266
>
> and ... I think there's a fix:
> https://lkml.org/lkml/2012/1/24/136
>
> Probably worth filing a bug at this point, also please try and
> reproduce this issue with oneiric, and the latest mainline
> kernel *[1] if possible. Thanks.

installed oneiric this time. failed to mount /var, /home, /opt and
/usr/local LVs.
I had to run vgchange -a y to make those LVs available and then
booted all the way. details: http://paste.ubuntu.com/882168/

And I choose skip.. it does boot all the way but not so useful w/o /var
as shown below.

/dev/mapper/vg0-root: clean, 7197/610800 files, 133568/2441216 blocks
/dev/md0: clean, 229/97536 files, 46927/390132 blocks
/dev/mapper/vg0-usr: clean, 44869/610800 files, 182623/2441216 blocks
The disk drive for /home is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M for manual recovery

Skipping /home at user request
The disk drive for /opt is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M for manual recovery

Skipping /opt at user request
The disk drive for /usr/local is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M for manual recovery

Skipping /usr/local at user request
The disk drive for /var is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M for manual recovery

Skipping /var at user request
* Starting AppArmor profiles [ OK ]
* Starting MD monitoring service mdadm --monitor [ OK ]
cd: 33: can't cd to /var/cache/pppconfig

Ubuntu 11.10 apa-splunk-05 ttyS0

apa-splunk-05 login:

>
> Peter
>
> 1. https://wiki.ubuntu.com/Kernel/MainlineBuilds
> * http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
>
>
>>
>>>
>>> --
>>> Asif Iqbal
>>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>> A: Because it messes up the order in which people normally read text.
>>> Q: Why is top-posting such a bad thing?
>>
>>
>>
>>
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
 

Thread Tools




All times are GMT. The time now is 02:46 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org