Re: How much of that was replacing dud drives?
HGST you mean?
(Hitachi ≠ HGST)
138 posts • joined 7 May 2010
HGST you mean?
(Hitachi ≠ HGST)
That is all
I had the pleasure of visiting a building where the architects managed to design the server room with a FOUR FOOT flloor void rather than the desired 4 inches. Somehow this cock-up of NASA dimensioning proportions made it through all checks and that's how the building was constructed.
By the time the building was completed and occupied, the data centre looked 'normal'... until you lifted a floor panel and stared into the void; this was one data centre where you **really** had to be careful if you left a floor panel out of place! There was so much space below the floor that the IT guys had installed servers down there - as my knees and back dscovered when I turned up to fit a new Ethernet card and was told which tile to lift to start my crawl.
> advances which aid or assist users who eyesight and/or coordination is failing.
A nice pair of Apple iEyes inserts...
Direct Cortex Inject (DCItm) for pure digital visiion, and only the occasional, discrete advertisement in the corner of your vision (unless you upgrade to the ad-free subscription package).
No....O's....O's for Macs.
"IoT mostly seems to be rich people taking dumb appliances adding data mining technology for the poor unwashed masses and then eventually charging far more to buy the original dumb appliance again that doesn't spy on you (for them of course)."
I call this "The bacon strategy":
* Once upon a time, bacon was just cured/smoked pork with nothing added; it tasted fine and cooked well.
* Then some bright spark worked out how to inject water into the process and sell a crappier version of bacon for greater profit.
* Over time, this crappy, water-laden bacon became the norm and everyone just accepted the state of play because they grew up with the shitty stuff.
* Next, the bacon companies started to sell 'traditional' bacon again with no added water, but because it was now 'special', they charged extra for a now-considered-premium product.
Great airline; the last (and I really mean LAST) time I flew with them, they upgraded my direct San Francisco to London Heathrow flight to include an additional 8 hours at the airport and a free visit to Dulles Washington. I effectively gained a WHOLE DAY of extra traveling for no extra charge and skipped a Monday at work; what's not to like!?
One thumb down when I checked at 10:27 - SOOO...someone disagrees that a quick image backup before applying the update is worth the time.
Jean Luc Picard facepalms in your general direction.
All of my home and work machines dual boot Windows 10 and Debian 8, and live in Debian most of the time. I forsee some liberal use of Clonezilla coming up before doing anything with Windows.
I am waiting for your call - I'm cheap too!
this file contains the function and procedure declarations
for the TurboPascal/Advanced NetWare interface}
Strvar = String;
function xtndopn(var Mode, Handle: Integer;var Filename: Strvar): Integer; external 'PASNETA.COM';
function setattr(var Func, Attribute: Integer; var Filename: Strvar): Integer; external xtndopn;
function eojstat(var Flag: Integer):integer; external xtndopn;
function PRLH_Log(var FileHandle,HiByteOffset,LoByteOffset,HiLockLen,
LoLockLen,Flags,TimeOut: Integer): Integer; external xtndopn;
function PRLH_Rel(var FileHandle,HiByteOffset,LoByteOffset,HiLockLen,
LoLockLen: Integer): Integer; external xtndopn;
function PRLH_Clr(var FileHandle,HiByteOffset,LoByteOffset,HiLockLen,
LoLockLen: Integer): Integer; external xtndopn;
function PRLF_Log(var fcb,HiByteOffset,LoByteOffset,HiLockLen,LoLockLen,
Flags,TimeOut: Integer): Integer; external xtndopn;
function PRLF_Rel(var fcb,HiByteOffset,LoByteOffset: Integer): Integer; external xtndopn;
function PRLF_Clr(var fcb,HiByteOffset,LoByteOffset: Integer): Integer; external xtndopn;
function PRLS_Lck(var Flags,TimeOut: Integer): Integer; external xtndopn;
function PRLS_Rel: Integer; external xtndopn;
function PRLS_Clr: Integer; external xtndopn;
function OpenSem(var Sema4: Strvar; var SemaValu,HiHandle,LoHandle,OpenCnt: Integer): Integer; external xtndopn;
function ExamSem(var HiHandle,LoHandle,SemaValu,OpenCnt: Integer): Integer; external xtndopn;
function WaitSem(var HiHandle,LoHandle,TimeOut: Integer): Integer; external xtndopn;
function SigSem(var HiHandle,LoHandle: Integer): Integer; external xtndopn;
function ClosSem(var HiHandle,LoHandle: Integer): Integer; external xtndopn;
Carbon is conductive. Small particles can cause real problems among tiny surface mount components and high frequency circuits.
It's all very well the BT router (maybe) pumping out more power, but wifi comms is a two-way thing and your tablet or phone etc. is going to be transmitting at the same strength it has always done....so if the device's signal couldn't make it back from the potting shed before it STILL aint gonna make it back now.
Must be a day with a 'y' in the name.
No - the 4th emergency service is the Coastguard.
/I think we have a few left.
The vouchers...don't forget the coloured vouchers...orange ones, green ones and...wow I bought enough to get a white and blue one!
Bless Doug Simmons...we had an electronics club stand at our school summer fair (about 1978/9) and I wrote to him for some marketing freebies and he sent a large box of catalogues and starship posters.
/Also 4 digits.
"The house prices must be low"
Rock bottom, I hear.
> > > Hey, why not have a backup? >>>Or RAID?<<<
You really didn't write that, did you!? Hand in your sysadmin card on the way out. Kthxbye.
Also never assume that the people who made and managed the backups are still around to restore them. Documentation - stored in several places FTW.
I was working up to a state of worry and agitation when the article mentioned apps getting rid of bankers, lawyers and estate agents. I'm so very torn now.
I'll just leave this here:
"The Acorn System 1 is a grandparent of the BBC micro:bit; it was designed by Sophie Wilson and Steve Furber, who went on to help develop the BBC Microcomputer.
Acorn System 1:
Processor: 8-bit 6502, 1MHz
Approx MIPS: 0.5
ROM: 512 bytes
Processor: 32-bit ARM Cortex M0, 16MHz
Approx MIPS: 13
Flash: 256kB "
/Sheldon Cooper would not have been so sloppy.
> It would probably have been better to hold off to next school year.
> My Pi probably boots up in around 15 seconds or so.
So, about 14 seconds more that a micro:bit ;-)
Help make the community happen - there's an Area 51 initiative on Stack Exchange to create a micro:bit Q&A site - please head over and upvote some of the questions that have not made it to 10 yet.
** Please don't upvote any question that already has 10 upvotes; they have already passed the needed score so it will be a wasted vote. **
Also check out this sub on Reddit: https://www.reddit.com/r/Micro_Bit/
(There's a couple of other micro:bit subs on Reddit, but that one is the most active)
I've upvoted this one, purely because it's a pain to head down the phone/tablet route only to find that support for your particular model...they're 'working on it'.
/Galaxy Note 10.1 tablet.
> Wow, I'm talking to Dr Sheldon Cooper... oops ;)
Nah, you're being corrected by someone working close to the project!
/I'm impartial to trains and have no fear of birds.
Agreed, the ultimate launch date was not good and has meant the micro:bits being delivered so close to the end of the school year that there was little point in bringing them into the curriculum.
I am a STEM ambassador and we have a growing network of members who are tooled up with micro:bits and able to support schools who wish to use the board in conjunction with curriculum activities. You should encourage your school to reach out to the STEM organisation to see who could help either directly or remotely.
I understand there was some talk about speccing the micro:bit with a larger RAM, but this would have meant moving to the next model of Nordic SoCs and the cost was considered too high.
The board is intended for basic coding and for that it's fine - if you require more RAM, then the micro:bit is probably not the right fit for your project.
I've seen 'successor' mentioned in official circles. not 'emulator', although there have been comments about hoping the micro:bit emulates the success of the BBC Micro, which is a completely different context.
The ecosystem for the micro:bit is getting there - notably the micropython team are making progress on an almost daily basis. I predict some people working hard during the impending Summer hols.
The Zero has no LED matrix display, no bluetooth, no accelerometer, no built-in switches and no magnetometer so it's hardly ready 'out of the box' to do anything, plus prepping one for use can be a bit of hassle. The micro:bit can almost hit the ground running; I have both and the micro:bit is the best fit for its intended purpose.The Zero could be step 2 on a coding journey unless one moves to the Arduino ecosystem or somethig like the ST Nucleo boards.
Catweazle holds the patent on electrickery:
> Of course not: all in-house IT systems have their DR plans fully documented, with a test failover performed monthly.
Actually we did a failover every two months on our in house system.
Yes, in-house IT can be a mess in many cases, but for any organisation with mission-critical parts kept in-house, *you* retain control of the specification and management of your live and redundant resources and can plan for business continuity and failover under your control and to a budget and resource pool that meets your requirements; perhaps even considering worse-case scenarios like hiring a shipping container data centre or, as in our case, being able to cannibalise other, less critical services, for parts while we wait for spares and an engineer to turn up within their 1/2/4/whatever hour response window.
As an example, we specced a standby system running a single unit tape backup/restore function (in case our autochanger failed) to have the same hardware as one of our primary servers. One day, the HP SAS caching controller on a live server failed and brought down the ERP system . While we were on the phone arranging a service call-out, another team member replaced the controller with the one from the 'spare' system. Total downtime was 12 minutes - and that was our only service break on that system in about 3 years.
When you rely on DR in a SAAS cloud-based environment, you won't likely have a dedicated engineer thinking about what they can do for you and your service - they will be taking a holistic view across the entire failed infrastructure and the solution will most likely take longer to implement unless its something simple like failed switch or router because whole systems/backups (ha - if they exist) will be being restored rather than just *your* systems and backups.
Readers with corporate phones who aren't allowed to install adblockers disagree.
Adblockers not allowed on corporate phone. Believe me, I tried (physically and trying to get approval).
Autoplay MS^H^H ads top of page.
Please at least detect mobile browsers and replace auto play ads with a static image.
Fkn annoying on my phone on train on way to work. Please stop this crap.
Many years ago, there was an attempt to give electronic engineers a shorter, snappy title akin to those what call themselved "electricians". The best anyone could come up with was "electroneers".
Whoa, your post had 1 stability event in 2. That's awesome!
> United, are your security people listening?
Nah, they are all stuck in a departures lounge somewhere on their way back from a conference because their flight was delayed/cancelled.
So...longer than an 8 hour wait at SFO before your flight to LHR is finally cancelled and you have to fly to Dulles and eventually arrive back home over one day late...and no you can't use our lounge while we dick around trying to work out how to get you home?
I refuse to fly United now .. all subsequent business flights have been with Virgin Atlantic.
This is not an HDS system; it's from HGST - totally different organisations.
These systems use Erasure Coding to scatter elements of the stored objects across multiple disks (or sites, if you have more than one system), and rebuild times are based on the time taken to reconstruct the elements stored on one disk.
There are boxes out in the field (previous generation ones) for which reliability data is available, plus there are the ones in the labs and development centres. Overall, it's possible to calculate reliability figures based on the MTBF/AFR and other parameters for individual components.
These systems don't use RAID. Check out 'Erasure Coding'
Exactly! The storage policies which determine how objects are stored, how many parts they are spread across on the disks and how many parts we can afford to lose (the 'safety') is customer configurable and determines the effective storage size.
/Currently sitting in a training course at HGST for this, so getting a kick etc...
It was the mid/late 1980s and we'd just installed a row of spanking-new IBM PC-AT computers (286 processor, no less) running a CAD application called Daisy on a *nix OS called Daisy-DNIX. In those days RAM was very expensive so not a lot was fitted and the systems swapped to disk constantly.
Everything was going swimmingly until some electronic-engineer-who-should-have-known-better fancied a brew-up and plugged his electric kettle into the end socket on a run of daisy-chained (heh!) extension leads. Of course, the fuse blew in the FIRST plug and all the computers went down.
The resulting mess caused by machines that were shut down incorrectly while busily swapping took a couple of days to sort out.
Those machines swapped so much that we were forever replacing busted disks.
Happy days. Have a read: https://en.wikipedia.org/wiki/Daisy_Systems
Just have to mention my Acorn System 1 from 1979; this was Acorn's first commercial computer. I received it about a year ago from someone who had it 'in a box under my desk somewhere'. The unit needed some TLC, but after a few PCB track repairs, a couple of replacement logic chips and some rework on the LED display ribbon cable it's up and working again - although I have to admit that I don't run it 24/7 and the display is not up to email or surfing the 'net.
You can see a pic of the unit here: http://forum.6502.org/viewtopic.php?f=12&t=3286&start=15
It's sitting on a pile of parts I have ordered so I can make a replica (when I get round to it!)
More info here: https://en.wikipedia.org/wiki/Acorn_System_1
Um..OK...you carry on there. We all went down the pub about 3 hours ago.
Meanwhile: anonymous faux engineer in stock shot burns the crap out of C109 for no apparent reason.
/Claims: "I was told to make sure the cap was on the hot side"
"The 77-page report dug up extra vulnerabilities in the once-popular encryption platform but say none are sufficient to undermine the jettisoned software."
sudo killall -9 Autopilot