Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: tunnie on 20 August 2011, 19:31:02
-
How easy is it to replace hard disk on one?
The fool with root access The highly competition techy might be asked to replace one!
Never touched blade servers before.... don't even know how to remove them from the Centre :-[
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
-
How easy is it to replace hard disk on one? The fool with root access The highly competition techy might be asked to replace one!
Never touched blade servers before.... don't even know how to remove them from the Centre :-[
Are you planning on taking it away with you then ;D
Seriously, being IBM, i would hope they are easy accessible, hot swappable drives.
So......just unplug the caddy of the drive you want to replace and plug the new caddy(with new drive) in.
Worth checking with some one else first, but in my IT days years ago......if the disk array was hardware raid....it was pull the old drive out and plug the new one in, and pray it didnt crash ;D and then went on to rebuild itself :y
-
No changed one on an IGM blade (we have hardware peeps for such simple tasks, people who do get off their backsides ;D)
Proliant blades and Sun blades are simple, hot swap units, same as their standalone servers of same era, can't imagine IBM would be any different...
-
not sure its the right model but looks fairly straight forward http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00718745/c00718745.pdf
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
What make? Never seen one without hot swap disks...
-
How easy is it to replace hard disk on one? The fool with root access The highly competition techy might be asked to replace one!
Never touched blade servers before.... don't even know how to remove them from the Centre :-[
Are you planning on taking it away with you then ;D
I was assuming it needed to be removed in order to replace HD :-[
Regarding RAID, i've no idea what the setup is. The genius company I used to work for, decided to sack everyone who knew anything about the systems we ran.
Its now down to 5 people (from 60 at its peak) - I'm the only technical member of staff, so not a good start ;D
No changed one on an IGM blade (we have hardware peeps for such simple tasks, people who do get off their backsides ;D)
Proliant blades and Sun blades are simple, hot swap units, same as their standalone servers of same era, can't imagine IBM would be any different...
I might need to see if they have left any manuals around! Did a hot swappable PSU for first time few weeks back.
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
Well these blades are running Red Hat, but as the whole service is fubared, the blade can be shutdown :)
-
I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
Actually, I bet Windows would cope far better than most other server systems :P
-
server, without a hot swap disk :-?
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
Well these blades are running Red Hat, but as the whole service is fubared, the blade can be shutdown :)
Built properly, a failed HDD shouldn't affect service on a server, unless they are using software mirroring....
-
server, without a hot swap disk :-?
OOF's isn't ::)
-
server, without a hot swap disk :-?
OOF's isn't ::)
members , must put the hands in the pocket me thinks ;D :y
-
server, without a hot swap disk :-?
OOF's isn't ::)
members , must put the hands in the pocket me thinks ;D :y
For our needs, a 30min outage to replace a disk isn't that important.
Besides, as the server hardware comes out of my pocket, I was the one making the choice between hot plug disks, or some new tyres on the Rover ;D ;D
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
Well these blades are running Red Hat, but as the whole service is fubared, the blade can be shutdown :)
Built properly, a failed HDD shouldn't affect service on a server, unless they are using software mirroring....
It all went to poo when they ditched their hosting at rackspace to save money, services where brought in house and everything screwed up!
We are amazed its lasted as long as it has, I cannot get a Sybase Database to boot, it keeps corrupting chucks of the DB, the just disappear from the file system :-?
At first it was just one, now 6 chucks have gone! Just not listed there.... :-/
We got it all back, i left it alone, came back later in day and the database had died again, booting it again chucks had disappeared! :-/
-
server, without a hot swap disk :-?
OOF's isn't ::)
members , must put the hands in the pocket me thinks ;D :y
For our needs, a 30min outage to replace a disk isn't that important.
Besides, as the server hardware comes out of my pocket, I was the one making the choice between hot plug disks, or some new tyres on the Rover ;D ;D
;D ;D I can guess the choice ;D :y
-
server, without a hot swap disk :-?
OOF's isn't ::)
members , must put the hands in the pocket me thinks ;D :y
For our needs, a 30min outage to replace a disk isn't that important.
Besides, as the server hardware comes out of my pocket, I was the one making the choice between hot plug disks, or some new tyres on the Rover ;D ;D
;D ;D I can guess the choice ;D :y
Given that Mrs TB cooks my dinner, and you lot don't, tyres for her car were always going to win ;D
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
Well these blades are running Red Hat, but as the whole service is fubared, the blade can be shutdown :)
Built properly, a failed HDD shouldn't affect service on a server, unless they are using software mirroring....
It all went to poo when they ditched their hosting at rackspace to save money, services where brought in house and everything screwed up!
We are amazed its lasted as long as it has, I cannot get a Sybase Database to boot, it keeps corrupting chucks of the DB, the just disappear from the file system :-?
At first it was just one, now 6 chucks have gone! Just not listed there.... :-/
We got it all back, i left it alone, came back later in day and the database had died again, booting it again chucks had disappeared! :-/
:-?
normally , the database will be marked suspect in case of some problems.. :-/
-
Was fsck running when it came back up?
-
server, without a hot swap disk :-?
OOF's isn't ::)
members , must put the hands in the pocket me thinks ;D :y
For our needs, a 30min outage to replace a disk isn't that important.
Besides, as the server hardware comes out of my pocket, I was the one making the choice between hot plug disks, or some new tyres on the Rover ;D ;D
;D ;D I can guess the choice ;D :y
Given that Mrs TB cooks my dinner, and you lot don't, tyres for her car were always going to win ;D
thats sure.. my stomach is also the #1 ;D :y
-
Was fsck running when it came back up?
Yes, after I rebooted the box i did:
Login as root
umount sda1,umount sdb1, umount sdc1
e2fsck sda1, e2fsck sdb1, e2fsck sdc1
mount –a
Login as Sybase & attempt to start, gets stuck at master device size :(
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
What make? Never seen one without hot swap disks...
I .. can't remember :) I think they were HP, but I could be wrong - since I changed roles my access card doesn't even let me into the lab where the fun stuff is anymore :'(
-
Was fsck running when it came back up?
Yes, after I rebooted the box i did:
Login as root
umount sda1,umount sdb1, umount sdc1
e2fsck sda1, e2fsck sdb1, e2fsck sdc1
mount –a
Login as Sybase & attempt to start, gets stuck at master device size :(
did you get any error messages on fsck ?
didi you mount all volumes adressed in sybase ?
otherwise must start normally :-/
-
Was fsck running when it came back up?
Yes, after I rebooted the box i did:
Login as root
umount sda1,umount sdb1, umount sdc1
e2fsck sda1, e2fsck sdb1, e2fsck sdc1
mount –a
Login as Sybase & attempt to start, gets stuck at master device size :(
Did you need to run fsck? Was the database loaded before unmounting?
-
No different to a regular server, at least it wasn't in the blade server we had in the lab at work. Shut the blade down, release it (just like you'd release a drive in a storage array) and slide it out.
From then on it's just a regular PC in a very small case..
Shouldn't need to shut it down. Being a blade, it'll be Enterprise class, thus 99% likely hot swap.
Hm.. our blades were obviously different, then :) You couldn't get at the drives without taking the casing off the blade - and since the blade is the entire server.. I can't imagine Windows would have been too happy with the power being unceremoniously removed as the blade was yanked out :D
What make? Never seen one without hot swap disks...
I .. can't remember :) I think they were HP, but I could be wrong - since I changed roles my access card doesn't even let me into the lab where the fun stuff is anymore :'(
Can't think of an HP blade that doesn't have a SMART Array and hot plug disks. But then I only really get involved with HP Proliants, not idea if they do Integrity based Blades...
-
Was fsck running when it came back up?
Yes, after I rebooted the box i did:
Login as root
umount sda1,umount sdb1, umount sdc1
e2fsck sda1, e2fsck sdb1, e2fsck sdc1
mount –a
Login as Sybase & attempt to start, gets stuck at master device size :(
Did you need to run fsck? Was the database loaded before unmounting?
Those are the instructions I have, no the database was not loaded....