Announcement

Collapse
No announcement yet.

external disk weirdness

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Qqmike
    replied
    Still on the run (special occasion distracting me here). Follow what oshuluvr is saying about the dmesg.

    Just one comment about your other comment:

    sudo gdisk /dev/sdb, then ?, then r (= recovery and transformation options (experts only)), then d = use main GPT header (rebuilding backup)
    When you do this (in the interactive gdisk), and are done, don't then forget to type w for write the changes before you close out and exit, right?

    Leave a comment:


  • przxqgl
    replied
    Originally posted by Qqmike View Post
    sudo gdisk /dev/sdb, then ?, then r (= recovery and transformation options (experts only)), then d = use main GPT header (rebuilding backup)
    after following Qqmike's suggestion, now, when i run dmesg again, this time i get:

    Code:
    [ 3619.262061] usb-storage 2-2:1.0: USB Mass Storage device detected
    [ 3619.262616] scsi host9: usb-storage 2-2:1.0
    [ 3621.215350] scsi 9:0:0:0: Direct-Access     WD       My Book 1130     1012 PQ: 0 ANSI: 6
    [ 3621.215881] scsi 9:0:0:1: Enclosure         WD       SES Device       1012 PQ: 0 ANSI: 6
    [ 3621.217165] sd 9:0:0:0: Attached scsi generic sg2 type 0
    [ 3621.217528] ses 9:0:0:1: Attached Enclosure device
    [ 3621.217700] ses 9:0:0:1: Attached scsi generic sg3 type 13
    [ 3634.783385] sd 9:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    [ 3634.783618] sd 9:0:0:0: [sdb] Write Protect is off
    [ 3634.783626] sd 9:0:0:0: [sdb] Mode Sense: 47 00 10 08
    [ 3634.783873] sd 9:0:0:0: [sdb] No Caching mode page found
    [ 3634.783879] sd 9:0:0:0: [sdb] Assuming drive cache: write through
    [ 3634.784514] sd 9:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    [ 3634.812623] Alternate GPT is invalid, using primary GPT.
    [ 3634.812658]  sdb: sdb1 sdb2 sdb3
    [ 3634.813608] sd 9:0:0:0: [sdb] 732558336 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    [ 3634.813906] sd 9:0:0:0: [sdb] Attached SCSI disk
    which looks a lot more like the partitions oshunluvr was asking for... but there's still that ominous sounding " Alternate GPT is invalid" which i don't particularly like

    Leave a comment:


  • przxqgl
    replied
    woo... so, i unplugged the drive and typed dmesg, and i got so much stuff on the screen that i can't capture it all...

    then i plugged the drive in, and typed dmesg again, and this time i got pretty much the same overwhelmingly large amount of stuff, plus this:

    Code:
    [ 3619.241150] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
    [ 3619.258472] usb 2-2: LPM exit latency is zeroed, disabling LPM.
    [ 3619.260968] usb 2-2: New USB device found, idVendor=1058, idProduct=1130
    [ 3619.260976] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 3619.260981] usb 2-2: Product: My Book 1130
    [ 3619.260985] usb 2-2: Manufacturer: Western Digital
    [ 3619.260988] usb 2-2: SerialNumber: 574341575A30313830343834
    [ 3619.262061] usb-storage 2-2:1.0: USB Mass Storage device detected
    [ 3619.262616] scsi host9: usb-storage 2-2:1.0
    [ 3621.215350] scsi 9:0:0:0: Direct-Access     WD       My Book 1130     1012 PQ: 0 ANSI: 6
    [ 3621.215881] scsi 9:0:0:1: Enclosure         WD       SES Device       1012 PQ: 0 ANSI: 6
    [ 3621.217165] sd 9:0:0:0: Attached scsi generic sg2 type 0
    [ 3621.217528] ses 9:0:0:1: Attached Enclosure device
    [ 3621.217700] ses 9:0:0:1: Attached scsi generic sg3 type 13
    um... does that include a list of partitions? it certainly doesn't have the names that i'm used to...

    Leave a comment:


  • Qqmike
    replied
    (Good, oshunluvr, I'm supposed to be gone by now, waiting on a phone call; re Post #14 IF YOU GUYS DECIDE TO FIX THE SUPPOSED BROKEN GPT ... sudo gdisk /dev/sdb, then ?, then r (= recovery and transformation options (experts only)), then d = use main GPT header (rebuilding backup) since his output said this: "Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header.")

    A gdisk Walkthrough

    www.rodsbooks.com/gdisk/walkthrough.html

    Roderick Smith

    GPT fdisk Tutorial

    www.rodsbooks.com/gdisk/

    Roderick Smith

    ...

    Leave a comment:


  • oshunluvr
    replied
    Since it's a USB disk, start at the beginning and verify it's working. With the drive unplugged, open a terminal and type dmesg. You'll see a bunch of stuff on the screen. Then plug the drive in and type dmesg again. If the drive doesn't appear in the dmesg output, including a list of it's partitions, it not being detected properly. If you do see output showing the partitions (/dev/sdc1 etc...) then we can move forward.

    Re. fat (aka fat16) vfat and fat32 - vfat is an extension of fat16, fat32 is an extension of vfat and not normally used with linux. fat32/vfat have a file size limit of 4GB but can be used on larger volumes than that - up to 8TB for fat32.

    As far as the reformat - there's ways to handle that if you have a lot of space on the drive.

    Leave a comment:


  • przxqgl
    replied
    Originally posted by Qqmike View Post
    sudo gdisk -l /dev/sdx will tell you if it sees a GPT partitioned disk and if it is healthy or broken. If it is broken, the interactive form of gdisk can probably fix it: sudo gdisk /dev/sdx (with no options).
    "sudo gdisk -l /dev/sdb" gave me the following:

    Code:
    GPT fdisk (gdisk) version 0.8.8
    
    Caution: invalid backup GPT header, but valid main header; regenerating
    backup header from main header.
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: damaged
    
    ****************************************************************************
    Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
    verification and recovery are STRONGLY recommended.
    ****************************************************************************
    Disk /dev/sdb: 732558336 sectors, 2.7 TiB
    Logical sector size: 4096 bytes
    Disk identifier (GUID): 8E2D5510-7E63-4F58-8836-5F35FFB08726
    Partition table holds up to 128 entries
    First usable sector is 6, last usable sector is 732558330
    Partitions will be aligned on 8-sector boundaries
    Total free space is 65536 sectors (256.0 MiB)
    
    Number  Start (sector)    End (sector)  Size       Code  Name
       1               6           51205   200.0 MiB   EF00  EFI System Partition
       2           51206       488332461   1.8 TiB     AF00  backup
       3       488365230       732525562   931.4 GiB   AF00  home
    once again, i'm not a linux genius, but my impression is that amounts to "broken"...

    "sudo gdisk /dev/sdb" says this:

    Code:
    GPT fdisk (gdisk) version 0.8.8
    
    Caution: invalid backup GPT header, but valid main header; regenerating
    backup header from main header.
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: damaged
    
    ****************************************************************************
    Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
    verification and recovery are STRONGLY recommended.
    ****************************************************************************
    
    Command (? for help):
    and, because of the fact that i'm no linux genius, i don't know what to do next... ? for help told me how to verify the disk (it's okay, unsurprisingly), but it didn't tell me how to recover... help?
    Last edited by przxqgl; Sep 29, 2015, 03:15 PM.

    Leave a comment:


  • Qqmike
    replied
    I don't think I have studied this thread as carefully as I should, but I'm on the run, don't want to interrupt the flow here, just two things strike me (quickly):

    The traditional MBR partitioning scheme only sees up to 2 TB. Thus, the GPT is better for very large disks.

    sudo gdisk -l /dev/sdx will tell you if it sees a GPT partitioned disk and if it is healthy or broken. If it is broken, the interactive form of gdisk can probably fix it: sudo gdisk /dev/sdx (with no options).

    Leave a comment:


  • przxqgl
    replied
    i didn't reformat it, i went straight to partitioning it, so if it was FAT32 when i bought it, then it's no surprise that that's what it is now...

    however, here's an interesting tidbit. i turned off my machine, unplugged the disk, then turned the machine on again and ran the "parted" command, which said:

    Code:
    Model: ATA WDC WD10EZEX-60M (scsi)
    Disk /dev/sda: 1000GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: msdos
    
    Number  Start   End     Size    Type      File system  Flags
     1      1049kB  984GB   984GB   primary   ext4         boot
     2      984GB   1000GB  16.3GB  extended
     5      984GB   1000GB  16.3GB  logical
    (yes, i also unplugged all of the other USB disks, as well)

    now, here's the interesting part. when i plugged the 3TB, 2 partition disk in again, this is what it said:

    Code:
    Error: The backup GPT table is corrupt, but the primary appears OK, so that will
    be used.
    OK/Cancel? ok                                                             
    Model: WD My Book 1130 (scsi)
    Disk /dev/sdb: 3001GB
    Sector size (logical/physical): 4096B/4096B
    Partition Table: gpt
    
    Number  Start   End     Size    File system  Name                  Flags
     1      24.6kB  210MB   210MB                EFI System Partition  boot
     2      210MB   2000GB  2000GB               backup
     3      2000GB  3000GB  1000GB               home
    it's a start, no?

    Leave a comment:


  • vinnywright
    replied
    so what was it formated to when you originally made it for a backup disk ?

    VINNY

    Leave a comment:


  • przxqgl
    replied
    Originally posted by vinnywright View Post
    1 more thing fat32 will not suport a disk that large ,,,if it is 3TB ,,,,fat will only see 4GB I think .
    i will definitely do that, but it's going to have to be after i take the data off and store it somewhere else, because, if i recall correctly, formatting the disk means erasing all of the data contained therein, and that's what i'm trying to avoid... it was called /media/backup for a reason...

    Originally posted by vinnywright View Post
    you should repartition it as NTFS if windows neads to use it ,,,, or ext4 if linux only.
    i understand, and there is no reason to format it FAT32 or NTFS, because i only use linux and mac... but, as i said, the disks (or, rather, the partitions) are going to have to be cleared of all their data before i reformat them, otherwise even worse things are likely to happen than have already happened.

    Leave a comment:


  • vinnywright
    replied
    to be sure /dev/sdc is the disk ,,,,shutdown the box ,,,,unplug it ,,,,reboot and run the parted command again and see if /dev/sdc is gone ,,,,,,plug it back in run the parted command ,,,,is it back ?

    if yes use the partition manager to repartition it as NTFS or ext4

    VINNY

    Leave a comment:


  • vinnywright
    replied
    1 more thing fat32 will not suport a disk that large ,,,if it is 3TB ,,,,fat will only see 4GB I think .

    you should repartition it as NTFS if windows neads to use it ,,,, or ext4 if linux only.

    VINNY

    Leave a comment:


  • przxqgl
    replied
    Originally posted by vinnywright View Post
    well first what did you partition it with ,,,,,,?
    KDE Partition Manager

    Originally posted by vinnywright View Post
    you can mount it diferent way's ,,,,in dolphin by clicking it in the places panel if it is showing
    it is not showing up in dolphin at all.

    Originally posted by vinnywright View Post
    "make a place to mount it"
    Code:
    sudo mkdir /mnt/disk
    "mount it to /mnt/disk"
    Code:
    sudo mount -t fat32 /dev/sdc1 /mnt/disk
    Code:
    mount: unknown filesystem type 'fat32'
    mount: maybe you meant 'vfat'?
    so, do i mean 'vfat'? i'm not even sure what 'vfat' is... very fat?

    Leave a comment:


  • vinnywright
    replied
    Originally posted by przxqgl View Post
    in that case, no, i can't see the disk using "sudo parted -l"...

    and, additionally, i've got a mysterious, unknown disk at /dev/sdc... 8/



    if it didn't change anything when i partitioned it, then, yes, /dev/sdc is, possibly, one of the partitions...

    how do i get it to mount, and how do i get the other partition to show up?
    well first what did you partition it with ,,,,,,?

    you can mount it diferent way's ,,,,in dolphin by clicking it in the places panel if it is showing ,,,,,,,,,,,,,,, or on the CLI with something like

    "make a place to mount it"
    Code:
    sudo mkdir /mnt/disk
    "mount it to /mnt/disk"
    Code:
    sudo mount -t fat32 /dev/sdc1 /mnt/disk
    now navigate to /mnt/disk in dolphin and see whats in their.

    if you have permissions problems use a root dolphin
    Code:
    kdesudo dolphin
    if this is the disk we can start working out the problems with getting it to auto mount and your user access rites

    VINNY

    Leave a comment:


  • przxqgl
    replied
    in that case, no, i can't see the disk using "sudo parted -l"...

    and, additionally, i've got a mysterious, unknown disk at /dev/sdc... 8/

    you say you partitioned it (the 3TB disk) into 2 partitions ,,,sdc is 1 partition formated fat32
    if it didn't change anything when i partitioned it, then, yes, /dev/sdc is, possibly, one of the partitions...

    how do i get it to mount, and how do i get the other partition to show up?
    Last edited by przxqgl; Sep 29, 2015, 01:42 PM.

    Leave a comment:

Users Viewing This Topic

Collapse

There are 0 users viewing this topic.

Working...
X