Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #205409 > unrolled thread

Can't scan new disk

Back to article view | Back to linux.debian.user

Contents

  Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 00:30 +0100
    Re: Can't scan new disk deb <deb@rangingthoughts.org> - 2019-02-16 01:10 +0100
      Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 02:50 +0100
    Re: Can't scan new disk songbird <songbird@anthive.com> - 2019-02-16 01:30 +0100
      Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 02:50 +0100
    Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-16 04:20 +0100
      Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 21:40 +0100
        Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-16 23:20 +0100
          Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-18 04:20 +0100
            Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-19 00:40 +0100
          Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-19 19:00 +0100
            Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-20 03:50 +0100
              Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-20 04:30 +0100
                Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-20 06:30 +0100
                  Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-20 14:20 +0100
    Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-16 09:50 +0100
      Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 21:30 +0100
        Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-18 06:10 +0100
          Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 07:20 +0100
            Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 10:30 +0100
              Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 10:30 +0100
                Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 11:30 +0100
            Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-20 10:30 +0100
              Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 10:50 +0100
                Re: Can't scan new disk "Thomas Schmitt" <scdbackup@gmx.net> - 2019-02-20 11:30 +0100
              Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 13:20 +0100
              Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-24 15:50 +0100
                Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-24 21:30 +0100
                  Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 23:10 +0100
                    Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-25 01:10 +0100
                    Re: Can't scan new disk Linux-Fan <Ma_Sys.ma@web.de> - 2019-02-25 12:40 +0100
                  Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-25 15:20 +0100
                    Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-25 15:50 +0100
                      Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-25 16:00 +0100
                        Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-25 16:30 +0100
                        Re: Can't scan new disk <tomas@tuxteam.de> - 2019-02-26 09:30 +0100
                Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 23:10 +0100
                Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-25 20:20 +0100
            Re: Can't scan new disk Jude DaShiell <jdashiel@panix.com> - 2019-02-20 18:40 +0100

Page 1 of 2  [1] 2  Next page →

#205409 — Can't scan new disk

I just bought a new backup disk, and I want to check it. It's mounted in 
a USB dock.

Running the following gives an error:

root@martha:~# umount /dev/sdb1
root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
/dev/sdb1 is in use.
e2fsck: Cannot continue, aborting.

What's causing this and how do I fix it?  It's not MATE; I tried 
rebooting to rescue mode, but that didn't help.

Mark

[toc] | [next] | [standalone]

#205411

On 2/15/2019 6:24 PM, Mark Allums wrote:
> umount /dev/sdb1
> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1 



Just curious, is it a Western Digital disk?

[toc] | [prev] | [next] | [standalone]

#205413

On 2/15/19 6:08 PM, deb wrote:
> 
> On 2/15/2019 6:24 PM, Mark Allums wrote:
>> umount /dev/sdb1
>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1 
> 
> 
> 
> Just curious, is it a Western Digital disk?
> 
> 
> 

No, a Seagate IronWolf Pro 12 TB

[toc] | [prev] | [next] | [standalone]

#205412

Mark Allums wrote:

> I just bought a new backup disk, and I want to check it. It's mounted in 
> a USB dock.
>
> Running the following gives an error:
>
> root@martha:~# umount /dev/sdb1
> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
> /dev/sdb1 is in use.
> e2fsck: Cannot continue, aborting.
>
> What's causing this and how do I fix it?  It's not MATE; I tried 
> rebooting to rescue mode, but that didn't help.

  sure you got the right disk?

  does it show up in the journal/log when you
unplug it and plug it back in?

  something may be grabbing it automatically perhaps
so check your fstab entry and make sure it isn't
being mounted automatically if you don't want it to
be done like that.  (is it appearing in /mnt ? ).

  check the label, uuid, partition table before doing
anything too serious to it (to make sure you really
do have the right device).

  i never have backup disks being mounted automatically
because i don't always even have them running.


  songbird

[toc] | [prev] | [next] | [standalone]

#205414

