Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 34

Thread: Error mounting /dev/sdb7

  1. #21
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    So if I put my HDD in this machine, and this machine's HDD in my machine, what exactly would that achieve? Is there potential my HDD could get messed up too if it's the machine causing problems?
    Earlier I mentioned window$ tried to auto repair and stopped (because it wanted human intervention) do you think it worthwhile intervening and getting window$ to do a repair? I'm presuming it can see the drive/partitions.

  2. #22
    Join Date
    Nov 2009
    Beans
    3,336

    Re: Error mounting /dev/sdb7

    on the first post there is this error

    Error: Can't have a partition outside the disk!
    You would be as well dropping oldfred a personal message and asking if its the problem - then go from there ........

    There are other posts showing what happens when this message comes up ....... but whether they apply to your own situation I cannot be sure

    window$ to do a repair? I'm presuming it can see the drive/partitions.
    Never presume anything - especially when it can involve losing lots of data - but only your friend can decide how much useful data is on the drive.
    there are ways of getting a lot of it off - or even making a copy/clone of the drive - before something happens that makes it non retrievable.

    So oldfred is probably as good as anyone to look into this - if he is available. https://ubuntuforums.org/member.php?u=852711
    Last edited by 23dornot23d; November 10th, 2018 at 04:27 PM.

  3. #23
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting /dev/sdb7

    If error is from sdb, post this in code tags:
    sudo gdisk -l /dev/sdb

    Do not use older live installer. Only newer versions of fdisk support gpt partitioned drives. You can use parted or gdisk, each gives slightly different and often useful info.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  4. #24
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    Quote Originally Posted by MibunoOokami View Post
    I can't say I've ever noticed that. I will check now.
    Quote Originally Posted by MibunoOokami View Post
    Nope, I can't see the drives being listed.
    Checked this on my own machine and per my earlier comments, still haven't seen the drives show on the splash screen.

    Quote Originally Posted by 23dornot23d View Post
    Never presume anything - especially when it can involve losing lots of data - but only your friend can decide how much useful data is on the drive.
    there are ways of getting a lot of it off - or even making a copy/clone of the drive - before something happens that makes it non retrievable.
    Ok, thanks for the heads up. I'm glad it's not my machine because I would have gone with my presumption and probably made a real mess of things.

    Quote Originally Posted by oldfred View Post
    If error is from sdb, post this in code tags:
    sudo gdisk -l /dev/sdb

    Do not use older live installer. Only newer versions of fdisk support gpt partitioned drives. You can use parted or gdisk, each gives slightly different and often useful info.
    Live installer being LiveCD? That could be a contributing factor, the latest version I have on disc is 14.04 I can't boot with USB because I need a PW for BIOS.

    The output for now
    Code:
    ubuntu@ubuntu:~$ sudo gdisk -l /dev/sdb 
    GPT fdisk (gdisk) version 0.8.8 
     
    Partition table scan: 
      MBR: protective 
      BSD: not present 
      APM: not present 
      GPT: present 
     
    Found valid GPT with protective MBR; using GPT. 
    Disk /dev/sdb: 1953525168 sectors, 931.5 GiB 
    Logical sector size: 512 bytes 
    Disk identifier (GUID): 11B88084-F195-4744-8F41-594A07CD3829 
    Partition table holds up to 128 entries 
    First usable sector is 34, last usable sector is 1953525134 
    Partitions will be aligned on 2048-sector boundaries 
    Total free space is 4181 sectors (2.0 MiB) 
     
    Number  Start (sector)    End (sector)  Size       Code  Name 
       1            2048         1023999   499.0 MiB   2700  Basic data partition 
       2         1024000         1228799   100.0 MiB   EF00  EFI system partition 
       3         1228800         1261567   16.0 MiB    0C01  Microsoft reserved part 
       4         1261568       104191255   49.1 GiB    0700  Basic data partition 
       5       104192000       105191423   488.0 MiB   EF00   
       6       105191424       166948863   29.4 GiB    8300   
       7       166948864      1953523711   851.9 GiB   8300

  5. #25
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    I just went and got a blank DVD and put 18.04 on it. Here are the most up-to-date outputs of the various commands I have tried so far. There is some difference, I hope this will help.

    Code:
    ubuntu@ubuntu:~$ dmesg | tail
    [ 1474.276606] Bluetooth: hci0: last event is not cmd complete (0x0f)
    [ 1490.151568] Bluetooth: hci0: last event is not cmd complete (0x0f)
    [ 1498.307229] wlp32s0: authenticate with a4:91:b1:44:4b:8d
    [ 1498.320155] wlp32s0: send auth to a4:91:b1:44:4b:8d (try 1/3)
    [ 1498.322124] wlp32s0: authenticated
    [ 1498.324086] wlp32s0: associate with a4:91:b1:44:4b:8d (try 1/3)
    [ 1498.328888] wlp32s0: RX AssocResp from a4:91:b1:44:4b:8d (capab=0x1411 status=0 aid=1)
    [ 1498.329087] wlp32s0: associated
    [ 1498.585427] IPv6: ADDRCONF(NETDEV_CHANGE): wlp32s0: link becomes ready
    [ 1506.276620] Bluetooth: hci0: last event is not cmd complete (0x0f)
    Code:
    ubuntu@ubuntu:~$ sudo parted -l
    Model: ATA WDC WD10JPVX-22J (scsi)
    Disk /dev/sda: 1000GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: gpt
    Disk Flags: 
    
    Number  Start   End     Size    File system  Name                          Flags
     1      1049kB  524MB   523MB   ntfs         Basic data partition          hidden, diag
     2      524MB   629MB   105MB   fat32        EFI system partition          boot, esp
     3      629MB   646MB   16.8MB               Microsoft reserved partition  msftres
     4      646MB   53.3GB  52.7GB  ntfs         Basic data partition          msftdata
     5      53.3GB  53.9GB  512MB   fat32                                      boot, esp
     6      53.9GB  85.5GB  31.6GB  ext4
     7      85.5GB  1000GB  915GB   ext4
    
    
    Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
    has been opened read-only.
    Model: HL-DT-ST DVDRAM GUE1N (scsi)                                       
    Disk /dev/sr0: 1953MB
    Sector size (logical/physical): 2048B/2048B
    Partition Table: mac
    Disk Flags: 
    
    Number  Start   End     Size    File system  Name   Flags
     1      2048B   6143B   4096B                Apple
     2      1913MB  1916MB  2392kB               EFI
    Code:
    ubuntu@ubuntu:~$ sudo fdisk -l
    Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop5: 13 MiB, 13619200 bytes, 26600 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 11B88084-F195-4744-8F41-594A07CD3829
    
    Device         Start        End    Sectors   Size Type
    /dev/sda1       2048    1023999    1021952   499M Windows recovery environment
    /dev/sda2    1024000    1228799     204800   100M EFI System
    /dev/sda3    1228800    1261567      32768    16M Microsoft reserved
    /dev/sda4    1261568  104191255  102929688  49.1G Microsoft basic data
    /dev/sda5  104192000  105191423     999424   488M EFI System
    /dev/sda6  105191424  166948863   61757440  29.5G Linux filesystem
    /dev/sda7  166948864 1953523711 1786574848 851.9G Linux filesystem
    That (above) looks completely different now, and I notice the partitions are now sda1-7

    Code:
    ubuntu@ubuntu:~$ ls -l /dev/disk/by-uuid/
    total 0
    lrwxrwxrwx 1 root root  9 Nov 10 18:17 2018-07-25-03-21-56-00 -> ../../sr0
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 64de21bd-d4ab-467e-91ea-e3695662b11f -> ../../sda7
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 7CE85440E853F6BC -> ../../sda1
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 7a21c3df-8067-4661-953a-7d7404c3e2d1 -> ../../sda6
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 ABC1-C43A -> ../../sda5
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 AE55-7A3F -> ../../sda2
    lrwxrwxrwx 1 root root 10 Nov 10 18:44 FA3657BC36577919 -> ../../sda4
    Code:
    ubuntu@ubuntu:~$ sudo gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 1.0.3
    
    Problem opening /dev/sdb for reading! Error is 123.

  6. #26
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting /dev/sdb7

    See this, post #2 by author of gdisk:
    https://ubuntuforums.org/showthread.php?t=1490819

    It is saying drive may have issues. Double check that all cables are tightly connected.
    Then in Disks, upper right corner is Smart Status. It will say good or bad, and can run many tests. Do not know details on tests.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  7. #27
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    Quote Originally Posted by oldfred View Post
    See this, post #2 by author of gdisk:
    https://ubuntuforums.org/showthread.php?t=1490819

    It is saying drive may have issues. Double check that all cables are tightly connected.
    Then in Disks, upper right corner is Smart Status. It will say good or bad, and can run many tests. Do not know details on tests.
    I've got the back off the machine and found a lot of play in the optical drive and the HDD. The HDD screws all got about 3/4 - 1 turn to tighten them, cables seem secure.

    Two questions before I put the cover back on and try the smart status:

    #1 I've tightened the optical drive screw as far as it will go, possibly over done it, yet the drive still moves a good 1-2mm is that normal? It looks like I may be able to fold a bit of pater, or perhaps put some aluminium tape in there there to reduce the play, would you recommend that if the play is not normal?

    #2 Whilst I have the back off, would now be a good time to try and reset the BIOS PW? Or should that be a later task once we've established what's going on?

    Thanks

  8. #28
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Error mounting /dev/sdb7

    If you have case open, you might as well reset BIOS. You may jumper pins or remove motherboard battery for a bit.
    Also then a good idea to see if a newer version of UEFI/BIOS is available from vendor & update it.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  9. #29
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    After 2.5 - 3hrs waiting for the extensive Smart disk check to complete, the results are "last self-test completed successfully" and the "disk is OK"
    I still get the same output error
    Code:
    ubuntu@ubuntu:~$ sudo gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 1.0.3
    
    Problem opening /dev/sdb for reading! Error is 123.
    Last edited by MibunoOokami; November 11th, 2018 at 05:04 AM. Reason: Output

  10. #30
    Join Date
    Feb 2011
    Beans
    463
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Error mounting /dev/sdb7

    Quote Originally Posted by oldfred View Post
    See this, post #2 by author of gdisk:
    https://ubuntuforums.org/showthread.php?t=1490819

    It is saying drive may have issues. Double check that all cables are tightly connected.
    Then in Disks, upper right corner is Smart Status. It will say good or bad, and can run many tests. Do not know details on tests.
    Per post #2 of that thread you linked, here is the output of dmesg | tail -n 20.
    Code:
    ubuntu@ubuntu:~$ dmesg | tail -n 20
    [  505.263688] audit: type=1400 audit(1541917963.824:163): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.gnome-logs.gnome-logs" pid=3861 comm="apparmor_parser"
    [  505.336116] audit: type=1400 audit(1541917963.900:164): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine" pid=3869 comm="apparmor_parser"
    [  505.336120] audit: type=1400 audit(1541917963.900:165): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=3869 comm="apparmor_parser"
    [  505.340975] audit: type=1400 audit(1541917963.904:166): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.core" pid=3871 comm="apparmor_parser"
    [  505.345355] audit: type=1400 audit(1541917963.908:167): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.core.hook.configure" pid=3873 comm="apparmor_parser"
    [  505.618027] audit: type=1400 audit(1541917964.180:168): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.gnome-logs" pid=3880 comm="apparmor_parser"
    [  505.959040] audit: type=1400 audit(1541917964.520:169): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.gnome-logs.gnome-logs" pid=3882 comm="apparmor_parser"
    [  506.500828] audit: type=1400 audit(1541917965.064:170): apparmor="STATUS" operation="profile_load" profile="unconfined" name="snap-update-ns.gnome-system-monitor" pid=3982 comm="apparmor_parser"
    [  506.589407] audit: type=1400 audit(1541917965.152:171): apparmor="STATUS" operation="profile_load" profile="unconfined" name="snap.gnome-system-monitor.gnome-system-monitor" pid=3984 comm="apparmor_parser"
    [  509.950544] kauditd_printk_skb: 46 callbacks suppressed
    [  509.950546] audit: type=1400 audit(1541917968.968:218): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine" pid=4151 comm="apparmor_parser"
    [  509.950550] audit: type=1400 audit(1541917968.968:219): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=4151 comm="apparmor_parser"
    [  509.954388] audit: type=1400 audit(1541917968.972:220): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.core" pid=4153 comm="apparmor_parser"
    [  509.961531] audit: type=1400 audit(1541917968.980:221): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.core.hook.configure" pid=4155 comm="apparmor_parser"
    [  510.203762] audit: type=1400 audit(1541917969.220:222): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.gnome-system-monitor" pid=4162 comm="apparmor_parser"
    [  510.516750] audit: type=1400 audit(1541917969.536:223): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.gnome-system-monitor.gnome-system-monitor" pid=4164 comm="apparmor_parser"
    [  510.812986] audit: type=1400 audit(1541917969.832:224): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.gnome-system-monitor" pid=4171 comm="apparmor_parser"
    [  511.135534] audit: type=1400 audit(1541917970.152:225): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.gnome-system-monitor.gnome-system-monitor" pid=4173 comm="apparmor_parser"
    [  511.208932] audit: type=1400 audit(1541917970.228:226): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine" pid=4180 comm="apparmor_parser"
    [  511.208937] audit: type=1400 audit(1541917970.228:227): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/4917/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=4180 comm="apparmor_parser"
    Any thoughts? Does this output produce any helpful info?

Page 3 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

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