Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #205488
| From | Mark Allums <mark@allums.email> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Can't scan new disk |
| Date | 2019-02-18 04:20 +0100 |
| Message-ID | <xsHDk-3BM-5@gated-at.bofh.it> (permalink) |
| References | <xrV5D-1kY-1@gated-at.bofh.it> <xrYGd-3Ds-1@gated-at.bofh.it> <xseUG-4YG-1@gated-at.bofh.it> <xsgtr-60i-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web