Hello:
I started this thread not because grub on both disks should be by default
but because I found difficulties in recovering. If I performed badly, and
there is no problem in installing grub on the working disk, then I see no
problem. There are many raids, not limited to raid1. Perhaps it is
Francesco Pietra wrote:
Alexandru Cardaniuc wrote:
Did I miss something during the debian installation? Why wasn't grub
automatically installed on both disks?
Seems like it should have been. I would file a bug against the
debian-installer or installation-reports.
I started this
Alexandru Cardaniuc wrote:
I just did 2 reinstalls in the last two weeks (upgrade from sqeeze to
wheezy screwed up my grub config and then my 6 year old drives started
failing - so much fun :), but basically during both reinstalls and
creating MD devices with debian installer (md0/md1/md2)
Bob Proulx b...@proulx.com writes:
Nonetheless, I'll try to digest your manual. At this point, could
you also describe how to safely proceed, on this situation, to have
grub on both disks? It would be useful community wide, to complete
the raid1 installation from the Debian installer.
As
On Wed, Mar 6, 2013 at 8:38 AM, Bob Proulx b...@proulx.com wrote:
Francesco Pietra wrote:
Bob Proulx wrote:
Francesco Pietra wrote:
Thanks so much for this manual. Unfortunately, I have no more the
initial situation (one HD replaced) because I was hurried by an editor
to provide
On Wed, Mar 06, 2013 at 06:59:01AM +0100, Francesco Pietra wrote:
I had all my data on another raid1 machine. Following the new install,
all data were scp transferred. All my machine are on a router, with
passwordless scp. Which is also used to contact external server for
computational work.
On Wed, Mar 6, 2013 at 8:44 AM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
snip
Thanks a lot for your generous help. I (we) learned a lot from you.
Are you running with raid1 on raw sda and sdb or are you creating
partitions and running raid on the partitions (which to me is the
snip
As far as I can remember, I already posted for this system
root@.:/home/francesco# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda2[0] sdb2[1]
487759680 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
191296 blocks super 1.2 [2/2] [UU]
Sorry, I forgot both the list and the appropriate output;
root@:/home/francesco# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096
On Wed, Mar 06, 2013 at 08:03:12PM +0100, Francesco Pietra wrote:
Sorry, I forgot both the list and the appropriate output;
root@:/home/francesco# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors
On Wed, Mar 6, 2013 at 9:03 PM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
On Wed, Mar 06, 2013 at 08:03:12PM +0100, Francesco Pietra wrote:
Sorry, I forgot both the list and the appropriate output;
root@:/home/francesco# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
Francesco Pietra wrote:
Thanks so much for this manual. Unfortunately, I have no more the
initial situation (one HD replaced) because I was hurried by an editor
to provide computational data from my CUDA server. I did not want to
run the server before all my data were backed up. Therefore I
On Tue, Mar 5, 2013 at 7:30 PM, Bob Proulx b...@proulx.com wrote:
Francesco Pietra wrote:
Thanks so much for this manual. Unfortunately, I have no more the
initial situation (one HD replaced) because I was hurried by an editor
to provide computational data from my CUDA server. I did not want
Francesco Pietra wrote:
Bob Proulx wrote:
Francesco Pietra wrote:
Thanks so much for this manual. Unfortunately, I have no more the
initial situation (one HD replaced) because I was hurried by an editor
to provide computational data from my CUDA server. I did not want to
run the server
: Francesco Pietra chiendar...@gmail.com
Date: Sat, Mar 2, 2013 at 10:11 AM
Subject: Re: RAID1 all bootable
To: Lennart Sorensen lsore...@csclub.uwaterloo.ca, amd64 Debian
debian-am...@lists.debian.org, debian-users
debian-user@lists.debian.org
Is this recipe devised for installing grub
Hi Francesco,
As far as I can determine reading this thread you have had a RAID1
with two disks sda and sdb. The disk sda failed. But grub was only
installed on the failed sda. The disk sdb contains a mirror of
everything but does not boot.
Earlier in the thread Lennart gave an excellent
Hi Bob:
Thanks so much for this manual. Unfortunately, I have no more the
initial situation (one HD replaced) because I was hurried by an editor
to provide computational data from my CUDA server. I did not want to
run the server before all my data were backed up. Therefore I did a
fresh amd64
Is this recipe devised for installing grub on both sda and sda with an
undamaged RAID1?
In my case, with the sda that contained grub loader replaced by a new
disk, the rescue mode (using the same CD installer for amd64 wheezy)
did not find any partition. Inverting the SATA cables, same result.
: Francesco Pietra chiendar...@gmail.com
Date: Sat, Mar 2, 2013 at 10:11 AM
Subject: Re: RAID1 all bootable
To: Lennart Sorensen lsore...@csclub.uwaterloo.ca, amd64 Debian
debian-am...@lists.debian.org, debian-users
debian-user@lists.debian.org
Is this recipe devised for installing grub on both sda
in this situation.
Thanks
francesco pietra
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Sat, Mar 2, 2013 at 10:11 AM
Subject: Re: RAID1 all bootable
To: Lennart Sorensen lsore...@csclub.uwaterloo.ca, amd64 Debian
debian-am...@lists.debian.org
RAID1 (md0 md1) is not seen. I assume that this is the way Knoppix
behaves in this situation.
Thanks
francesco pietra
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Sat, Mar 2, 2013 at 10:11 AM
Subject: Re: RAID1 all bootable
To: Lennart Sorensen
Hi:
With a raid1 amd64 wheezy, one of the two HDs got broken.
Unfortunately, I had added grub to sda only, which is just the one
broken. So that, when it is replaced with a fresh HD, the OS is not
found. Inverting the SATA cables of course does not help (Operative
System Not Found). In a previous
Francesco,
If your RAID is mdadm based, I would use a live CD and then chroot into
your installed OS. Once in, I would use grub-install /dev/sd? to add the
MBR info to the mirror. Once you are back up and running you can use
mdadm to remove the defective disk and if desired add a new one to the
On Fri, Mar 01, 2013 at 08:20:09PM +0100, Francesco Pietra wrote:
Hi:
With a raid1 amd64 wheezy, one of the two HDs got broken.
Unfortunately, I had added grub to sda only, which is just the one
broken. So that, when it is replaced with a fresh HD, the OS is not
found. Inverting the SATA
24 matches
Mail list logo
