On Sunday 09 April 2017 18:43:32 Ron Leach wrote:
> While trying to install Debian 7.11
Why are you installing Wheezy?
Lisi
On 04/09/2017 08:43 PM, Ron Leach wrote:
> List, good evening,
>
> I am trying to install Debian onto an LVM, and I want the LVM to use a
> pair of disks in a RAID1 configuration. I'm having difficulty
> instructing the partitioner to do this.
>
> I have a new, empty, machine with 2 x 3TB disks.
Hi Ron,
On Sun, Apr 09, 2017 at 06:43:32PM +0100, Ron Leach wrote:
> What partitions - I think I mean logical volumes - might I be best
> using for my installation, keeping in mind that I will need to extend
> whatever logical volume houses the 'users-files'?
I think you are making a conceptual e
List, good evening,
I am trying to install Debian onto an LVM, and I want the LVM to use a
pair of disks in a RAID1 configuration. I'm having difficulty
instructing the partitioner to do this.
I have a new, empty, machine with 2 x 3TB disks. This new machine is
intended to replace our exis
Dear all,
I'm a newbie in using Debian, my first task (and a good chance to learn
using debian) is to setup an email server with the following hardware:
Intel S1200btlr board (Intel C204 chipset) with a Xeon E3-1230v2 CPU on it
2*1T disks, form a RAID1 by intel embeded server raid technology II
(
On Wed, Dec 5, 2012 at 1:21 PM, Marcus Blumhagen
wrote:
> Am 05.12.2012 17:01, schrieb Tom H:
>>
>> Since you're using grub-legacy and might be using update-grub and the
>> "DEBIAN AUTOMAGIC KERNELS LIST" system, make sure that "groot" in
>> "/etc/boot/menu.lst" is set to the right value.
>
> I ha
Please CC me on reply, since I am not subscribed to the list, because my
mailbox is quite limited.
Am 05.12.2012 17:01, schrieb Tom H:
> On Wed, Dec 5, 2012 at 8:40 AM, Marcus Blumhagen
> wrote:
>> just recently I was faced with a non-booting remote box running
>> Debian 6.0 (Squeeze).
>> [...]
On Wed, Dec 5, 2012 at 8:40 AM, Marcus Blumhagen
wrote:
> Please CC me on reply, since I am not subscribed to the list.
I consider rude not to subscribe to a list asking for help - but
that's just me...
> just recently I was faced with a non-booting remote box running Debian 6.0
> (Squeeze).
Please CC me on reply, since I am not subscribed to the list.
Hello,
just recently I was faced with a non-booting remote box running Debian
6.0 (Squeeze). Lacking access to any kind of console, I was quite
clueless why it wouldn´t come up after what should have been a routine
reboot. I have a
On Sat, Jan 22, 2011 at 8:24 AM, Jack Schneider wrote:
> On Sat, 22 Jan 2011 04:54:32 -0500
> Tom H wrote:
>
>> On Fri, Jan 21, 2011 at 8:51 PM, Jack Schneider
>> wrote:
>> >
>> > I think I found a significant glitch.. I appears that mdadm is
>> > confused. I think it happened when I created
On Sat, 22 Jan 2011 04:54:32 -0500
Tom H wrote:
> On Fri, Jan 21, 2011 at 8:51 PM, Jack Schneider
> wrote:
> >
> > I think I found a significant glitch.. I appears that mdadm is
> > confused. I think it happened when I created the /dev/md2 array
> > from the new disks. It looks like the meta
On Fri, Jan 21, 2011 at 8:51 PM, Jack Schneider wrote:
>
> I think I found a significant glitch.. I appears that mdadm is
> confused. I think it happened when I created the /dev/md2 array from
> the new disks. It looks like the metadata 1.2 vs 0.90 configs is the
> culprit...
>
> Here's the
On Tue, 18 Jan 2011 17:31:29 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > It booted to the correct grub menu then to Busy Box. I am thinking
> > it goes to BB because it can't find /var and or /usr on the
> > md1/sda5 LVM partition.
>
> Very likely.
>
> > I checked /proc/mdstat and lo &
Jack Schneider wrote:
> It booted to the correct grub menu then to Busy Box. I am thinking it
> goes to BB because it can't find /var and or /usr on the md1/sda5 LVM
> partition.
Very likely.
> I checked /proc/mdstat and lo & behold there was md1:active
> with correct partitions and md0: active a
On Tue, 18 Jan 2011 16:19:11 -0200
Henrique de Moraes Holschuh wrote:
> On Tue, 18 Jan 2011, Jack Schneider wrote:
> > Both /etc/fstab and /etc/mtab show entries for /dev/md126..
> >
> > What the ... ?
>
> After you modified thei files in the real filesystem, did you update
> the initramfs?
>
On Tue, 18 Jan 2011, Jack Schneider wrote:
> Both /etc/fstab and /etc/mtab show entries for /dev/md126..
>
> What the ... ?
After you modified thei files in the real filesystem, did you update the
initramfs?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all an
On Mon, 17 Jan 2011 20:43:16 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > mdadm --stop /dev/md125
> > > mdadm --assemble /dev/md0
> > > --update=super-minor /dev/sda1 /dev/sdc1
> > >
> > > mdadm --stop /dev/126
> > > mdadm --assemble /dev/md1
> > > --update=
On Mon, 17 Jan 2011 20:43:16 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > mdadm --stop /dev/md125
> > > mdadm --assemble /dev/md0
> > > --update=super-minor /dev/sda1 /dev/sdc1
> > >
> > > mdadm --stop /dev/126
> > > mdadm --assemble /dev/md1
> > > --update=
Jack Schneider wrote:
> Bob Proulx wrote:
> > mdadm --stop /dev/md125
> > mdadm --assemble /dev/md0 --update=super-minor /dev/sda1 /dev/sdc1
> >
> > mdadm --stop /dev/126
> > mdadm --assemble /dev/md1 --update=super-minor /dev/sda5 /dev/sdc5
>
> Bob, a small glitch. mdadm:/dev/sda1 exists
On Mon, 17 Jan 2011 15:50:12 -0600
Jack Schneider wrote:
> On Mon, 17 Jan 2011 12:48:29 -0700
> Bob Proulx wrote:
>
> > Jack Schneider wrote:
> > > Bob Proulx wrote:
> > > > But, and this is an important but, did you previously add the
> > > > new disk array to the LVM volume group on the above
On Mon, 17 Jan 2011 12:48:29 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > But, and this is an important but, did you previously add the new
> > > disk array to the LVM volume group on the above array? If so
> > > then you are not done yet. The LVM volume group won
Jack Schneider wrote:
> Bob Proulx wrote:
> > Note that if you add new disk to the lvm root volume group then you
> > also need to rebuild the initrd or your system won't be able to
> > assemble the array at boot time and will fail to boot. (Saying that
> > mostly for people who find this in the a
On Mon, 17 Jan 2011 12:48:29 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:> will be well..
>
> I have my fingers crossed for you that it will all be okay.
>
> > I have not done the things you have suggested above. I'll wait for
> > your response and then go!!!
>
> Plea
Jack Schneider wrote:
> Bob Proulx wrote:
> > But, and this is an important but, did you previously add the new disk
> > array to the LVM volume group on the above array? If so then you are
> > not done yet. The LVM volume group won't be able to assemble without
> > the new disk. If you did then
On Mon, 17 Jan 2011 07:19:03 -0600
Jack Schneider wrote:
> On Sun, 16 Jan 2011 18:42:49 -0700
> Bob Proulx wrote:
>
> > Jack,
> >
> > With your pastebin information and the mdstat information (that last
> > information in your mail and pastebins was critical good stuff) and
> > I found this ol
On Sun, 16 Jan 2011 18:42:49 -0700
Bob Proulx wrote:
> Jack,
>
> With your pastebin information and the mdstat information (that last
> information in your mail and pastebins was critical good stuff) and
> I found this old posting from you too: :-)
>
> http://lists.debian.org/debian-user/200
Jack,
With your pastebin information and the mdstat information (that last
information in your mail and pastebins was critical good stuff) and
I found this old posting from you too: :-)
http://lists.debian.org/debian-user/2009/10/msg00808.html
With all of that I deduce the following:
/dev/
On Sat, 15 Jan 2011 16:57:46 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > Jack Schneider wrote:
> > > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > > until ~7 days ago) There are 4 drives, 2 of which had never been
> > > > used or formatted.
On Sat, 15 Jan 2011 16:57:46 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > Jack Schneider wrote:
> > > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > > until ~7 days ago) There are 4 drives, 2 of which had never been
> > > > used or formatted.
On Sat, 15 Jan 2011 16:57:46 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > Bob Proulx wrote:
> > > Jack Schneider wrote:
> > > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > > until ~7 days ago) There are 4 drives, 2 of which had never been
> > > > used or formatted.
On Sat, 15 Jan 2011, Tom H wrote:
> On Sat, Jan 15, 2011 at 9:06 AM, Henrique de Moraes Holschuh
> wrote:
> > On Sat, 15 Jan 2011, Jack Schneider wrote:
> >> > >> You might want to try configuring grub and fstab to use UUID's
> >> > >> instead of /dev/mdX. That removes the possibility that the ke
Jack Schneider wrote:
> Bob Proulx wrote:
> > Jack Schneider wrote:
> > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > until ~7 days ago) There are 4 drives, 2 of which had never been
> > > used or formatted. I configured a new array using Disk Utility from
> > > a live Ubun
On Sat, Jan 15, 2011 at 5:29 PM, Jack Schneider wrote:
> On Fri, 14 Jan 2011 05:25:45 -0700
> Bob Proulx wrote:
>> Jack Schneider wrote:
>> >
>> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> > until ~7 days ago) There are 4 drives, 2 of which had never been
>> > used or form
On Sat, Jan 15, 2011 at 9:06 AM, Henrique de Moraes Holschuh
wrote:
> On Sat, 15 Jan 2011, Jack Schneider wrote:
>> > >> You might want to try configuring grub and fstab to use UUID's
>> > >> instead of /dev/mdX. That removes the possibility that the kernel
>> > >> will change the mdX designation
On Sat, Jan 15, 2011 at 8:24 AM, Jack Schneider wrote:
> On Fri, 14 Jan 2011 12:16:37 -0500
> Tom H wrote:
>> >> >
> [BIG SNIP]
>
>> >> You might want to try configuring grub and fstab to use UUID's
>> >> instead of /dev/mdX. That removes the possibility that the kernel
>> >> will change the mdX
On Fri, 14 Jan 2011 05:25:45 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > until ~7 days ago) There are 4 drives, 2 of which had never been
> > used or formatted. I configured a new array using Disk Utility from
> > a live U
On Sat, 15 Jan 2011 12:06:11 -0200
Henrique de Moraes Holschuh wrote:
> On Sat, 15 Jan 2011, Jack Schneider wrote:
> > > >> You might want to try configuring grub and fstab to use UUID's
> > > >> instead of /dev/mdX. That removes the possibility that the
> > > >> kernel will change the mdX desig
On Sat, 15 Jan 2011, Jack Schneider wrote:
> > >> You might want to try configuring grub and fstab to use UUID's
> > >> instead of /dev/mdX. That removes the possibility that the kernel
> > >> will change the mdX designations.
> > >>
> > >> Use blkid to find out the UUID's of your partitions.
Wha
On Fri, 14 Jan 2011 05:25:45 -0700
Bob Proulx wrote:
> Jack Schneider wrote:
> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > until ~7 days ago) There are 4 drives, 2 of which had never been
> > used or formatted. I configured a new array using Disk Utility from
> > a live U
On Fri, 14 Jan 2011 12:16:37 -0500
Tom H wrote:
> >> >
[BIG SNIP]
> >> You might want to try configuring grub and fstab to use UUID's
> >> instead of /dev/mdX. That removes the possibility that the kernel
> >> will change the mdX designations.
> >>
> >> Use blkid to find out the UUID's of your p
On Fri, Jan 14, 2011 at 7:06 AM, Jack Schneider wrote:
> On Thu, 13 Jan 2011 17:43:53 -0500
> Rob Owens wrote:
>> On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
>> >
>> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> > until ~7 days ago) There are 4 drives, 2
On Thu, Jan 13, 2011 at 5:43 PM, Rob Owens wrote:
> On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
>>
>> I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> until ~7 days ago) There are 4 drives, 2 of which had never been
>> used or formatted. I configured a new arra
On Fri, 14 Jan 2011 06:06:17 -0600
Jack Schneider wrote:
> On Thu, 13 Jan 2011 17:43:53 -0500
> Rob Owens wrote:
>
> > On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
> > >
> > > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > > until ~7 days ago) There are 4
Jack Schneider wrote:
> I have a raid1 based W/S running Debian Squeeze uptodate. (was
> until ~7 days ago) There are 4 drives, 2 of which had never been
> used or formatted. I configured a new array using Disk Utility from a
> live Ubuntu CD. That's where I screwed up... The end result was the
> n
On Thu, 13 Jan 2011 17:43:53 -0500
Rob Owens wrote:
> On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
> >
> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
> > until ~7 days ago) There are 4 drives, 2 of which had never been
> > used or formatted. I configured a
On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
>
> I have a raid1 based W/S running Debian Squeeze uptodate. (was
> until ~7 days ago) There are 4 drives, 2 of which had never been
> used or formatted. I configured a new array using Disk Utility from a
> live Ubuntu CD. That's whe
I have a raid1 based W/S running Debian Squeeze uptodate. (was
until ~7 days ago) There are 4 drives, 2 of which had never been
used or formatted. I configured a new array using Disk Utility from a
live Ubuntu CD. That's where I screwed up... The end result was the
names of the arrays were changed
Hi Alan,
On 20 Jul 2010, at 12:52, Alan Chandler wrote:
> Lets take this back to the list - not keep it between us - and I am
> subscribed to the list so no need to copy me.
Ah. Sorry. I didn't realise I had only mailed you directly.
> I don't know. When I have had a problem before, I have ju
On 18/07/10 18:30, Matthew Glubb wrote:
Hi Alan,
Thanks very much for your reply.
Lets take this back to the list - not keep it between us - and I am
subscribed to the list so no need to copy me.
On 17 Jul 2010, at 20:08, Alan Chandler wrote:
You don't include the one piece of informati
Hello,
The four failures seem really high to me too. This might be a silly
question but: have you checked/replaced the controller and cables yet?
I had a machine with four disks and one of them picked randomly were
reported as bad every few weeks (all of them connected to the motherboard).
I rul
Matthew Glubb put forth on 7/17/2010 3:11 AM:
> Normally in the past when a disk has failed, I have dropped the offending
> disk from the array, replaced the disk, booted, rebuilt the filesystem on the
> new disk and re-synced the array. I've done this about four times with this
> method.
Once
On 17/07/10 09:11, Matthew Glubb wrote:
Hi All,
I have a problem replacing a failed disk with a LVM volume on a RAID1 array.
Normally in the past when a disk has failed, I have dropped the offending disk
from the array, replaced the disk, booted, rebuilt the filesystem on the new
disk and re-
Hi All,
I have a problem replacing a failed disk with a LVM volume on a RAID1 array.
Normally in the past when a disk has failed, I have dropped the offending disk
from the array, replaced the disk, booted, rebuilt the filesystem on the new
disk and re-synced the array. I've done this about fou
On Fri, 2 Apr 2010 12:35:50 -0400 (EDT), Paul E Condon wrote:
> For installing Squeeze, I think the business card CD is more useful
> than the daily build. The business card CD has far less new stuff
> burnt onto the media, only what is absolutely necessary to setting up
> the local end of the link
; bootloader to the mbr(s). Grub failed, both grub2 and legacy. lilo also
> > would not install.
> >
> > I was installing via netboot and had this failure with both the
> > 2010-02-11 netboot.tar.gz release for amd64 as well as the 2010-03-30
> > amd64 snapshot.
>
;
> I was installing via netboot and had this failure with both the
> 2010-02-11 netboot.tar.gz release for amd64 as well as the 2010-03-30
> amd64 snapshot.
>
> I finally got a running squeeze on raid1 by using lenny's d-i to install
> lenny, then upgrading (following &#
3-30
amd64 snapshot.
I finally got a running squeeze on raid1 by using lenny's d-i to install
lenny, then upgrading (following '/msg dpkg lenny->squeeze' instructions
from #debian). This now works fully upgraded to grub2 and squeeze.
I need to proceed with using that system rig
Zhengquan Zhang wrote:
Dear debian community,
I will build up a backup server which has 2x1T + 1x250G drives. the size
of the one full backup will be about 400G.
My initial plan was to install debian lenny on the 250G drive. leave
2x1T drive untouched and then make software raid1 on them after
Dear debian community,
I will build up a backup server which has 2x1T + 1x250G drives. the size
of the one full backup will be about 400G.
My initial plan was to install debian lenny on the 250G drive. leave
2x1T drive untouched and then make software raid1 on them after the
installation.
I hav
On Friday 23 February 2007 16:12, José Pablo Fernández wrote:
> So, nobody knows what might be going on here?
Nevermind, it is now working (although I don't know what solved it, I hate
that).
--
José Pablo Fernández
[EMAIL PROTECTED]
So, nobody knows what might be going on here?
On Wednesday 21 February 2007 01:15, José Pablo Fernández wrote:
> I have a raid1 setup with three partitions:
>
> md0, mounted on /, composed of /dev/sda1 and /dev/sdb1
> md1, mounted on swap, composed of /dev/sda2 and /dev/sdb2
> md2, mounted on swap
On Wednesday 21 February 2007 14:43, martin f krafft wrote:
> also sprach José Pablo Fernández <[EMAIL PROTECTED]>
[2007.02.21.1836 +0100]:
> > > Have a look at what /usr/share/mdadm/mkconf outputs.
> >
> > There's no such file. I used apt-file to search for it and I've only got:
>
> Ah, you are s
also sprach José Pablo Fernández <[EMAIL PROTECTED]> [2007.02.21.1836 +0100]:
> > > Those lines are the output of a command, mdadm --detail --scan
> >
> > So? :)
>
> I can't modify the output of a command (unless I modify the sources of the
> command, of course).
mdadm --detail is not what you u
On Wednesday 21 February 2007 14:26, martin f krafft wrote:
> also sprach José Pablo Fernández <[EMAIL PROTECTED]>
[2007.02.21.1812 +0100]:
> > Those lines are the output of a command, mdadm --detail --scan
>
> So? :)
I can't modify the output of a command (unless I modify the sources of the
com
also sprach José Pablo Fernández <[EMAIL PROTECTED]> [2007.02.21.1812 +0100]:
> Those lines are the output of a command, mdadm --detail --scan
So? :)
Have a look at what /usr/share/mdadm/mkconf outputs.
> The other set of similar lines which are the config in
> /etc/mdadm/mdadm.conf are the only
On Wednesday 21 February 2007 07:32, martin f krafft wrote:
> also sprach José Pablo Fernández <[EMAIL PROTECTED]>
[2007.02.21.0515 +0100]:
> > ARRAY /dev/md2 level=raid1 num-devices=2 UUID=[...]
> >devices=/dev/sda3,/dev/sdb3
> > ARRAY /dev/md0 level=raid1 num-devices=2 UUID=[...]
> >devi
also sprach José Pablo Fernández <[EMAIL PROTECTED]> [2007.02.21.0515 +0100]:
> ARRAY /dev/md2 level=raid1 num-devices=2 UUID=[...]
>devices=/dev/sda3,/dev/sdb3
> ARRAY /dev/md0 level=raid1 num-devices=2 UUID=[...]
>devices=/dev/sda1
> ARRAY /dev/md1 level=raid1 num-devices=2 UUID=[...]
>
I have a raid1 setup with three partitions:
md0, mounted on /, composed of /dev/sda1 and /dev/sdb1
md1, mounted on swap, composed of /dev/sda2 and /dev/sdb2
md2, mounted on swap, composed of /dev/sda3 and /dev/sdb3
I am not sure how it was installed because it was done a long time ago, I
don't e
Hello,
My testing box is an amd64, 1 G ram with dual 80 GB Seagate SATA drives,
running Etch. I'm new to the LVM/raid1 concept. Following advice I
received here (or was it on amd64; no matter, its not amd64 specific), I
currently have both disks partitioned the same:
1 small
On Tue, Aug 17 at 10:46PM -0700, Alvin Oga wrote:
> On Tue, 17 Aug 2004, Alvin Oga wrote:
> > On Tue, 17 Aug 2004, Will Trillich wrote:
> > > lemme check to make sure i grok the recommendation -- HDA and
> > > HDB are primary and secondary on the first bus (C: and D: in
> > > windows parlance), and
On Tue, 17 Aug 2004, Alvin Oga wrote:
>
> hi ya will
>
> On Tue, 17 Aug 2004, Will Trillich wrote:
>
> > lemme check to make sure i grok the recommendation -- HDA and
> > HDB are primary and secondary on the first bus (C: and D: in
> > windows parlance), and HDC and HDD are primary and second
hi ya will
On Tue, 17 Aug 2004, Will Trillich wrote:
> lemme check to make sure i grok the recommendation -- HDA and
> HDB are primary and secondary on the first bus (C: and D: in
> windows parlance), and HDC and HDD are primary and secondary on
> the second bus (E: and F: in windows parlance).
On Sun, Aug 15 at 09:53PM -0700, Alvin Oga wrote:
> On Sun, 15 Aug 2004, Will Trillich wrote:
> > $ sfdisk -d
> > # partition table of /dev/hda
> > unit: sectors
> >
> > /dev/hda1 : start= 63, size= 192717, Id=83, bootable
> > /dev/hda2 : start= 192780, size= 1959930, Id=82
> > /dev/hda3
I've got a setup here for root software raid1, installed a few months ago.
Running woody, on a pair of 40 gig IDE drives, installed as /dev/hda and
/dev/hdc.
I installed the raid1 root as per the documentation on tldp.org
We had a power outage over the weekend, and when the system came back up,
i
Thanks for the help, i solved it so:
i had a spare partition-pair mirrored, i copied the / fs on it, told lilo
that this new md will be the new root fs, and voila!
thanks to all who helped.
charlie
--
Vegh Karoly
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
hi ya karoly
since hda1 is NOT in your /dev/md0 ... you're stuck...
-- once it all works... use /dev/hda and /dev/hdc instead
-- remove all the extra (disk info) jibberish in your lilo.conf
and raidtab
but ... first, try building your raid manually...
On Fri, 17 May 2002, Alvin Oga wrote:
> hi ya karoly...
hi & thx for the help,
> did you try "raidsetfaulty" ?
> raidsetfaulty /dev/md0 /dev/hda1
> raidhotremove /dev/md0 /dev/hda1
~ # raidsetfaulty /dev/md1 /dev/hda1
~ # raidhotremove /dev/md1 /dev/hda1
/dev/md1: can not hot-remove
hi ya karoly...
did you try "raidsetfaulty" ?
raidsetfaulty /dev/md0 /dev/hda1
raidhotremove /dev/md0 /dev/hda1
..
what does your lilo.conf look like ??
- does it have initrd.gz in it ??
- which kernel is in initrd.gz ??
thanx
alvin
On Fri, 17 May 2002,
On Thu, 16 May 2002, Alvin Oga wrote:
> if you are trying to hotadd ... you need to hotremove it first...
~ # cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md1 : active raid1 hdb1[0]
4200896 blocks [2/1] [U_]
md2 : active raid1 hda2[1] hdb2[0]
6297408 blocks [2/2]
On Thu, 16 May 2002, Dave Sherohman wrote:
> Take a close look at your boot messages. Your system most likely booted
> off /dev/hda1, then mounted /dev/md1 as /. If so, it's still running
> the kernel from hda1, which is the source of those active inodes.
i booted from a floopy, docu for this w
On Thu, May 16, 2002 at 02:21:35PM +0200, Karoly VEGH wrote:
> in the log:
>
> md: trying to hot-add hda1 to md1 ...
> md: can not import hda1, has active inodes!
> md: error, md_import_device() returned -16
>
> what am i supposed to do, to get rid of those ugly active inodes ?
Take a close look
hi ya
i dont quite understand the problem... besides the typo like /dev/rooot
if you are looking to "see" /dev/hda2 and /dev/hdb2
separately
- you wont ... its been raided together
if you are trying to hotadd ... you need to hotremove it first...
and might even need to h
On Thu, 16 May 2002, Ralf G. R. Bergs wrote:
> >~ # ls -l /dev/rooot
> >ls: /dev/rooot: No such file or directory
>^^^
of course you are right, but:
~> ls -l /dev/root
ls: /dev/root: No such file or directory
~>
charlie
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
On Thu, 16 May 2002 14:21:35 +0200 (MEST), Karoly VEGH wrote:
>~ # ls -l /dev/rooot
>ls: /dev/rooot: No such file or directory
^^^
Well, THIS device you probably won't even find if your setup is right. :-)
--
Sign the EU petition against SPAM: L I N U X .~.
http://www.
Hi,
I have two disks (same size, same partitions) in raid1, but to the / fs i
cannot add both hda's:
/etc/raidtab:
[..]
# /usr mirror
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 32
persistent-superblock 1
Hi
No, the /boot - directory is on my / partition.
I will try you suggestion soon.
Right now my main problem is that when I make a rescue from a floppy.
I have to run fsck manually on /dev/md0
then after a reboot i have to run fsck again.
It is like /dev/md0 is not properly unmounted ???
Hi Knud,
do you have your boot image on the raid disk?
The image should reside in the /boot - directory and this directory has to be
on a separate partition. Lilo cannot boot from a raid partition.
The /boot partition could be very small, I choose 25 MB.
That's enough for a lot of images.
Hope t
Knud Sørensen wrote:
>
> I trying to make a system boot on a soft raid1 device.
>
> I have been following
> http://linuxdoc.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.12
> method 2.
>
> If you have it working I would be happy for some help.
>
> I would like to see your lilo.conf, fstab, raidtab.
I trying to make a system boot on a soft raid1 device.
I have been following
http://linuxdoc.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.12
method 2.
If you have it working I would be happy for some help.
I would like to see your lilo.conf, fstab, raidtab.
On boot I get
L 01 01 01 01 01 ...
W
89 matches
Mail list logo
