Page 5 of 5 FirstFirst ... 345
Results 41 to 49 of 49

Thread: Kernel bug ? unknown partition table on some usb flash drives

  1. #41
    Join Date
    Sep 2012
    Posts
    4,972

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    Quote Originally Posted by robertot5 View Post
    Thanks. The problem is, partition has flag 0x81 and Linux accepts only 0x00 or ox80. Notice that fdisk also displays ?? instead of "Active" flag. Technically this looks like a bug - "Active partition" flag is defined as high bit only, the rest is strictly speaking undefined, so Linux probably should accept it. Do you know which program/operating system created this partition?

    Fixing it is trivial - just use fdisk to mark partition as active - but it may cause side effects if anything relies on this flag value (not in Linux).

  2. #42

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    Quote Originally Posted by arvidjaar View Post
    Thanks. The problem is, partition has flag 0x81 and Linux accepts only 0x00 or ox80. Notice that fdisk also displays ?? instead of "Active" flag. Technically this looks like a bug - "Active partition" flag is defined as high bit only, the rest is strictly speaking undefined, so Linux probably should accept it. Do you know which program/operating system created this partition?

    Fixing it is trivial - just use fdisk to mark partition as active - but it may cause side effects if anything relies on this flag value (not in Linux).
    It was made using basic Windows XP SP3.

    I will try and make it Active using fdisk and then check it both in Linux and Windows.
    OpenSUSE Leap 42.2 x64 KDE

  3. #43

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    Setting it active using fdisk /dev/sdb made it working again, both Linux and Windows, even my TV can see the contents now.

    This is the result of dmesg after making it active

    Code:
    [17050.737892] usb 2-1: new high-speed USB device number 4 using ehci-pci
    [17050.857930] usb 2-1: New USB device found, idVendor=13fe, idProduct=4100
    [17050.857935] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [17050.857937] usb 2-1: Product: USB DISK 2.0
    [17050.857939] usb 2-1: Manufacturer:         
    [17050.857940] usb 2-1: SerialNumber: 070D27888255C220
    [17050.996500] usb-storage 2-1:1.0: USB Mass Storage device detected
    [17050.996595] scsi8 : usb-storage 2-1:1.0
    [17050.996675] usbcore: registered new interface driver usb-storage
    [17052.087503] scsi 8:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 4
    [17052.088093] sd 8:0:0:0: Attached scsi generic sg2 type 0
    [17053.051903] sd 8:0:0:0: [sdb] 7579008 512-byte logical blocks: (3.88 GB/3.61 GiB)
    [17053.052843] sd 8:0:0:0: [sdb] Write Protect is off
    [17053.052849] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
    [17053.053551] sd 8:0:0:0: [sdb] No Caching mode page found
    [17053.053555] sd 8:0:0:0: [sdb] Assuming drive cache: write through
    [17053.078773]  sdb: unknown partition table
    [17053.082893] sd 8:0:0:0: [sdb] Attached SCSI removable disk
    [17163.849925]  sdb: sdb1
    OpenSUSE Leap 42.2 x64 KDE

  4. #44
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    On 2014-07-26 18:56, robertot5 wrote:
    >
    > Setting it active using fdisk /dev/sdb made it working again, both Linux
    > and Windows, even my TV can see the contents now.
    >


    Curious!

    I did wonder about that question mark in fdisk output, but I thought it
    could not be as simple as that. I dismissed suggesting you to use fdisk
    to change the mark to active or inactive (both should work, I think),
    because I believed the problem to be worse.

    I thought the partition active mark would affect one partition entry,
    not the whole table not being read.

    Curious!


    > This is the result of dmesg after making it active
    >


    There is still something weird going on yet:

    >
    > Code:
    > --------------------
    > [17053.078773] sdb: unknown partition table
    > [17053.082893] sd 8:0:0:0: [sdb] Attached SCSI removable disk
    > [17163.849925] sdb: sdb1
    >
    > --------------------


    It still says "unknown partition table". :-?

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  5. #45
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    On 2014-07-26 14:06, robertot5 wrote:

    > It was made using basic Windows XP SP3.


    Wasn't the device formatted by the manufacturer, or did you format it
    yourself again?

    Also Windows typically formats the partition, but does not change the
    partition data: that's done by another program (fdisk in Windows, for
    instance).


    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  6. #46

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    Quote Originally Posted by robin_listas View Post
    On 2014-07-26 14:06, robertot5 wrote:

    > It was made using basic Windows XP SP3.


    Wasn't the device formatted by the manufacturer, or did you format it
    yourself again?

    Also Windows typically formats the partition, but does not change the
    partition data: that's done by another program (fdisk in Windows, for
    instance).


    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))
    No, it was formatted using Windows right click > format > quick format. Never used any utilities in Windows like fdisk, etc.

    Here is another dmesg output of plugging in the flash drive after a reboot.

    Code:
    [20528.707433] usb 2-1: new high-speed USB device number 5 using ehci-pci
    [20528.827523] usb 2-1: New USB device found, idVendor=13fe, idProduct=4100
    [20528.827527] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [20528.827529] usb 2-1: Product: USB DISK 2.0
    [20528.827531] usb 2-1: Manufacturer:         
    [20528.827532] usb 2-1: SerialNumber: 070D27888255C220
    [20528.827807] usb-storage 2-1:1.0: USB Mass Storage device detected
    [20528.827896] scsi9 : usb-storage 2-1:1.0
    [20529.919146] scsi 9:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 4
    [20529.920933] sd 9:0:0:0: Attached scsi generic sg2 type 0
    [20531.053832] sd 9:0:0:0: [sdb] 7579008 512-byte logical blocks: (3.88 GB/3.61 GiB)
    [20531.054452] sd 9:0:0:0: [sdb] Write Protect is off
    [20531.054456] sd 9:0:0:0: [sdb] Mode Sense: 23 00 00 00
    [20531.055107] sd 9:0:0:0: [sdb] No Caching mode page found
    [20531.055113] sd 9:0:0:0: [sdb] Assuming drive cache: write through
    [20531.080604]  sdb: sdb1
    [20531.084969] sd 9:0:0:0: [sdb] Attached SCSI removable disk
    OpenSUSE Leap 42.2 x64 KDE

  7. #47
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    On 2014-07-26 21:46, robertot5 wrote:

    > No, it was formatted using Windows right click > format > quick format.
    > Never used any utilities in Windows like fdisk, etc.


    Which means that you were using the partition table created by the stick
    manufacturer (or perhaps supplier). Format, and even less quick format
    in Windows, do not touch that at all.


    > Here is another dmesg output of plugging in the flash drive after a
    > reboot.


    There it is recognizing the table just fine. So that was it, the
    bootable mark... (!)

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  8. #48
    Join Date
    Sep 2012
    Posts
    4,972

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    Quote Originally Posted by robin_listas View Post
    I thought the partition active mark would affect one partition entry,
    not the whole table not being read.
    Partition table had just one partition entry.

  9. #49
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Kernel bug ? unknown partition table on some usb flash drives

    On 2014-07-27 19:46, arvidjaar wrote:
    >
    > robin_listas;2655963 Wrote:
    >>
    >> I thought the partition active mark would affect one partition entry,
    >> not the whole table not being read.
    >>

    >
    > Partition table had just one partition entry.


    Yes, but to me the partition table is not the entries, even if it is
    just one entry.

    To me, "bad table" means, for instance, that the bytes where the start
    sector is written to is misaligned by one byte, for example, so that the
    fields can not be read. If a field contains "81" which is an invalid
    value, that's a bad entry in one field of the table, not a bad table.

    That's how I understand things, but obviously others think different, so
    perhaps I'm wrong ;-)

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

Page 5 of 5 FirstFirst ... 345

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •