From owner-freebsd-questions@freebsd.org Fri Dec 1 02:35:35 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E61BDF10B7 for ; Fri, 1 Dec 2017 02:35:35 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1172B8024D for ; Fri, 1 Dec 2017 02:35:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.191.233]) by mrelayeu.kundenserver.de (mreue006 [212.227.15.167]) with ESMTPA (Nemesis) id 0M1MLN-1fDnB73NEX-00tQjW; Fri, 01 Dec 2017 03:30:12 +0100 Date: Fri, 1 Dec 2017 03:29:57 +0100 From: Polytropon To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org Subject: Re: Mount NTFS from "Live" system? Message-Id: <20171201032957.576e569a.freebsd@edvax.de> In-Reply-To: <53922.1512076255@segfault.tristatelogic.com> References: <78bf2bd4-63e0-afce-1b24-ebdadba055b5@qeng-ho.org> <53922.1512076255@segfault.tristatelogic.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:QX0aIOTnVHE4KHphurLMvDC2KKcgXj1M5skldNOdSrOYDKQWgjr hB4itBrLnO8XpYiZpXMuOy9XlkAhJIfdEOUyZ/wESv65Pt1c0Hrff6+R1yPTSWcpKvDE47b 7ypnUMoffsy21BWI6bYlRuzWAYhCcCBHhYJbhVTnKGvjnE560NVQZwyz2q23Q41XvKYINnx 71PZFWvvDjtu4L480aWeg== X-UI-Out-Filterresults: notjunk:1;V01:K0:2Dv27r4lAZQ=:TY8Kft4PB/xQ9VHyaw8Sma GmnfrTlsTXxiQIR7RlTHyRaqfEmA7Vrxw75mHQJR44d06JZ+7wYKgS3cFkCRF4rLdAC6X080O vKNQiKFtvU30KQT03e6A0+JlDz8Vm2W/e2XowkcBPaRZOfZPhZ+W/czNGHFuFsTNCZVayPCgU XmZPm/FB52l/JS6B5lUwSvy9aHKFixRCaN9dNUmwMx9axaku17Z8CUcz7uzoQU6cvTDn4QXGu bahn1dZqDJdU5J7BOUk1TsqSwA3IK0CxmcTq3aery+PDrGceT+mL5ZSjBYEebhOAtDDvi2/h5 t36/LgrhehLdJ/RNl2EC88yHD9gj+yRHba735YF0nRIQr5Tg4v6x4bJJ13/NkmfcXA6qTCdrj eYm7/3hjCmjWqi0o05NSCc/iX/oFcJhV+14dSOQxnpHShj9CgkA4w4Ju4xDCfLNKaqOmEV3gU VfkjXxI34YC04f4y0Pgj4zALe7G4PpnBpQgh+mERTqbrgH5mGaBJ4a/BAuFxLq9zhbp+Lsn8H UCPjfp2i/TNCU+YNkw6VL+AB4AuFQzAIcwi2a86KzW0FjfkFRUzEFE1MhetSjBuzkPguin13m hoWDsGOfKeFcqNMkhBd84lsW9YPowtHvdp8ookr2/SawpTK0P+d5u1rH3vxc5iGlJTBLz+soA BrREFTvcIUnlio9FqhVqx+AZeSD9iTsRJWOJMKZXZQtmOIvudVgxUqrGKNi9hk9hpyWHTM80i mbD59SpUVmKgOwd4iHStIKAIdAV32nZTrwAnG5u0ksk7UkUCdF/5MyGNj8N6xQDQfnTxEeg+5 9ctUbiM X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 02:35:35 -0000 On Thu, 30 Nov 2017 13:10:55 -0800, Ronald F. Guilmette wrote: > What I never knew till today was that any of the "blue" drives would self-idle. > > Does that only happen on the 2.5" "laptop" ones? I have a WD Blue 3.5" 2TB disk which does not seem to exhibit this behaviour. Maybe an older firmware version prior to the "green IT" move? I don't have Blue 2.5" (only SSDs) in laptops so I cannot counter-check. > Anyway, yea, I can see how this could possibly cause problems in the case of > *nix systems. (And it is annoying to me generally when my various tech toys > start thinking that they are smarter than I am, and making decisions for me, > especially those that I would not have made myself.) Get used to it - this will be the default of all "modern" items you will be able to purchase. In worst case, they come with a lower-level "know everything better than you" firmware that cannot be accessed or controlled from the OS. It doesn' matter if it's present in CPUs, mainboards, or hard disks; even cars, TVs, desk phones or heaters can be affected... :-( > I'm gonna try to see if I can disable this "feature" on this specific drive > and then see If I can maybe get it to complete the self test... which it did > not do the last time I tried. You can use smartctl to dump the capabilities and settings list of a drive to verify that setting. > But one would think/hope that even if the drive was set to auto-idle, it would > at least have enough brains/courtesy not to fall asleep in the middle of a > built-in firmware self-test. But maybe not. And maybe this drive is not > actually broke after all. Why not? "Bricked by firmware update" is nothing unusual in our "modern" "smart" time anymore. ;-) > However if your SSDs ever -do- start to spin, then you've got a real > problem on your hands. :-) If you put SSDs into an ATL and handle them like tape cartridges, well, floating, sliding and spinning becomes normal. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...