On 2/15/19 6:21 PM, songbird wrote:
> Mark Allums wrote:
> 
>> I just bought a new backup disk, and I want to check it. It's mounted in
>> a USB dock.
>>
>> Running the following gives an error:
>>
>> root@martha:~# umount /dev/sdb1
>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>> /dev/sdb1 is in use.
>> e2fsck: Cannot continue, aborting.
>>
>> What's causing this and how do I fix it?  It's not MATE; I tried
>> rebooting to rescue mode, but that didn't help.
> 
>    sure you got the right disk?

100% sure.


> 
>    does it show up in the journal/log when you
> unplug it and plug it back in?
> 
>    something may be grabbing it automatically perhaps
> so check your fstab entry and make sure it isn't
> being mounted automatically if you don't want it to
> be done like that.  (is it appearing in /mnt ? ).
> 
>    check the label, uuid, partition table before doing
> anything too serious to it (to make sure you really
> do have the right device).
> 
>    i never have backup disks being mounted automatically
> because i don't always even have them running.
> 
> 
>    songbird
> 

It isn't mounted.

[toc] | [prev] | [next] | [standalone]

#205416

On 2/15/19 3:24 PM, Mark Allums wrote:
> I just bought a new backup disk, and I want to check it. It's mounted in 
> a USB dock.
> 
> Running the following gives an error:
> 
> root@martha:~# umount /dev/sdb1
> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
> /dev/sdb1 is in use.
> e2fsck: Cannot continue, aborting.
> 
> What's causing this and how do I fix it?  It's not MATE; I tried 
> rebooting to rescue mode, but that didn't help.


On 2/15/19 5:37 PM, Mark Allums wrote:
 > ... Seagate IronWolf Pro 12 TB


What is the make and model of the USB dock, and is it rated for 12 TB?


Does e2fsck work when the drive is connected to an internal SATA port?


I use HDD trays and mobile docks for my backup drives:

https://www.startech.com/HDD/Mobile-Racks/Black-Serial-ATA-Drive-Drawer-with-Shock-Absorbers-Professional-Series~DRW115SATBK


David

[toc] | [prev] | [next] | [standalone]

#205445

On 2/15/19 9:12 PM, David Christensen wrote:
> On 2/15/19 3:24 PM, Mark Allums wrote:
>> I just bought a new backup disk, and I want to check it. It's mounted 
>> in a USB dock.
>>
>> Running the following gives an error:
>>
>> root@martha:~# umount /dev/sdb1
>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>> /dev/sdb1 is in use.
>> e2fsck: Cannot continue, aborting.
>>
>> What's causing this and how do I fix it?  It's not MATE; I tried 
>> rebooting to rescue mode, but that didn't help.
> 
> 
> On 2/15/19 5:37 PM, Mark Allums wrote:
>  > ... Seagate IronWolf Pro 12 TB
> 
> 
> What is the make and model of the USB dock, and is it rated for 12 TB?

It is an Orico, I don't know the model, and I was not aware there was a 
"rating" for disk sizes.




> 
> 
> Does e2fsck work when the drive is connected to an internal SATA port?

Hasn't been tried, as I was not aware there was a difference between USB 
SATA and internal SATA.  Also, it would be highly inconvenient.  I'd 
like to try other possible solutions first.

Thanks,

Mark


> 
> 
> I use HDD trays and mobile docks for my backup drives:
> 
> https://www.startech.com/HDD/Mobile-Racks/Black-Serial-ATA-Drive-Drawer-with-Shock-Absorbers-Professional-Series~DRW115SATBK 


I will consider this.


> 
> 
> David
> 

Thanks a lot,
Mark

[toc] | [prev] | [next] | [standalone]

#205448

