Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #13870 > unrolled thread
| Started by | Tim Watts <tw_usenet@dionic.net> |
|---|---|
| First post | 2015-03-04 13:14 +0000 |
| Last post | 2015-05-03 10:57 +0100 |
| Articles | 20 on this page of 143 — 39 participants |
Back to article view | Back to comp.os.linux.misc
Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 13:14 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Jeroen Belleman <jeroen@nospam.please> - 2015-03-04 15:15 +0100
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-04 14:19 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 14:32 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Robert Heller <heller@deepsoft.com> - 2015-03-04 08:53 -0600
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 15:08 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Kirk_Von_Rockstein <Kirk_Von_Rockstein@nowhere.invalid> - 2015-03-05 20:11 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud ruben safir <ruben@mrbrklyn.com> - 2015-03-12 03:12 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-12 08:24 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Ruben Safir <mrbrklyn@panix.com> - 2015-03-12 19:07 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Dan Espen <despen@verizon.net> - 2015-03-04 09:57 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 15:10 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Dan Espen <despen@verizon.net> - 2015-03-04 11:57 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 17:14 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud John Rumm <see.my.signature@nowhere.null> - 2015-03-23 10:47 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Real Doctor <ian.groups@btinternet.com> - 2015-03-23 12:08 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud HarpingOn <postmaster@127.0.0.1> - 2015-03-04 15:11 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 15:22 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-04 15:36 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-04 17:07 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 17:15 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-04 18:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 18:55 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-04 19:13 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 19:48 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-04 23:47 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-05 07:55 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Rich <rich@example.invalid> - 2015-03-05 09:53 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-05 12:09 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-05 14:19 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-05 19:27 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud chris <ithinkiam@gmail.com> - 2015-03-05 22:04 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Rich <rich@example.invalid> - 2015-03-05 10:04 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-05 12:28 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-05 13:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-05 11:50 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "J. Clarke" <j.clarke.873638@gmail.com> - 2015-03-20 14:24 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud Joe Beanfish <joebeanfish@nospam.duh> - 2015-03-22 15:05 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Dan Espen <despen@verizon.net> - 2015-03-04 14:51 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 20:16 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-10 14:44 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-03-11 17:45 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Robert Heller <heller@deepsoft.com> - 2015-03-11 14:15 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-11 15:42 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-11 23:26 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-03-12 18:17 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Adrian <toomany2cvs@gmail.com> - 2015-03-12 07:47 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-12 12:23 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-13 07:19 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-12 08:22 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Folderol <general@musically.me.uk> - 2015-03-12 09:14 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Huge <Huge@nowhere.much.invalid> - 2015-03-12 09:39 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Adrian <toomany2cvs@gmail.com> - 2015-03-12 09:42 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-12 16:59 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Adrian <toomany2cvs@gmail.com> - 2015-03-12 17:20 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Robert Heller <heller@deepsoft.com> - 2015-03-12 12:49 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-12 19:03 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-12 10:12 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-03-12 18:17 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-13 07:13 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-12 20:50 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud John Hasler <jhasler@newsguy.com> - 2015-03-12 16:08 -0500
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-12 21:24 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Capitol <spam@wher.eva.co.uk> - 2015-03-12 22:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud ImperiusDamian <damianblack.wolf@gmail.com> - 2015-03-18 09:13 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud Robert Riches <spamtrap42@jacob21819.net> - 2015-03-19 02:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "J. Clarke" <j.clarke.873638@gmail.com> - 2015-03-20 14:30 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-12 20:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Nigel Wade <nmw@ion.le.ac.uk> - 2015-03-12 09:47 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Huge <Huge@nowhere.much.invalid> - 2015-03-12 09:38 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-12 09:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Daniel James <daniel@me.invalid> - 2015-03-12 10:50 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-12 15:25 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-13 08:19 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-13 12:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-13 19:39 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-14 02:12 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-03-13 15:13 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Folderol <general@musically.me.uk> - 2015-03-13 16:53 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-13 19:30 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Daniel James <daniel@me.invalid> - 2015-03-14 13:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 14:48 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-14 16:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 17:58 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-14 22:41 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-14 18:20 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-14 19:34 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-14 22:43 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "J. Clarke" <j.clarke.873638@gmail.com> - 2015-03-20 14:53 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud Daniel James <daniel@me.invalid> - 2015-03-15 13:34 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Folderol <general@musically.me.uk> - 2015-03-15 15:41 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-15 18:40 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-16 15:35 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-16 15:45 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Dennis@home" <dennis@nowhere.invalid> - 2015-03-16 16:21 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Andy Burns <usenet.feb2014@adslpipe.co.uk> - 2015-03-16 19:05 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-16 21:40 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-17 15:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Nigel Wade <nmw@ion.le.ac.uk> - 2015-03-12 11:17 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-12 12:03 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Stan Bischof <stan@worldbadminton.com> - 2015-03-12 16:28 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-12 20:35 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Richard Kettlewell <rjk@greenend.org.uk> - 2015-03-11 22:52 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-03-12 18:17 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud ruben safir <ruben@mrbrklyn.com> - 2015-03-12 02:51 -0400
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-12 08:21 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Ruben Safir <mrbrklyn@panix.com> - 2015-03-12 19:09 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud HarpingOn <postmaster@127.0.0.1> - 2015-03-04 15:10 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 15:19 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-03-04 15:54 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 16:10 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Daniel James <daniel@me.invalid> - 2015-03-05 11:20 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-05 12:29 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-04 18:56 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Martin Gregorie <martin@address-in-sig.invalid> - 2015-03-05 00:33 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2015-03-05 22:46 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-06 08:07 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2015-03-14 11:56 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 14:47 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-15 05:40 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 18:51 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-15 06:12 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 19:23 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-15 06:27 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-14 22:00 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "john james" <jj9801@nospam.com> - 2015-03-15 11:22 +1100
Re: Opensource slowing down? "GoogleDrive" private cloud Huge <Huge@nowhere.much.invalid> - 2015-03-15 09:10 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Tony Houghton <h@realh.co.uk> - 2015-03-15 00:08 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Java Jive <java@evij.com.invalid> - 2015-03-15 15:34 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2015-03-15 18:33 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud The Natural Philosopher <tnp@invalid.invalid> - 2015-03-16 07:46 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "Anonymous Remailer (austria)" <mixmaster@remailer.privacy.at> - 2015-03-16 00:16 +0100
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-16 10:55 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-16 18:10 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-17 13:55 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-17 21:15 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-17 16:17 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-18 08:15 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud "John F" <j@j.ii> - 2015-03-18 09:02 -0700
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-03-18 16:14 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud ruben <nowhere@nowhere.nor> - 2015-05-03 06:49 +0000
Re: Opensource slowing down? "GoogleDrive" private cloud Marc Haber <mh+usenetspam1118@zugschl.us> - 2015-05-03 09:12 +0200
Re: Opensource slowing down? "GoogleDrive" private cloud Tim Watts <tw_usenet@dionic.net> - 2015-05-03 10:57 +0100
Page 5 of 8 — ← Prev page 1 2 3 4 [5] 6 7 8 Next page →
| From | Daniel James <daniel@me.invalid> |
|---|---|
| Date | 2015-03-14 13:00 +0000 |
| Message-ID | <VA.00000a19.37372070@me.invalid> |
| In reply to | #14056 |
In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, Dennis@home wrote: > When someone takes one to bits can they look to see how they ensure > mains doesn't get across the disks when the psu melts? The PSU can burn because you buy another. The NAS itself is (mostly) trashed by the fire, but you can take the drives out an put them in a new NAS and read the data. The idea is to protect the things (data) that can't be replaced, but simply to replace the things that can. -- Cheers, Daniel.
[toc] | [prev] | [next] | [standalone]
| From | Tim Watts <tw_usenet@dionic.net> |
|---|---|
| Date | 2015-03-14 14:48 +0000 |
| Message-ID | <kaudtb-anl.ln1@squidward.dionic.net> |
| In reply to | #14064 |
On 14/03/15 13:00, Daniel James wrote: > In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, > Dennis@home wrote: >> When someone takes one to bits can they look to see how they ensure >> mains doesn't get across the disks when the psu melts? > > The PSU can burn because you buy another. I believe the point was: what happens when the PSU melts and dumps mains to the output and blows your NAS to tiny weeny bits? I would hope the NAS had some serious crowbar protection on its incoming DC in.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2015-03-14 16:43 +0000 |
| Message-ID | <me1oga$lbg$1@news.albasani.net> |
| In reply to | #14066 |
On 14/03/15 14:48, Tim Watts wrote: > On 14/03/15 13:00, Daniel James wrote: >> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >> Dennis@home wrote: >>> When someone takes one to bits can they look to see how they ensure >>> mains doesn't get across the disks when the psu melts? >> >> The PSU can burn because you buy another. > > I believe the point was: what happens when the PSU melts and dumps mains > to the output and blows your NAS to tiny weeny bits? > And almost impossible scenario. What happens when an asteroid takes out your house at the same time as one takes out the public cloud server? There is physical serious separation between the mains and the LV on any modern PSU. Line several mm of plastic bobbin at least. And the PU needs to be working properly in order to deliver ANY volts to the secondary of the transformer. The chances of overvoltage are approximately zero. It's sad that the fallacy of the precautionary principle, that any possibility no matter how remote, must be considered and have huge sums spent on it in order to satisfy the idiocy of people who don't understand technology and science has transferred itself from climate change to backup policy for computer systems. > I would hope the NAS had some serious crowbar protection on its incoming > DC in. > -- Everything you read in newspapers is absolutely true, except for the rare story of which you happen to have first-hand knowledge. – Erwin Knoll
[toc] | [prev] | [next] | [standalone]
| From | Tim Watts <tw_usenet@dionic.net> |
|---|---|
| Date | 2015-03-14 17:58 +0000 |
| Message-ID | <oe9etb-cgs.ln1@squidward.dionic.net> |
| In reply to | #14067 |
On 14/03/15 16:43, The Natural Philosopher wrote: > On 14/03/15 14:48, Tim Watts wrote: >> On 14/03/15 13:00, Daniel James wrote: >>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >>> Dennis@home wrote: >>>> When someone takes one to bits can they look to see how they ensure >>>> mains doesn't get across the disks when the psu melts? >>> >>> The PSU can burn because you buy another. >> >> I believe the point was: what happens when the PSU melts and dumps mains >> to the output and blows your NAS to tiny weeny bits? >> > > And almost impossible scenario. The fire turns the potting compound to carbon, bridging the tracks on the PCB and resulting in a flashover. Of course it's not impossible.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2015-03-14 22:41 +0000 |
| Message-ID | <me2df2$qb0$1@news.albasani.net> |
| In reply to | #14068 |
On 14/03/15 17:58, Tim Watts wrote: > On 14/03/15 16:43, The Natural Philosopher wrote: >> On 14/03/15 14:48, Tim Watts wrote: >>> On 14/03/15 13:00, Daniel James wrote: >>>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >>>> Dennis@home wrote: >>>>> When someone takes one to bits can they look to see how they ensure >>>>> mains doesn't get across the disks when the psu melts? >>>> >>>> The PSU can burn because you buy another. >>> >>> I believe the point was: what happens when the PSU melts and dumps mains >>> to the output and blows your NAS to tiny weeny bits? >>> >> >> And almost impossible scenario. > > The fire turns the potting compound to carbon, bridging the tracks on > the PCB and resulting in a flashover. What potting compound? You cant flashover 2cm either. > > Of course it's not impossible. > -- Everything you read in newspapers is absolutely true, except for the rare story of which you happen to have first-hand knowledge. – Erwin Knoll
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-14 18:20 +0000 |
| Message-ID | <me1u60$nn$1@dont-email.me> |
| In reply to | #14067 |
On Sat, 14 Mar 2015 16:43:54 +0000, The Natural Philosopher wrote: > On 14/03/15 14:48, Tim Watts wrote: >> On 14/03/15 13:00, Daniel James wrote: >>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >>> Dennis@home wrote: >>>> When someone takes one to bits can they look to see how they ensure >>>> mains doesn't get across the disks when the psu melts? >>> >>> The PSU can burn because you buy another. >> >> I believe the point was: what happens when the PSU melts and dumps >> mains to the output and blows your NAS to tiny weeny bits? >> >> > And almost impossible scenario. > Maybe, maybe not. Trevor Potts evidently thinks its a reasonable enough scenario to have passed the question on to ioSafe. > There is physical serious separation between the mains and the LV on any > modern PSU. Line several mm of plastic bobbin at least. > Everything is likely to be on the same PCB, so while what you say may be right at room temp, but is it still true when the plastic power brick is starting to burn, some of the plastics will have melted and solder may have started to drip. > And the PU needs to be working properly in order to deliver ANY volts to > the secondary of the transformer. The chances of overvoltage are > approximately zero. > I don't think there are any transformers in the type of external PSU that was supplied with the ioSafe 214 that got destructively tested. As I said earlier, in the video: http://www.theregister.co.uk/2013/12/02/setting_the_iosafe_214_on_fire/ The external PSU looks very like the sort of plastic power brick that comes with a laptop. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | "Dennis@home" <dennis@nowhere.invalid> |
|---|---|
| Date | 2015-03-14 19:34 +0000 |
| Message-ID | <55048d27$0$13316$b1db1813$d2f06f9f@news.astraweb.com> |
| In reply to | #14067 |
On 14/03/2015 16:43, The Natural Philosopher wrote: > On 14/03/15 14:48, Tim Watts wrote: >> On 14/03/15 13:00, Daniel James wrote: >>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >>> Dennis@home wrote: >>>> When someone takes one to bits can they look to see how they ensure >>>> mains doesn't get across the disks when the psu melts? >>> >>> The PSU can burn because you buy another. >> >> I believe the point was: what happens when the PSU melts and dumps mains >> to the output and blows your NAS to tiny weeny bits? >> > > And almost impossible scenario. > > > What happens when an asteroid takes out your house at the same time as > one takes out the public cloud server? > > > There is physical serious separation between the mains and the LV on any > modern PSU. Line several mm of plastic bobbin at least. > > And the PU needs to be working properly in order to deliver ANY volts to > the secondary of the transformer. The chances of overvoltage are > approximately zero. > > It's sad that the fallacy of the precautionary principle, that any > possibility no matter how remote, must be considered and have huge sums > spent on it in order to satisfy the idiocy of people who don't > understand technology and science has transferred itself from climate > change to backup policy for computer systems. You try melting the plastic bobbin while holding the low voltage DC output and make sure you film it for the darwin awards.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2015-03-14 22:43 +0000 |
| Message-ID | <me2dhq$qb0$2@news.albasani.net> |
| In reply to | #14075 |
On 14/03/15 19:34, Dennis@home wrote: > On 14/03/2015 16:43, The Natural Philosopher wrote: >> On 14/03/15 14:48, Tim Watts wrote: >>> On 14/03/15 13:00, Daniel James wrote: >>>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, >>>> Dennis@home wrote: >>>>> When someone takes one to bits can they look to see how they ensure >>>>> mains doesn't get across the disks when the psu melts? >>>> >>>> The PSU can burn because you buy another. >>> >>> I believe the point was: what happens when the PSU melts and dumps mains >>> to the output and blows your NAS to tiny weeny bits? >>> >> >> And almost impossible scenario. >> >> >> What happens when an asteroid takes out your house at the same time as >> one takes out the public cloud server? >> >> >> There is physical serious separation between the mains and the LV on any >> modern PSU. Line several mm of plastic bobbin at least. >> >> And the PU needs to be working properly in order to deliver ANY volts to >> the secondary of the transformer. The chances of overvoltage are >> approximately zero. >> >> It's sad that the fallacy of the precautionary principle, that any >> possibility no matter how remote, must be considered and have huge sums >> spent on it in order to satisfy the idiocy of people who don't >> understand technology and science has transferred itself from climate >> change to backup policy for computer systems. > > > You try melting the plastic bobbin while holding the low voltage DC > output and make sure you film it for the darwin awards. > Oh dear. No problem. You would think that no one actually paid any attention to the years of experience that goes into design safety specifications.. -- Everything you read in newspapers is absolutely true, except for the rare story of which you happen to have first-hand knowledge. – Erwin Knoll
[toc] | [prev] | [next] | [standalone]
| From | "J. Clarke" <j.clarke.873638@gmail.com> |
|---|---|
| Date | 2015-03-20 14:53 -0400 |
| Message-ID | <MPG.2f7636c962890adc98983d@news.eternal-september.org> |
| In reply to | #14075 |
In article <55048d27$0$13316$b1db1813$d2f06f9f@news.astraweb.com>, dennis@nowhere.invalid says... > > On 14/03/2015 16:43, The Natural Philosopher wrote: > > On 14/03/15 14:48, Tim Watts wrote: > >> On 14/03/15 13:00, Daniel James wrote: > >>> In article <55029d91$0$18431$b1db1813$df808093@news.astraweb.com>, > >>> Dennis@home wrote: > >>>> When someone takes one to bits can they look to see how they ensure > >>>> mains doesn't get across the disks when the psu melts? > >>> > >>> The PSU can burn because you buy another. > >> > >> I believe the point was: what happens when the PSU melts and dumps mains > >> to the output and blows your NAS to tiny weeny bits? > >> > > > > And almost impossible scenario. > > > > > > What happens when an asteroid takes out your house at the same time as > > one takes out the public cloud server? > > > > > > There is physical serious separation between the mains and the LV on any > > modern PSU. Line several mm of plastic bobbin at least. > > > > And the PU needs to be working properly in order to deliver ANY volts to > > the secondary of the transformer. The chances of overvoltage are > > approximately zero. > > > > It's sad that the fallacy of the precautionary principle, that any > > possibility no matter how remote, must be considered and have huge sums > > spent on it in order to satisfy the idiocy of people who don't > > understand technology and science has transferred itself from climate > > change to backup policy for computer systems. > > > You try melting the plastic bobbin while holding the low voltage DC > output and make sure you film it for the darwin awards. Really depends on what they use. If its DAP or some kind of thermoplastic it will carbonize nicely--if it's Teflon the stuff will dissociate without ever forming a carbon track.
[toc] | [prev] | [next] | [standalone]
| From | Daniel James <daniel@me.invalid> |
|---|---|
| Date | 2015-03-15 13:34 +0000 |
| Message-ID | <VA.00000a1b.3c7c5d31@me.invalid> |
| In reply to | #14066 |
In article <kaudtb-anl.ln1@squidward.dionic.net>, Tim Watts wrote: > I believe the point was: what happens when the PSU melts and > dumps mains to the output and blows your NAS to tiny weeny bits? That's certainly the right question to be asking. I thought someone had wanted the NAS and it's PSU to be usable after the fire, but rereading today I can't find it. > I would hope the NAS had some serious crowbar protection on its > incoming DC in. Indeed so ... and on the ethernet and USB connectors, though the power input is more likely to cause trouble. -- Cheers, Daniel.
[toc] | [prev] | [next] | [standalone]
| From | Folderol <general@musically.me.uk> |
|---|---|
| Date | 2015-03-15 15:41 +0000 |
| Message-ID | <20150315154104.14624fa5@debian> |
| In reply to | #14084 |
On Sun, 15 Mar 2015 13:34:16 -0000 Daniel James <daniel@me.invalid> wrote: > In article <kaudtb-anl.ln1@squidward.dionic.net>, Tim Watts wrote: > > I believe the point was: what happens when the PSU melts and > > dumps mains to the output and blows your NAS to tiny weeny bits? > > That's certainly the right question to be asking. > > I thought someone had wanted the NAS and it's PSU to be usable after > the fire, but rereading today I can't find it. > > > I would hope the NAS had some serious crowbar protection on its > > incoming DC in. > > Indeed so ... and on the ethernet and USB connectors, though the power > input is more likely to cause trouble. Ethernet is pretty bomb-proof by design. USB is very much a weak point. There nothing bar a simple polyfuse protecting the +5V line, and the I/O ones are totally vulnerable. Indeed, recently I read about some b**tard designing a device - masquerading as memory stick - that keeps pulsing these with a very high voltage, resulting in severe MB damage :( -- W J G
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-15 18:40 +0000 |
| Message-ID | <me4jm5$hn4$3@dont-email.me> |
| In reply to | #14086 |
On Sun, 15 Mar 2015 15:41:04 +0000, Folderol wrote: > On Sun, 15 Mar 2015 13:34:16 -0000 Daniel James <daniel@me.invalid> > wrote: > >> In article <kaudtb-anl.ln1@squidward.dionic.net>, Tim Watts wrote: >> > I believe the point was: what happens when the PSU melts and dumps >> > mains to the output and blows your NAS to tiny weeny bits? >> >> That's certainly the right question to be asking. >> >> I thought someone had wanted the NAS and it's PSU to be usable after >> the fire, but rereading today I can't find it. >> >> > I would hope the NAS had some serious crowbar protection on its >> > incoming DC in. >> >> Indeed so ... and on the ethernet and USB connectors, though the power >> input is more likely to cause trouble. > > Ethernet is pretty bomb-proof by design. > > USB is very much a weak point. There nothing bar a simple polyfuse > protecting the +5V line, and the I/O ones are totally vulnerable. > Indeed, recently I read about some b**tard designing a device - > masquerading as memory stick - that keeps pulsing these with a very high > voltage, resulting in severe MB damage :( Yes - and think of the effect of a good, hot fire on the rats-nest of cables under the desk behind the NAS box. Who's to say that you wouldn't get 240v on the CAT5 or a USB cable? But, I wouldn't expect the motherboard to survive the file: it looks to be outside the fireproofing wrapped round the disk, so with such a design you can do all you need by putting a high voltage shunt across the SATA leads as they enter the fireproof disk area. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-16 15:35 +0000 |
| Message-ID | <me6t7f$tdc$1@dont-email.me> |
| In reply to | #14088 |
On Sun, 15 Mar 2015 18:40:05 +0000, Martin Gregorie wrote: > On Sun, 15 Mar 2015 15:41:04 +0000, Folderol wrote: > >> On Sun, 15 Mar 2015 13:34:16 -0000 Daniel James <daniel@me.invalid> >> wrote: >> >>> In article <kaudtb-anl.ln1@squidward.dionic.net>, Tim Watts wrote: >>> > I believe the point was: what happens when the PSU melts and dumps >>> > mains to the output and blows your NAS to tiny weeny bits? >>> >>> That's certainly the right question to be asking. >>> >>> I thought someone had wanted the NAS and it's PSU to be usable after >>> the fire, but rereading today I can't find it. >>> >>> > I would hope the NAS had some serious crowbar protection on its >>> > incoming DC in. >>> >>> Indeed so ... and on the ethernet and USB connectors, though the power >>> input is more likely to cause trouble. >> >> Ethernet is pretty bomb-proof by design. >> >> USB is very much a weak point. There nothing bar a simple polyfuse >> protecting the +5V line, and the I/O ones are totally vulnerable. >> Indeed, recently I read about some b**tard designing a device - >> masquerading as memory stick - that keeps pulsing these with a very >> high voltage, resulting in severe MB damage :( > > Yes - and think of the effect of a good, hot fire on the rats-nest of > cables under the desk behind the NAS box. Who's to say that you wouldn't > get 240v on the CAT5 or a USB cable? > > But, I wouldn't expect the motherboard to survive the file: it looks to > be outside the fireproofing wrapped round the disk, so with such a > design you can do all you need by putting a high voltage shunt across > the SATA leads as they enter the fireproof disk area. OK, just heard back form Trevor Potts and the ioSafe guys. I asked: "When the PSU shorted out due to the fire, could it have fried the disks by letting AC get into the NAS box or does it have designed-in features that would prevent this happening? As it looks, to me anyway, like a standard laptop power brick, this seems like a reasonable question. I'll be very interested to hear what you have to say about it. " And the reply from ioSafe is: "In such an event, the worst case scenario is that any data in transit would be lost. The data on the drives would not be lost. " ...so it looks as though they've thought about this problem. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | Theo Markettos <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2015-03-16 15:45 +0000 |
| Message-ID | <iAD*K6Bqv@news.chiark.greenend.org.uk> |
| In reply to | #14094 |
In uk.comp.os.linux Martin Gregorie <martin@address-in-sig.invalid> wrote: > And the reply from ioSafe is: > > "In such an event, the worst case scenario is that any data in transit > would be lost. The data on the drives would not be lost. > " > > ...so it looks as though they've thought about this problem. Or they didn't understand the question... since they don't explain what measures they've taken to prevent this happening. Theo
[toc] | [prev] | [next] | [standalone]
| From | "Dennis@home" <dennis@nowhere.invalid> |
|---|---|
| Date | 2015-03-16 16:21 +0000 |
| Message-ID | <550702ea$0$47006$b1db1813$1367588f@news.astraweb.com> |
| In reply to | #14094 |
On 16/03/2015 15:35, Martin Gregorie wrote: > OK, just heard back form Trevor Potts and the ioSafe guys. > > I asked: > "When the PSU shorted out due to the fire, could it have fried the disks > by letting AC get into the NAS box or does it have designed-in features > that would prevent this happening? > > As it looks, to me anyway, like a standard laptop power brick, this seems > like a reasonable question. I'll be very interested to hear what you > have to say about it. > " > > And the reply from ioSafe is: > > "In such an event, the worst case scenario is that any data in transit > would be lost. The data on the drives would not be lost. > " > > ...so it looks as though they've thought about this problem. > > I think you need to ask "What happens when the power brick melts and mains gets applied to the 12V DC input of the NAS? What stops it frying the disks?"
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet.feb2014@adslpipe.co.uk> |
|---|---|
| Date | 2015-03-16 19:05 +0000 |
| Message-ID | <1tKdnTuOP7P2tJrInZ2dnUVZ8kGdnZ2d@brightview.co.uk> |
| In reply to | #14094 |
Martin Gregorie wrote: > "When the PSU shorted out due to the fire, could it have fried the disks > by letting AC get into the NAS box > > And the reply from ioSafe is: > > "In such an event, the worst case scenario is that any data in transit > would be lost. The data on the drives would not be lost." > > ...so it looks as though they've thought about this problem. Or, they want you to assume they've thought about it</cynicmode>
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-16 21:40 +0000 |
| Message-ID | <me7iki$ued$1@dont-email.me> |
| In reply to | #14101 |
On Mon, 16 Mar 2015 19:05:17 +0000, Andy Burns wrote: > Martin Gregorie wrote: > >> "When the PSU shorted out due to the fire, could it have fried the >> disks >> by letting AC get into the NAS box >> >> And the reply from ioSafe is: >> >> "In such an event, the worst case scenario is that any data in transit >> would be lost. The data on the drives would not be lost." >> >> ...so it looks as though they've thought about this problem. > > Or, they want you to assume they've thought about it</cynicmode> Request for clarification sent. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-17 15:00 +0000 |
| Message-ID | <me9fic$2db$1@dont-email.me> |
| In reply to | #14103 |
On Mon, 16 Mar 2015 21:40:34 +0000, Martin Gregorie wrote: > On Mon, 16 Mar 2015 19:05:17 +0000, Andy Burns wrote: > >> Martin Gregorie wrote: >> >>> "When the PSU shorted out due to the fire, could it have fried the >>> disks >>> by letting AC get into the NAS box >>> >>> And the reply from ioSafe is: >>> >>> "In such an event, the worst case scenario is that any data in transit >>> would be lost. The data on the drives would not be lost." >>> >>> ...so it looks as though they've thought about this problem. >> >> Or, they want you to assume they've thought about it</cynicmode> > > Request for clarification sent. I wrote: "The scenario I'm interested in is where there is the usual rats nest of cables behind the 214 and the fire gets into this, melting or burning insulation so a live mains conductor contacts a wire in any of the CAT5, USB or DC power cable so that mains voltage gets into the 214's PCB. Is there anything in the 214's circuits that would prevent that frying the disk drive electronics? " and the reply was: "As it happens, burning the cables is no more likely to result in data loss than simply improperly pulling the plug. We actually perform our fire testing with the units plugged in and powered on. " So I guess you'll draw your own conclusions. I'm out of this thread. Toodle-pip. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
| From | Nigel Wade <nmw@ion.le.ac.uk> |
|---|---|
| Date | 2015-03-12 11:17 +0000 |
| Message-ID | <cmdatmFtuk2U1@mid.individual.net> |
| In reply to | #14029 |
On 12/03/15 09:43, The Natural Philosopher wrote: > Precisely. Fireproof is nuts. Two locations is all you need > It isn't nuts at all. Having no backup is nuts. Having all backups co-located is nuts. Having a fireproof/waterproof local backup is a perfectly sensible idea. 30min protection may well be sufficient for most house fires, and it's a lot more convenient than offsite storage. It keeps other things safer (not safe), which cannot (or should not) be duplicated elsewhere.
[toc] | [prev] | [next] | [standalone]
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Date | 2015-03-12 12:03 +0000 |
| Message-ID | <mdrv9s$e0n$2@dont-email.me> |
| In reply to | #14026 |
On Thu, 12 Mar 2015 09:38:15 +0000, Huge wrote: > On 2015-03-11, John F <j@j.ii> wrote: >> >> "Robert Heller" <heller@deepsoft.com> wrote in message >> news:r8GdnVmSCY3wCZ3InZ2dnUU7-IudnZ2d@giganews.com... >>> At 11 Mar 2015 17:45:37 GMT Charlie Gibbs <cgibbs@kltpzyxm.invalid> >>> wrote: > > [45 lines snipped] > >>>> A friend recently lost a lot of valuable photos due to Cloud failure. >>>> Even if there's no malice involved, shit happens. > > My advice is never to store anything "in the cloud" unless you can > afford to have it stolen or lost. > >> Exactly - and you can purchase a 1TB drive and a fireproof safe to put >> it in for less than the cost of a years rental on a good cloud server - >> even if the cloud server is free, it costs you in terms of dealing with >> the advertizing and spyware etc delivered with all the public services >> nowadays > > You don't even need the safe if you have somewhere "off site" to store > the disk - I keep mine in my locker at work. Get two backup disks and backup to them alternately. This way you always have the previous backup in its offline storage no matter what happens, even in the worst case: a massive power spike during a backup that fries both the PC and the disk you were backing up to when it happened. The really careful and/or paranoid will use a cycle of at least three backup disks. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
[toc] | [prev] | [next] | [standalone]
Page 5 of 8 — ← Prev page 1 2 3 4 [5] 6 7 8 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web