26/01/2012 23:07, Joey L wrote:
>>
>>>
>>> When I boot the system with all drives in, I get the superflous error.
>>>
>>> So the only way to boot is only to put in /dev/sdc alone and boot.
>>> when i get to a linux prompt, I insert the second drive into the system
>>> /dev/sdd
>>>
>>> To sync the
> You could check whether grub's OK via bootinfoscript (although the
> only real test'll be a reboot...).
>
> http://sourceforge.net/projects/bootinfoscript/
>
thanks for the script - will check it out
>
>>> My parted -l is:
>>>
>>> Disk /dev/sda: 1000GB
>>> Number Start End Size Type
>>
>> My configuration is as such:
>> /dev/md0 = /dev/sdc1 and /dev/sdd1
>> /dev/md1 = /dev/sda1 and /dev/sb1
>>
>> My swap partitions are not part of the array or mirror at all -
>> they are just regular partitions - they are:
>> /dev/sdc2 and /dev/sdd2.
>
> Any particular reason do do that ?
On Wed, Jan 25, 2012 at 5:35 PM, tv.deb...@googlemail.com
wrote:
> 25/01/2012 19:16, Joey L wrote:
>> Okay..I am telling all in this email -:)
>>
>> My configuration is as such:
>> /dev/md0 = /dev/sdc1 and /dev/sdd1
>> /dev/md1 = /dev/sda1 and /dev/sb1
>>
>> My swap partitions are not part o
25/01/2012 19:16, Joey L wrote:
In-line reply ;
> Okay..I am telling all in this email -:)
>
> My configuration is as such:
> /dev/md0 = /dev/sdc1 and /dev/sdd1
> /dev/md1 = /dev/sda1 and /dev/sb1
>
> My swap partitions are not part of the array or mirror at all -
> they are just regular p
Okay..I am telling all in this email -:)
My configuration is as such:
/dev/md0 = /dev/sdc1 and /dev/sdd1
/dev/md1 = /dev/sda1 and /dev/sb1
My swap partitions are not part of the array or mirror at all -
they are just regular partitions - they are:
/dev/sdc2 and /dev/sdd2.
When I boot the sy
24/01/2012 19:10, Joey L wrote:
> Sorry to load up on related issues in this mail, but have a big issue:
> After having synced my mirrored drives in software raid -
> I get the following error:
> error: superfluous RAID member (2 found).
There is a good chance that the error reported is more cosme
24/01/2012 18:34, Joey L wrote:
> In related questions - i hope you can answer - are :
>
> 1. why do i get an error when trying to make swap partition - i get
> this error below after running fdisk, creating a primary partition
> /dev/sdd2 and then changing the type - with t -
> As in below ---
>
Sorry to load up on related issues in this mail, but have a big issue:
After having synced my mirrored drives in software raid -
I get the following error:
error: superfluous RAID member (2 found).
the boot drive is /dev/sdc1 but added another one to the mirror - /dev/sdd1
my questions :
1. should
In related questions - i hope you can answer - are :
1. why do i get an error when trying to make swap partition - i get
this error below after running fdisk, creating a primary partition
/dev/sdd2 and then changing the type - with t -
As in below ---
2. the /dev/sdd drive is the mirrored drive i
Jon Dowland writes:
>
> Pretty sure at that stage it has loaded modules that let it interpret
> a selection of filesystem types, in order to fetch grub.cfg (and
> further
How does it decide which partition (on which disk) and what pathname
to use to find grub.cfg. I assume one it chooses a part
On 18/01/12 16:23, Joey L wrote:
When i put the drive sda into the system to add it back to the md0 -
the system keeps booting from it and refuses to boot from the good sdb
drive.
Boot with just the good drive; degrade the array (fail the missing
drive); relabel your root partition (whatever i
On 19/01/12 02:04, Marc Auslander wrote:
Now, does that code contain a copy of grub.cfg? Or
does it read it from someplace? If the second, how does it decide
where/how to read grub.cfg.
I understand how, once it has grub.cfg, it decides what to boot. It's
where grub.cfg comes from that I don'
19/01/2012 01:43, Joey L wrote:
> Also - is there a way in debian to realize which drive is mapped to
> which linux device ??
> When I go into the bios - i see disk labels or names as DSK04, DSK02
> and also long string of numbers - i guess it is the serial number of
> drive.
For partition UUID:
19/01/2012 00:03, Joey L wrote:
> Sorry - just a couple of last things:
>
>
> 1. do i run the command - "grub-install --recheck --no-floppy
> /dev/sdc1" and "grub-install --recheck --no-floppy /dev/sdd1" ???
>
> or do I run it on the whole drive meaning - "grub-install --recheck
> --no-floppy
This discussion opens a question I've been curious about.
IIUC, bios choses a boot device and runs the MBR code. Assuming
that's GRUB2 MBR code, GRUB2 then loads the 1.5 code hidden before the
first partition of the same device. Next step is to process grub.cfg.
Now, does that code contain a co
Also - is there a way in debian to realize which drive is mapped to
which linux device ??
When I go into the bios - i see disk labels or names as DSK04, DSK02
and also long string of numbers - i guess it is the serial number of
drive.
On Wed, Jan 18, 2012 at 6:03 PM, Joey L wrote:
> Sorry - just
Sorry - just a couple of last things:
1. do i run the command - "grub-install --recheck --no-floppy
/dev/sdc1" and "grub-install --recheck --no-floppy /dev/sdd1" ???
or do I run it on the whole drive meaning - "grub-install --recheck
--no-floppy /dev/sdc" and "grub-install --recheck --no-flopp
18/01/2012 22:22, Joey L wrote:
> okay..thanks for the clarification.
> I think it was initrd - busybox.
>
> my debian version is:
> root@rider:~# lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description:Debian GNU/Linux 6.0.3 (squeeze)
> Release:6.0.3
> Co
okay..thanks for the clarification.
I think it was initrd - busybox.
my debian version is:
root@rider:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 6.0.3 (squeeze)
Release:6.0.3
Codename: squeeze
uname -mrs
Linux 2.6.32-5-am
On Wed, 2012-01-18 at 13:38 -0500, Joey L wrote:
> thanks for the reply -
>
> 1. my issue is that i am not getting to the grub menu on the good
> disk, it always goes to the bad one.
> I think it puts me in a intrdfsram prompt or something similar - even
> if i change the bios settings.
> - so edi
18/01/2012 19:38, Joey L wrote:
> On Wed, Jan 18, 2012 at 12:49 PM, tv.deb...@googlemail.com
> wrote:
>> > 18/01/2012 18:03, Joey L wrote:
>>> >> The issue I am having is that if I put into the system both drives,
>>> >> the system always chooses the faulty drive.
>>> >> I do not even get linux sy
thanks for the reply -
1. my issue is that i am not getting to the grub menu on the good
disk, it always goes to the bad one.
I think it puts me in a intrdfsram prompt or something similar - even
if i change the bios settings.
- so editing the grub menu option - is unavailable for me.
2. regardin
18/01/2012 18:03, Joey L wrote:
> The issue I am having is that if I put into the system both drives,
> the system always chooses the faulty drive.
> I do not even get linux system - i get a weird text prompt - i think
> it is initrdfs - even if i change it in the bios.
>
> On installing grub - ca
The issue I am having is that if I put into the system both drives,
the system always chooses the faulty drive.
I do not even get linux system - i get a weird text prompt - i think
it is initrdfs - even if i change it in the bios.
On installing grub - can you tell me what is the procedure for that
18/01/2012 17:23, Joey L wrote:
> I have a raid 1 mdadm setup.
> I have devices sda and sdb with 2 partitions on each - sda1 and sda2
> on the other drive i have sdb1 and sdb2.
>
> Partition sda1 is the root partition and sda2 is the swap partition.
>
> My sda failed yesterday and now i am runnin
I have a raid 1 mdadm setup.
I have devices sda and sdb with 2 partitions on each - sda1 and sda2
on the other drive i have sdb1 and sdb2.
Partition sda1 is the root partition and sda2 is the swap partition.
My sda failed yesterday and now i am running in sdb only.
When i put the drive sda into
27 matches
Mail list logo