On 2/16/19 12:30 PM, Mark Allums wrote:
> On 2/15/19 9:12 PM, David Christensen wrote:
>> On 2/15/19 3:24 PM, Mark Allums wrote:
>>> I just bought a new backup disk, and I want to check it. It's mounted 
>>> in a USB dock.
>>>
>>> Running the following gives an error:
>>>
>>> root@martha:~# umount /dev/sdb1
>>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>>> /dev/sdb1 is in use.
>>> e2fsck: Cannot continue, aborting.
>>>
>>> What's causing this and how do I fix it?  It's not MATE; I tried 
>>> rebooting to rescue mode, but that didn't help.
>>
>>
>> On 2/15/19 5:37 PM, Mark Allums wrote:
>>  > ... Seagate IronWolf Pro 12 TB
>>
>>
>> What is the make and model of the USB dock, and is it rated for 12 TB?
> 
> It is an Orico, I don't know the model, and I was not aware there was a 
> "rating" for disk sizes.

Everything has limitations.  Figure out the model number, part number, 
whatever, and research its specifications -- there's no point trying to 
use a 12 TB drive in a dock that is rated for something elss.


>> Does e2fsck work when the drive is connected to an internal SATA port?
> 
> Hasn't been tried, as I was not aware there was a difference between USB 
> SATA and internal SATA. 

The more layers of hardware, software, and/or firmware between the CPU 
and the SATA port on the drive, the more opportunities for Murphy's Law. 
  When a drive is mounted internally, the connection is something like 
motherboard CPU -> motherboard PCIe -> motherboard SATA chip -> drive. 
But for an external USB dock, the connect becomes motherboard CPU -> 
motherboard PCIe -> motherboard USB chip -> dock USB chip -> dock CPU -> 
dock SATA chip -> drive.  While the motherboard stuff can be FOSS based 
upon manufacturer supplied reference source code (e.g. Intel), USB drive 
docks are typically proprietary and closed-source.  This makes USB docks 
next to impossible to trouble-shoot or bug-fix for end-users or FOSS 
distributors.


> Also, it would be highly inconvenient.  I'd 
> like to try other possible solutions first.


The idea is to devise a process of elimination to see if the problem is 
the drive, the USB dock, Debian, etc..

1.  Try another drive using that dock and Debian.

2.  Try another connection using that drive and Debian.

3.  Try another OS using that drive and dock.


David

[toc] | [prev] | [next] | [standalone]

#205488

Seagate IronWolf Pro 12 TB
Buster, Orico USB 3.0 Dock

>>>> Running the following gives an error:
>>>>
>>>> root@martha:~# umount /dev/sdb1
>>>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>>>> /dev/sdb1 is in use.
>>>> e2fsck: Cannot continue, aborting.

>>> Does e2fsck work when the drive is connected to an internal SATA port?
>>
>> Hasn't been tried, as I was not aware there was a difference between 
>> USB SATA and internal SATA. 

> 
> The idea is to devise a process of elimination to see if the problem is 
> the drive, the USB dock, Debian, etc..
> 
> 1.  Try another drive using that dock and Debian.

8 GB seagate drive, same error.

> 
> 2.  Try another connection using that drive and Debian.

Tried different dock, rated for 12 TB.  Same result.

Used gparted to delete the original partition, create a new one.  The 
following ensued:


GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2
Create Primary Partition #1 (ext4, 10.91 TiB) on /dev/sdb  00:00:00    ( 
ERROR )
      	
create empty partition  00:00:00    ( SUCCESS )
      	
path: /dev/sdb1 (partition)
start: 2048
end: 23437768703
size: 23437766656 (10.91 TiB)
clear old file system signatures in /dev/sdb1  00:00:00    ( SUCCESS )
      	
write 512.00 KiB of zeros at byte offset 0  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 67108864  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 274877906944  00:00:00    ( SUCCESS )
write 512.00 KiB of zeros at byte offset 12000136003584  00:00:00    ( 
SUCCESS )
write 4.00 KiB of zeros at byte offset 12000136462336  00:00:00    ( 
SUCCESS )
write 8.00 KiB of zeros at byte offset 12000136519680  00:00:00    ( 
SUCCESS )
flush operating system cache of /dev/sdb  00:00:00    ( SUCCESS )
set partition type on /dev/sdb1  00:00:00    ( SUCCESS )
      	
