Mail Archives: cygwin/2005/03/08/13:20:56
----Original Message----
>From: Chris Winne
>Sent: 08 March 2005 17:39
> I should know that if it ain't broke, don't fix it,
> but...
Um.... so does that mean you would consider it _good_ news if I tell you
that it looks very much like it was broke after all?
> In any case, seeing in installation that installing as
> user did not provide all functionality, I decided to
> reinstall as administrator. Following installation
> and relogging in as myself, my first sign of something
> fishy was an extra cygwin icon.
That's probably OK: when you installed just for yourself, setup offered to
create an icon on your desktop, which is in \Documents And Settings\<your
user name>\Desktop. When you were installing for all users, it created one
in the "all users" desktop in \Documents and Settings\All users\Desktop, but
it doesn't delete or remove any of the settings that you installed "just for
you", and the same goes for the icon, so you get two of them.
> My real sign of
> trouble was my second harddrive (e:) was nolonger
> mounted. I apparently have a double mount:
>
> $ mount
> C:\cygwin\bin on /usr/bin type user (binmode)
> C:\cygwin\bin on /usr/bin type system (binmode)
> C:\cygwin\lib on /usr/lib type user (binmode)
> C:\cygwin\lib on /usr/lib type system (binmode)
> C:\cygwin on / type user (binmode)
> C:\cygwin on / type system (binmode)
> c: on /cygdrive/c type system (binmode,noumount)
> j: on /cygdrive/j type system (binmode,noumount)
> k: on /cygdrive/k type system (binmode,noumount)
> l: on /cygdrive/l type system (binmode,noumount)
> p: on /cygdrive/p type system (binmode,noumount)
> q: on /cygdrive/q type system (binmode,noumount)
>
> $ mount -p
> Prefix Type Flags
> /cygdrive user binmode
> /cygdrive system binmode
This shouldn't be a problem. The system-level mounts should all be found
before the user-level ones and simply override them harmlessly. No, this is
the real problem:
> e: unk N/A N/A
Your HD is toast. Zapped. Zilch. Gone. Dead. Nackered. No boot
sector. This is nothing to do with cygwin mountpoints; this shows that even
'doze doesn't recognize it any more. Remember, a cygwin mount point isn't
like a Linux mount: it isn't responsible for loading a device driver or
getting the underlying OS to recognize the device, it's more like a shortcut
or softlink, just a handy way of referring to a 'doze path within the
POSIX-style filesystem based on the '/' root.
I'm afraid that it's just a coincidence that your HD has failed at the
same time you were reinstalling cygwin.
> Also, out from standard error with cygcheck, I got the
> following:
>
> cygcheck: dump_sysinfo: GetVolumeInformation() failed:
> 5
> cygcheck: dump_sysinfo: GetVolumeInformation() failed:
> 59
Error 5 is permission denied. Error 59 is a network failure presumably
relating to one of those network drives further down the list. It's hard to
know if either of these is related: I notice that the cygcheck output for
one of your network drives failed
>l: net N/A N/A
so perhaps the error 5 was the access to E: failing and the error 59 is the
access to L: failing, or perhaps the E: drive just failed silently (or
wasn't even scanned because the O/S didn't think it was really there), both
those errors relate to network drives, and neither gives us any further info
about what's happened to your HD.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -