1 |
On Saturday 20 February 2010, Iain Buchanan wrote: |
2 |
> On Sat, 2010-02-20 at 10:46 +0100, Francesco Talamona wrote: |
3 |
> > > Should I be able to mount them automatically and let the SW RAID |
4 |
> > > module sort it out or do I have to know how they're tied |
5 |
> > > together beforehand? |
6 |
> > > |
7 |
> > > md: looking for a shared spare drive |
8 |
> > > md100: no spare disk to reconstruct array! -- continuing in |
9 |
> > > degraded mode |
10 |
> > > md: recovery thread finished ... |
11 |
> > > md: hde5 [events: 000003a5]<6>(write) hde5's sb offset: 273024 |
12 |
> > > md: hdg5 [events: 000003a5]<6>(write) hdg5's sb offset: 273024 |
13 |
> > > XFS mounting filesystem md(9,100) |
14 |
> > > Ending clean XFS mount for filesystem: md(9,100) |
15 |
> > > |
16 |
> > > The partitions look like: |
17 |
> > > 9 100 546112 md100 |
18 |
> > > 9 101 273024 md101 |
19 |
> > |
20 |
> > It seems it has correctly mounted its partition... Can't you find |
21 |
> > it? |
22 |
> |
23 |
> This is with the server recovery console, which is basically just a |
24 |
> web page. No shell access. There's not much I can do to get at |
25 |
> md100 and md101 (is this what software RAID devices usually appear |
26 |
> as?) |
27 |
> |
28 |
> > I have the feeling that you are messing it up. If I understand it |
29 |
> > correctly the server has an hardware RAID controller, that has to |
30 |
> > be managed via its drivers. |
31 |
> |
32 |
> I think it's software RAID. There is no RAID controller AFAICT. All |
33 |
> 4 drives are visible to the BIOS as Primary and Secondary Master and |
34 |
> Slaves. |
35 |
|
36 |
This isn't a proof: most hardware RAID are proprietary software |
37 |
solutions pretending to be hardware. Linux without the driver can't see |
38 |
the logical volume and shows all the physical drives. |
39 |
|
40 |
You should do some research about that server hardware... Aren't snap |
41 |
equipped with PERC controller?. |
42 |
|
43 |
> > Another thing can come very useful: we once had a similar problem, |
44 |
> > we ended up borrowing one identical disc from another running |
45 |
> > server to put the array back online, we recovered our data, then |
46 |
> > restored the other server's array. |
47 |
> |
48 |
> That's a possibility given what I can find on Google, however these |
49 |
> are few and far between, so I'd have to find someone willing to send |
50 |
> their drive to me (or vice versa) or send me the OS, which |
51 |
> overlandstorage doesn't like! |
52 |
|
53 |
What happens if you physically remove the drive marked as bad? |
54 |
|
55 |
You may image it for backup, then format it at low level, then put it |
56 |
back in place as if it was brand new. Or add a similar disk to be |
57 |
considered spare by the controller (given that it is looking for a spare |
58 |
disk in first instance). |
59 |
|
60 |
Most controller have automated procedures to manage failures, disk swaps |
61 |
and so on. |
62 |
|
63 |
For this reason you can't be sure that the inspection operations you are |
64 |
doing are read only. Unless the drives are attached to another machine |
65 |
with a trusted OS doing nothing on its own. |
66 |
|
67 |
The ideas given above may let you to waste all of your data, be very |
68 |
careful and patient. |
69 |
|
70 |
Good luck. |
71 |
Francesco |
72 |
|
73 |
-- |
74 |
Linux Version 2.6.32-gentoo-r5, Compiled #2 SMP PREEMPT Wed Feb 17 |
75 |
20:30:02 CET 2010 |
76 |
Two 2.9GHz AMD Athlon 64 Processors, 4GB RAM, 11659 Bogomips Total |
77 |
aemaeth |