new partition type: ext4
create new ext4 file system  00:00:00    ( ERROR )
      	
mkfs.ext4 -F -O ^64bit -L '' '/dev/sdb1'  00:00:00    ( ERROR )
      	
mke2fs 1.44.5 (15-Dec-2018)
/dev/sdb1 is apparently in use by the system; will not make a filesystem 
here!

========================================

> 
> 3.  Try another OS using that drive and dock.


Win 10 with 2nd dock worked fine.  Not hard drive.  Not dock(s).  Seems 
to be Debian.  Systemd?

Mark

[toc] | [prev] | [next] | [standalone]

#205498

On 2/17/19 7:17 PM, Mark Allums wrote:
> Seagate IronWolf Pro 12 TB
> Buster > Orico USB 3.0 Dock

>> 1.  Try another drive using that dock and Debian.
> 
> 8 GB seagate drive, same error.

>> 2.  Try another connection using that drive and Debian.
> 
> Tried different dock, rated for 12 TB.  Same result.
> 
> Used gparted to delete the original partition, create a new one.  The 
> following ensued:

>> 3.  Try another OS using that drive and dock.
> 
> 
> Win 10 with 2nd dock worked fine. 

> Not hard drive.  Not dock(s).  Seems to be Debian.  Systemd?

It would seem that the 1st dock and Debian are both problems.  File bug 
reports with Orice and with Debian.


David

[toc] | [prev] | [next] | [standalone]

#205526

On Sat, 16 Feb 2019 14:12:43 -0800
David Christensen <dpchrist@holgerdanske.com> wrote:

...

> dock SATA chip -> drive.  While the motherboard stuff can be FOSS based 
> upon manufacturer supplied reference source code (e.g. Intel), USB drive 
> docks are typically proprietary and closed-source.  This makes USB docks 
> next to impossible to trouble-shoot or bug-fix for end-users or FOSS 
> distributors.

I'm not sure I understood what you're saying here: do you mean that the
drivers are closed source, or that the silicon design is closed source?
I've used a number of USB-SATA adapters, in docks as well as cables,
and they were all supported by standard in-kernel drivers (although
some of the hardware may have been at least a bit flaky).

Celejar

[toc] | [prev] | [next] | [standalone]

#205531

On 2/19/19 9:59 AM, Celejar wrote:
> On Sat, 16 Feb 2019 14:12:43 -0800
> David Christensen <dpchrist@holgerdanske.com> wrote:
> 
> ...
> 
>> dock SATA chip -> drive.  While the motherboard stuff can be FOSS based
>> upon manufacturer supplied reference source code (e.g. Intel), USB drive
>> docks are typically proprietary and closed-source.  This makes USB docks
>> next to impossible to trouble-shoot or bug-fix for end-users or FOSS
>> distributors.
> 
> I'm not sure I understood what you're saying here: do you mean that the
> drivers are closed source, or that the silicon design is closed source?
> I've used a number of USB-SATA adapters, in docks as well as cables,
> and they were all supported by standard in-kernel drivers (although
> some of the hardware may have been at least a bit flaky).

The ideal is for both the host and the device at either end of a USB 
cable to be "standards compliant":

https://www.usb.org/


This implies a complete and correct USB hardware/ firmware/ software 
protocol stack on both of them.


I try to buy computers, motherboards, add-on cards, etc., with Intel 
chips because Intel releases open-source reference device driver source 
code for some portion of their products.  Linux, Debian, FreeBSD, and 
other FOSS projects use and include this code (in source and/or binary 
form).  This gives me the best chance of a positive OOTB experience with 
those FOSS operating systems/ distributions:

https://software.intel.com/en-us/open-source


