Hi,
Got the problems solved. I couldn't solve the problem by using the rescue
disk, as it wouldn't let me stop the raid array.
What I did was drop into the maintenance mode:
mdadm --assemble /dev/md1 /dev/sdd1 /dev/sde1 //This should recreate the
array
mdadm --detail --scan
Hello,
I've been too nervous to reboot, so I've left it in the rescue mode at the
point where I assembled the raid arrays and went into boot at the \
partition.
Tried to run:
mdadm --stop /dev/md127
but got a mdadm: failed to stop array /dev/md127: Device or resource busy.
Perhaps a running
Thanks Bob, like I say, very much appreciated and I'll let you know how it
goes!
I'd like to hear about the optimisations, but I think I'll wait till I get
the system rebuilt!
James
On 4 July 2013 00:47, Bob Proulx b...@proulx.com wrote:
James Allsopp wrote:
Thanks Bob, really can't thank
James Allsopp wrote:
I'd like to hear about the optimisations, but I think I'll wait till I get
the system rebuilt!
Basically I had expected you to use either rescue mode of the d-i or a
livecd or other to assemble the arrays. You did. But neither array
came up completely correct. One came
Thanks Bob, really can't thank you enough. Just to be clear about this, I'd
do these commands from the rescue disk after I have assembled the arrays
and gone to the bash shell?
Much appreciated,
James
On 2 July 2013 22:44, Bob Proulx b...@proulx.com wrote:
James Allsopp wrote:
One other
James Allsopp wrote:
Thanks Bob, really can't thank you enough. Just to be clear about this, I'd
do these commands from the rescue disk after I have assembled the arrays
and gone to the bash shell?
Short answer: Yes. Go for it!
Longer answer: There are all kinds of things I want to say here.
Thanks Bob, I'll get back to after I've followed your instructions. I think
I'm going to have to learn to type with crossed fingers!
I think I initially sorted out all my partitions manually, rather than
directly using the installer to do it automatically,
Really appreciated,
James
On 2 July
One other point sda isn't the boot hard drive, that's the partitions /sdb1
and sdc1, but these should be the same (I thought I'd mirrored them to be
honest).
I tried mdadm --detail /dev/sdd1 but it didn't work. I have these results
if they help?
/dev/md1:
Version : 1.2
Creation Time :
For ruther information:
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.00
UUID : a529cd1b:c055887e:bfe78010:bc810f04
Creation Time : Fri Nov 20 09:37:34 2009
Raid Level : raid1
Used Dev Size : 972550912 (927.50 GiB 995.89 GB)
Array Size : 972550912 (927.50
James Allsopp wrote:
One other point sda isn't the boot hard drive, that's the partitions /sdb1
and sdc1, but these should be the same (I thought I'd mirrored them to be
honest).
I don't see sda anywhere. It might be a dual booting Windows disk?
Or other. But the BIOS will boot the first
Thanks Bob for your e-mail, it was really helpful. I think you've
identified the nub of the problem, not updating mdadm.conf and the
initramfs. However things are a bit unusual on the other side. I'm not
sure if the rescue disk or myself has screwed something up, but the second
raid which has
James Allsopp wrote:
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md126 : active raid1 sdb3[0] sdc3[1]
972550912 blocks [2/2] [UU]
So sdb3 and sdc3 are assembled into /dev/md126. That seems good. One
full array is assembled.
Is /dev/md126 your preferred name for that array?
Hi,
I have a debian machine which was on for a long time (~months). Just moved
house and rebooted and now it doesn't boot.
My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM
spanning them. Originally there was just one pair, but then I got two new
hard drives and added them. I
James Allsopp wrote:
I have a debian machine which was on for a long time (~months). Just moved
house and rebooted and now it doesn't boot.
Bummer.
My 4 harddrives are organised in pairs of RAID 1 (Mirrored) with LVM
spanning them. Originally there was just one pair, but then I got two new
14 matches
Mail list logo
