FWIW, on K740, I just had a USB3 HD change drive letters while idle,
mounted, rw.
I had run over 12TB testing it during about 3 weeks with no problem before
today.
Drive is on a rocketfish USB3 pcie card.
On Mint 16, I had a USB flash drive rendered inoperative on shutdown.
(it has no delay from umount to power off; possible write in progress?)
Mint 16 also disconnected USB3 drives, and much more often
(every 12 hrs on the dot on an FX8, every 1-2 hours, idle or busy, on an
A10)
The possible connection to this case is: 10+ years ago,
I had a UPS shut off (power was fine) during a disk write to an internal
Samsung HD, Windows XP.
The drive lost its boot sector (I still need to recover the data).
K740 shuts down without the delay of previous Knoppix.
If the internal HD had partitions mounted, maybe it was still writing?
A long shot, for sure.
Is there a cheat code to force a delay on shutdown before power off?
I think some drives are lying about syncing, given the large difference I
see
between drives when running expand_compressed_fs, which does a data sync
for every block.
(It was so slow on a Seagate HD I had to patch it to data sync every 3%)
IIRC, if a drive has many small writes pending, it may take a minute or
more just to empty
its RAM cache (some flash drives now have large RAM caches now).
Hope this helps
Charles
On Mon, 01 Sep 2014 10:36:26 +0200
Klaus Knopper <debian-knoppix@knopper.net> wrote:
Hello Jim,
Can you please send me a snapshot of the first sectors of both, the
Disks absolute start and partition start (if it's still partitioned)?
About 4MB of data for each may be sufficient for finding out what
happened, or if the NTFS signature is missing.
If your disk shows as /dev/sdb in /proc/partitions, the command would be:
dd if=/dev/sdb of=sdb.img bs=1M count=4
and
dd if=/dev/sdb1 of=sdb1.img bs=1M count=4
Send me the data (sdb.img,sdb1.img) via email (a zip or tar.gz archive
may save some bandwidth).
There may be an issus with some faulty hd firmware concerning boot of
_any_ other Os than the vendor-installed one unrelated to flash-knoppix
which I rememeber from reading an article, which would be a warranty case
for your disk because it's likely to happen again even when booting a
different windows version.
Though I don't think the problem is knoppix- or Linux-related yet, I'm of
course interested in finding cause a a possible fix for such disks.
And: Last week, we found one flash drive that, when plugged in with the
OS running, causes a reset of the USB port and all attached devices were
renumbered. When this happens _during_ a flash-knoppix session, it could
explain how a wrong disk gets repartitioned. I'm afraid that such a
problem with faulty hardware can neither be detected in advance, nor
getting fixed by software alone.
Regards
-Klaus
On 1. September 2014 05:21:41 MESZ, Jim Pritchett
<jpritchett1@charter.net> wrote:
> I don't know what stepped on my bootsector. Beginning with Windoze
> Vista, I
> used utorrent to get the revised v7.4.0 iso from the link at
> http://torrent.unix-ag.uni-kl.de I burned the English version of the
> iso
> to DVD. At this point, the drive was still working since the iso came
> from
> that drive. I then booted to the v7.4.0 DVD. I used the
> flash-knoppix menu
> item to put it on the USB stick. I then booted from the USB stick. I
> did
> some simple checks to make sure knoppix was working ok. I vaguely
> think I
> noticed that the 2 TB drive didn't show up at this point, but I'm not
> certain of that. I used IceWeasel to visit a couple of sites I use
> regulary
> just to make sure it worked. When I rebooted Vista, the drive wasn't
> there.
> This was obvious immediately since I have most of my Windoze data
> directories moved to that drive.
>
> I don't think there was any hibernation involved. The USB stick
> booted and
> appeared to work fine with the very limited testing I did. Since
> v7.4.0 was
> the change when the problem manifested, I used v7.0.5 and Windoze to
> do all
> the work trying to identify and fix the problem. I haven't gotten
> around to
> trying v7.4 again. When I do, it will be on a non-essential computer.
>
> Everything still seems to be back to normal.
>
> Some sort of Windoze malware is a possibility, but Norton found none.
> I suppose that some sort of Linux malware is another possibility.
> That
> seems unlikely though. There was a very small window for it to get
> in.
> Klaus suggested that I might have made an input error. I can't say it
> is
> impossible, but I don't think that is it.
> I think it is a good sign that we haven't seen any more incidents like
> this.
>
> Thank you for trying to help.
>
>
> Jim
>
>
> P.S. I suppose that I should say that it isn't my objective to blame
> anyone
> in this. I really appreciate all the work Klaus has put in. I would
> like
> to prevent this happening again to anyone.
>
>
>
>
>
>
> ----- Original Message -----
> From: "Ilari Halminen" <ilari2000-palsta@yahoo.co.uk>
> To: <debian-knoppix@lists.debian.org>
> Sent: Sunday, August 31, 2014 2:13 AM
> Subject: Re: my invalidated NTFS partition
>
>
> > Well, now there is a question what messed partions?
> >
> > As the first question do use something like hibernation, when you
> close
> > your
> > computer? Or do you shutdown correctly?
> >
> > I do not really know, but It comes in mind that it was a Windows
> virus
> > that
> > caused all that. At least some of those use bootsector for loading
> to
> > memory,
> > and using Knoppix could makes those crazy.
> >
> > I would also know, could you boot to Knoppix from that USB stick? If
> that
> > works perfect, then you cannot give wrong target place.
> >
> > Ilari H
> >
> > -----
> >
> > After almost three weeks of trying various tools, etc., I've finally
>
> > managed to
> > repair the damaged boot sector. Thank you very much to to Klaus and
>
> > Costakis
> > for trying to help. None of the linux tools I tried worked.
> Manually
> > trying
> > to fix the partition table didn't work either. Eventually, I found
> a
> > Windows
> > tool that fixed it in place. It appears that I have everthing back
> to
> > normal
> > with all my files and data intact.
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
> > Archive: https://lists.debian.org/1503525.EuUONvAWez@xubuntu
> >
> >
--
To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Archive:
[🔎] ae205b2c-88bb-45df-ac30-43e5c53316f6@email.android.com">https://lists.debian.org/[🔎] ae205b2c-88bb-45df-ac30-43e5c53316f6@email.android.com
--
Charles Evans <cvevans@users.sourceforge.net>