public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hashim Aziz <hashaziz@hotmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: cat /proc/partitions shows only devices, not partitions
Date: Sun, 01 Mar 2020 21:16:00 -0000	[thread overview]
Message-ID: <DB7PR01MB51934E03BFDFE94142F1966FD5E60@DB7PR01MB5193.eurprd01.prod.exchangelabs.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2090 bytes --]

This was an issue that I had previously in September of last year and sent the issue to this mailing list ("win-mounts no longer displays anything when doing "cat /proc/partitions") but the issue stopped occurring before I could get around to diagnosing it. This issue has now re-occurred and this time it seems permanent. When I run:

$ cat /proc/partitions
major minor  #blocks  name   win-mounts

    8     0         0 sda
    8    16         0 sdb
    8    32         0 sdc
    8    48         0 sdd
    8    64         0 sde
    8    80         0 sdf

...I see nothing at all in the win-mounts column. This makes it impossible for me to see which Windows drive letter maps to which /dev/sdX entry. On closer inspection, this seems to be because I'm not actually seeing any partitions of my drives, even though there are many - for example, I see /dev/sda but no /dev/sda1 or /dev/sda2, and because it's the partitions that are mounted, it's this that seems to result in me seeing nothing in the win-mounts column. I'm running Cygwin on Windows 7 (yes I'm aware it's EOL).

For testing purposes I also ran the following command (for obvious reasons I don't want to have run something like this to find my drive mappings):

$ for disk in /dev/sd*; do echo -n $disk$'\t'; cygpath -m $disk; done
/dev/sda        //./PhysicalDrive0
/dev/sda1       //./D:
/dev/sdb        //./PhysicalDrive1
/dev/sdc        //./PhysicalDrive2
/dev/sdc1       //./Volume{88cc26b4-e0e5-11e9-9cc4-806e6f6e6963}
/dev/sdc2       //./C:
/dev/sdd        //./PhysicalDrive3
/dev/sdd1       //./B:
/dev/sde        //./PhysicalDrive4
/dev/sde1       //./HarddiskVolume5
/dev/sde2       //./E:
/dev/sdf        //./PhysicalDrive5
/dev/sdf1       //./I:

​Thanks in advance for any help with this, it would be very much appreciated as I rely on Cygwin a lot.
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

             reply	other threads:[~2020-03-01 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01 21:16 Hashim Aziz [this message]
2020-03-02 16:56 ` Corinna Vinschen
2020-03-04 19:35 ` Andrey Repin
2020-03-03  0:55 Hashim Aziz
2020-03-03 10:44 ` Corinna Vinschen
2020-03-03  1:01 Hashim Aziz
2020-03-03 17:21 Hashim Aziz
2020-03-03 18:17 ` Corinna Vinschen
2020-03-07 20:36 ` Hashim Aziz
2020-03-09  3:11   ` Andrey Repin
2020-03-09 15:47 Hashim Aziz
2020-03-09 15:59 ` Bill Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB7PR01MB51934E03BFDFE94142F1966FD5E60@DB7PR01MB5193.eurprd01.prod.exchangelabs.com \
    --to=hashaziz@hotmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).