Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: Unable to Mount Partitions/Drive accessed by Windows 10

  1. #11
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Quote Originally Posted by arvidjaar View Post
    Boot Leap, run "journalctl --follow" in terminal, connect external HDD, post output of journalctl.
    A clarification please, do I connect ext HDD before or after running the "journalctl --follow" command? I only have to switch on the power to the HDD.

    Thanks

    PrakashC

  2. #12
    Join Date
    Oct 2014
    Location
    Rotterdam
    Posts
    651

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Like @arvidjaar wrote, in that order:

    1. run "journalctl --follow" in terminal
    2. connect external HDD
    3. post output of journalctl

  3. #13
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Quote Originally Posted by arvidjaar View Post
    Boot Leap, run "journalctl --follow" in terminal, connect external HDD, post output of journalctl.
    Code:
    -- Logs begin at Mon 2021-07-26 15:12:10 IST. --
    Jul 26 15:14:23 localhost.localdomain kwin_x11[2002]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 26112, resource id: 35652644, major code: 18 (ChangeProperty), minor code: 0
    Jul 26 15:14:28 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:14:34 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:14:35 localhost.localdomain su[2684]: (to root) prakash on pts/1
    Jul 26 15:14:35 localhost.localdomain su[2684]: pam_unix(su-l:session): session opened for user root by prakash(uid=1000)
    Jul 26 15:14:40 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:14:46 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:14:52 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:14:58 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:04 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:10 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:16 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:22 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:28 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:35 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:41 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:47 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:53 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:15:59 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:16:05 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:16:11 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    Jul 26 15:16:17 localhost.localdomain kernel: IPv6: MLD: clamping QRV from 1 to 2!
    That is what I get.

    PrakashC

  4. #14
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,098

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Is that what is added to your "follow" when you connect/switch on the device? Or that that only what was shown already direct after giving the command?

    The idea of the "follow" functionality is that you see a short list of the last logs and after that you will see every fresh log entry that is made. Thus allows one to see the direct effect of an action in the logs. Thus only the entries that are made as a result of the action (connecting) are important.

    I ask because I see nothing in relation to device connection.
    Henk van Velden

  5. #15
    Join Date
    Sep 2012
    Posts
    6,773

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Quote Originally Posted by PrakashC View Post
    That is what I get.
    Did you run it as root? If yes, your external disk is broken.

  6. #16
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Quote Originally Posted by arvidjaar View Post
    Did you run it as root? If yes, your external disk is broken.
    Any hope of retrieving data? Something like QPhotRec?

    PrakashC

  7. #17
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    In Microsoft community some one has reported being able to retrieve data fro the locked drive using UBCD software and Parted Magic.
    Anyone has experience with UBCD?

    PrakashC

  8. #18
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Lucky Break!

    I have been trawling through posts on Windows 10 hoping to find a way to reach into the external HDD but without any success. However whenever I turn on the PC either with Leap 15.2 or Windows 10 I switch on the affected HDD hoping for a miracle.

    Today while working with Windows 10 the drive suddenly showed signs of life! And I could access the data. After shutdown restarted with Leap and the HDD was still working. No idea what happened.

    Thanks.

    PrakashC

  9. #19
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,098

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    Fine. Of course make a backup of all on it as soon as possible.
    Henk van Velden

  10. #20
    Join Date
    Nov 2009
    Location
    New Delhi, India
    Posts
    253

    Default Re: Unable to Mount Partitions/Drive accessed by Windows 10

    The external drive is now readable. Ran the "journalctl --follow" command and switched on the external HDD. The output is as follows:

    Code:
    localhost:~ # journalctl --follow
    -- Logs begin at Sat 2021-08-14 09:58:57 IST. --
    Aug 14 12:19:13 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service...
    Aug 14 12:19:13 localhost.localdomain dbus-daemon[951]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Aug 14 12:19:13 localhost.localdomain systemd[1]: Started Network Manager Script Dispatcher Service.
    Aug 14 12:19:39 localhost.localdomain kwin_x11[2116]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 303, resource id: 60817411, major code: 15 (QueryTree), minor code: 0
    Aug 14 12:19:39 localhost.localdomain kwin_x11[2116]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 308, resource id: 60817411, major code: 18 (ChangeProperty), minor code: 0
    Aug 14 12:19:39 localhost.localdomain kwin_x11[2116]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 581, resource id: 39846875, major code: 18 (ChangeProperty), minor code: 0
    Aug 14 12:19:39 localhost.localdomain kwin_x11[2116]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 585, resource id: 58720261, major code: 18 (ChangeProperty), minor code: 0
    Aug 14 12:20:14 localhost.localdomain kwin_x11[2116]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3952, resource id: 39846970, major code: 18 (ChangeProperty), minor code: 0
    Aug 14 12:20:24 localhost.localdomain su[4283]: (to root) prakash on pts/1
    Aug 14 12:20:24 localhost.localdomain su[4283]: pam_unix(su-l:session): session opened for user root by prakash(uid=1000)
    Aug 14 12:21:30 localhost.localdomain kernel: usb 2-1.4: new high-speed USB device number 3 using xhci_hcd
    Aug 14 12:21:31 localhost.localdomain kernel: usb 2-1.4: New USB device found, idVendor=0bc2, idProduct=50a1, bcdDevice= 1.00
    Aug 14 12:21:31 localhost.localdomain kernel: usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
    Aug 14 12:21:31 localhost.localdomain kernel: usb 2-1.4: Product: FA GoFlex Desk
    Aug 14 12:21:31 localhost.localdomain kernel: usb 2-1.4: Manufacturer: Seagate
    Aug 14 12:21:31 localhost.localdomain kernel: usb 2-1.4: SerialNumber: NA0L4TLH
    Aug 14 12:21:31 localhost.localdomain mtp-probe[4345]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/usb2/2-1/2-1.4"
    Aug 14 12:21:31 localhost.localdomain mtp-probe[4345]: bus: 2, device: 3 was not an MTP device
    Aug 14 12:21:31 localhost.localdomain kernel: usb-storage 2-1.4:1.0: USB Mass Storage device detected
    Aug 14 12:21:31 localhost.localdomain kernel: scsi host4: usb-storage 2-1.4:1.0
    Aug 14 12:21:31 localhost.localdomain kernel: usbcore: registered new interface driver usb-storage
    Aug 14 12:21:31 localhost.localdomain kernel: usbcore: registered new interface driver uas
    Aug 14 12:21:32 localhost.localdomain kernel: scsi 4:0:0:0: Direct-Access     Seagate  FA GoFlex Desk   0D0B PQ: 0 ANSI: 0
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] 3907029167 512-byte logical blocks: (2.00 TB/1.82 TiB)
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] Write Protect is off
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] Mode Sense: 0f 00 00 00
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] No Caching mode page found
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
    Aug 14 12:21:32 localhost.localdomain kernel:  sdc: sdc1
    Aug 14 12:21:32 localhost.localdomain kernel: sd 4:0:0:0: [sdc] Attached SCSI disk
    Aug 14 12:21:32 localhost.localdomain udisksd[1877]: Error probing device: Error sending ATA command IDENTIFY DEVICE to /dev/sdc: Unexpected sense data returned:
                                                         0000: 70 00 05 00  00 00 00 0a  00 00 00 00  20 00 00 00    p........... ...
                                                         0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                                          (g-io-error-quark, 0)
    Request arvidjaar to kindly take a look and let me know if there are still some problems.
    Thanks
    PrakashC

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

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