AFAIK there are no commercial off the shelf (COTS) USB-SATA docks with 
FOSS hardware (device), firmware (device), or software (device or host). 
  (If somebody knows of any examples, please post the URL's.)


But, it might be possible to build your own using a FOSS operating 
system/ distribution and a single-board computer with a USB device port 
and a SATA host port:

https://en.wikipedia.org/wiki/Comparison_of_single-board_computers#I/O_interfaces_and_ports


David

[toc] | [prev] | [next] | [standalone]

#205532

On Tue, 19 Feb 2019 18:48:23 -0800
David Christensen <dpchrist@holgerdanske.com> wrote:

> On 2/19/19 9:59 AM, Celejar wrote:
> > On Sat, 16 Feb 2019 14:12:43 -0800
> > David Christensen <dpchrist@holgerdanske.com> wrote:
> > 
> > ...
> > 
> >> dock SATA chip -> drive.  While the motherboard stuff can be FOSS based
> >> upon manufacturer supplied reference source code (e.g. Intel), USB drive
> >> docks are typically proprietary and closed-source.  This makes USB docks
> >> next to impossible to trouble-shoot or bug-fix for end-users or FOSS
> >> distributors.
> > 
> > I'm not sure I understood what you're saying here: do you mean that the
> > drivers are closed source, or that the silicon design is closed source?
> > I've used a number of USB-SATA adapters, in docks as well as cables,
> > and they were all supported by standard in-kernel drivers (although
> > some of the hardware may have been at least a bit flaky).

...

> AFAIK there are no commercial off the shelf (COTS) USB-SATA docks with 
> FOSS hardware (device), firmware (device), or software (device or host). 
>   (If somebody knows of any examples, please post the URL's.)

I'm still not sure what you're saying - there certainly are COTS
devices fully supported by FOSS software. E.g., I have a Syba
SY-ENC50091:

https://www.sybausa.com/index.php?route=product/product&product_id=885

It works fine under Debian without needing any non-free stuff, as far
as I recall.

If you're objecting to the hardware not being FOSS, my understanding
is that most useful hardware isn't. Is the SATA hardware itself FOSS?

Celejar

[toc] | [prev] | [next] | [standalone]

#205535

On 2/19/19 7:21 PM, Celejar wrote:
> On Tue, 19 Feb 2019 18:48:23 -0800
> David Christensen <dpchrist@holgerdanske.com> wrote:
>> AFAIK there are no commercial off the shelf (COTS) USB-SATA docks with
>> FOSS hardware (device), firmware (device), or software (device or host).
>>    (If somebody knows of any examples, please post the URL's.)
> 
> I'm still not sure what you're saying - there certainly are COTS
> devices fully supported by FOSS software. E.g., I have a Syba
> SY-ENC50091:
> 
> https://www.sybausa.com/index.php?route=product/product&product_id=885
> 
> It works fine under Debian without needing any non-free stuff, as far
> as I recall.

The Syba USB-SATA dock works with Debian because the HDD manufacturer, 
Syba, the USB cable manufacturer, the computer manufacturer, and Debian 
have implemented everything needed for an end-to-end connection from the 
HDD firmware kernel to the Debian Linux kernel.  Standards facilitated 
that result.


> If you're objecting to the hardware not being FOSS, my understanding
> is that most useful hardware isn't. Is the SATA hardware itself FOSS?

I agree that, historically, hardware has often been closed-source.  But, 
similar to software, there are open-source hardware projects:

https://en.wikipedia.org/wiki/Open-source_hardware


David

[toc] | [prev] | [next] | [standalone]

#205550

On Tue, 19 Feb 2019 21:27:39 -0800
David Christensen <dpchrist@holgerdanske.com> wrote:

> On 2/19/19 7:21 PM, Celejar wrote:
> > On Tue, 19 Feb 2019 18:48:23 -0800
> > David Christensen <dpchrist@holgerdanske.com> wrote:
> >> AFAIK there are no commercial off the shelf (COTS) USB-SATA docks with
> >> FOSS hardware (device), firmware (device), or software (device or host).
> >>    (If somebody knows of any examples, please post the URL's.)
> > 
> > I'm still not sure what you're saying - there certainly are COTS
> > devices fully supported by FOSS software. E.g., I have a Syba
> > SY-ENC50091:
> > 
> > https://www.sybausa.com/index.php?route=product/product&product_id=885
> > 
> > It works fine under Debian without needing any non-free stuff, as far
> > as I recall.
> 
> The Syba USB-SATA dock works with Debian because the HDD manufacturer, 
> Syba, the USB cable manufacturer, the computer manufacturer, and Debian 
> have implemented everything needed for an end-to-end connection from the 
> HDD firmware kernel to the Debian Linux kernel.  Standards facilitated 
> that result.

Exactly. So what do you mean when you say that "there are no commercial
off the shelf (COTS) USB-SATA docks with FOSS hardware (device),
firmware (device), or software (device or host)"?

> > If you're objecting to the hardware not being FOSS, my understanding
> > is that most useful hardware isn't. Is the SATA hardware itself FOSS?
> 
> I agree that, historically, hardware has often been closed-source.  But, 
> similar to software, there are open-source hardware projects:
> 
> https://en.wikipedia.org/wiki/Open-source_hardware

Of course. But unlike with software, they are relatively few and minor,
and a normal user can't hope to go FOSS hardware as he can with software

Celejar

[toc] | [prev] | [next] | [standalone]

#205432

On 2019-02-15, Mark Allums <mark@allums.email> wrote:
> I just bought a new backup disk, and I want to check it. It's mounted in 
> a USB dock.
>
> Running the following gives an error:
>
> root@martha:~# umount /dev/sdb1
> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
> /dev/sdb1 is in use.
> e2fsck: Cannot continue, aborting.
>
> What's causing this and how do I fix it?  It's not MATE; I tried 
> rebooting to rescue mode, but that didn't help.
>
> Mark

People sometimes recommend 'fuser' in cases like these in order to
identify processes that might be accessing the drive.

I mean, the message says '/dev/sdb1 is in use.' Perhaps it is indeed.

 fuser -v -m /dev/sdb1

Worth a try, maybe, as no one else seems to have suggested it. 

[toc] | [prev] | [next] | [standalone]

#205444

On 2/16/19 2:41 AM, Curt wrote:
> On 2019-02-15, Mark Allums <mark@allums.email> wrote:
>> I just bought a new backup disk, and I want to check it. It's mounted in
>> a USB dock.
>>
>> Running the following gives an error:
>>
>> root@martha:~# umount /dev/sdb1
>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>> /dev/sdb1 is in use.
>> e2fsck: Cannot continue, aborting.
>>
>> What's causing this and how do I fix it?  It's not MATE; I tried
>> rebooting to rescue mode, but that didn't help.
>>
>> Mark
> 
> People sometimes recommend 'fuser' in cases like these in order to
> identify processes that might be accessing the drive.
> 
> I mean, the message says '/dev/sdb1 is in use.' Perhaps it is indeed.
> 
>   fuser -v -m /dev/sdb1
> 
> Worth a try, maybe, as no one else seems to have suggested it.

root@martha:~# fuser -v -m /dev/sdb1
root@martha:~#

No results.  Thanks.

Mark

[toc] | [prev] | [next] | [standalone]

#205492

[Multipart message — attachments visible in raw view] — view raw

On 17.02.2019 1:21, Mark Allums wrote:
> On 2/16/19 2:41 AM, Curt wrote:
>> On 2019-02-15, Mark Allums <mark@allums.email> wrote:
>>> I just bought a new backup disk, and I want to check it. It's
>>> mounted in
>>> a USB dock.
>>>
>>> Running the following gives an error:
>>>
>>> root@martha:~# umount /dev/sdb1
>>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>>> /dev/sdb1 is in use.
>>> e2fsck: Cannot continue, aborting.
>>>
>>> What's causing this and how do I fix it?  It's not MATE; I tried
>>> rebooting to rescue mode, but that didn't help.
>>>
>>> Mark
>>
>> People sometimes recommend 'fuser' in cases like these in order to
>> identify processes that might be accessing the drive.
>>
>> I mean, the message says '/dev/sdb1 is in use.' Perhaps it is indeed.
>>
>>   fuser -v -m /dev/sdb1
>>
>> Worth a try, maybe, as no one else seems to have suggested it.
>
> root@martha:~# fuser -v -m /dev/sdb1
> root@martha:~#
>
> No results.  Thanks.
>
> Mark
>
Maybe something simple like "lsof" command can shed some light on this
problem?
    $ sudo lsof /dev/sdb
    $ sudo lsof /dev/sdb1

Also show us an output of "gdisk" command:
    $ sudo gdisk -l /dev/sdb

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀ 

[toc] | [prev] | [next] | [standalone]

#205536

On 2/17/19 10:59 PM, Alexander V. Makartsev wrote:
> On 17.02.2019 1:21, Mark Allums wrote:
>> On 2/16/19 2:41 AM, Curt wrote:
>>> On 2019-02-15, Mark Allums <mark@allums.email> wrote:
>>>> I just bought a new backup disk, and I want to check it. It's 
>>>> mounted in
>>>> a USB dock.
>>>>
>>>> Running the following gives an error:
>>>>
>>>> root@martha:~# umount /dev/sdb1
>>>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>>>> /dev/sdb1 is in use.
>>>> e2fsck: Cannot continue, aborting.
>>>>
>>>> What's causing this and how do I fix it?  It's not MATE; I tried
>>>> rebooting to rescue mode, but that didn't help.
>>>>
>>>> Mark
>>>
>>> People sometimes recommend 'fuser' in cases like these in order to
>>> identify processes that might be accessing the drive.
>>>
>>> I mean, the message says '/dev/sdb1 is in use.' Perhaps it is indeed.
>>>
>>>   fuser -v -m /dev/sdb1
>>>
>>> Worth a try, maybe, as no one else seems to have suggested it.
>>
>> root@martha:~# fuser -v -m /dev/sdb1
>> root@martha:~#
>>
>> No results.  Thanks.
>>
>> Mark
>>
> Maybe something simple like "lsof" command can shed some light on this 
> problem?
>      $ sudo lsof /dev/sdb
>      $ sudo lsof /dev/sdb1

root@martha:~# lsof /dev/sdb
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
       Output information may be incomplete.
root@martha:~# lsof /dev/sdb1
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
       Output information may be incomplete.
root@martha:~#


> 
> Also show us an output of "gdisk" command:
>      $ sudo gdisk -l /dev/sdb

root@martha:~# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.3

Partition table scan:
   MBR: protective
   BSD: not present
   APM: not present
   GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 23437770752 sectors, 10.9 TiB
Model: ST12000NE0007-2G
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 6AFF425F-836E-4001-840E-FF40A0875F53
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 23437770718
Partitions will be aligned on 2048-sector boundaries
Total free space is 4029 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
    1            2048     23437768703   10.9 TiB    8300
root@martha:~#

Mark

[toc] | [prev] | [next] | [standalone]

#205538

On 2019-02-20, Mark Allums <mark@allums.email> wrote:
>>>
>> Maybe something simple like "lsof" command can shed some light on this 
>> problem?
>>      $ sudo lsof /dev/sdb
>>      $ sudo lsof /dev/sdb1
>
> root@martha:~# lsof /dev/sdb
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
>        Output information may be incomplete.
> root@martha:~# lsof /dev/sdb1
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
>        Output information may be incomplete.
> root@martha:~#

>From what I'm reading you'll have to be martha for this and not root
(*une fois n'est pas coutume*), if martha mounted.

>From man mount.fuse:

 SECURITY
   The fusermount program is installed set-user-gid to fuse. This is done to
   allow users from  fuse group to mount their own filesystem implementations.
   There must however be some limitations, in order to prevent Bad User from doing
   nasty things.  Currently those limitations are:

   1.     The user can only mount on a mountpoint, for which it has write permission

   2.     The mountpoint is not a sticky directory which isn't owned by the user (like /tmp usually
              is)

   3.     No other user (including root) can access the contents of the mounted filesystem.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web