eSata Drive Unmounting

ciresmis

New Member
Credits
159
Hello,
I just got a new Oyen Digital eSata external drive. I can see it when I start the computer, and I can seemingly mount the drive, but when I create a new folder, it removes that folder and unmounts itself. I am a new Linux user, so I am not yet comfortable with all the terminology. Any ideas how to fix this?

Thanks,
ciresmis
 


f33dm3bits

Gold Member
Gold Supporter
Credits
2,180
After you plug in your usb drive, then open a terminal en do this:
Code:
dmesg | tail -n 10
Post it here, then try to create a folder. Does it give you an error message? Then when it has automatically unmounted itself do the same as before and post it again here.
 

ciresmis

New Member
Credits
159
Thanks f33dm3bits. Here are the results.

After plugged in:
[19713.223324] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=104.244.37.20 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=53 ID=47942 DF PROTO=TCP SPT=443 DPT=34598 WINDOW=0 RES=0x00 RST URGP=0
[19713.937105] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=104.244.37.20 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=53 ID=43544 DF PROTO=TCP SPT=443 DPT=34580 WINDOW=0 RES=0x00 RST URGP=0
[19719.084610] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=199.250.160.129 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=54 ID=11239 DF PROTO=TCP SPT=443 DPT=56580 WINDOW=0 RES=0x00 RST URGP=0
[19719.084806] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=199.250.160.129 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=54 ID=11240 DF PROTO=TCP SPT=443 DPT=56580 WINDOW=0 RES=0x00 RST URGP=0
[19724.745345] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=01:00:5e:00:00:fb:00:00:ca:11:22:33:08:00 SRC=10.0.0.1 DST=224.0.0.251 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3814 PROTO=2
[19728.765036] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=76.13.32.152 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=47 ID=0 DF PROTO=TCP SPT=443 DPT=40180 WINDOW=0 RES=0x00 RST URGP=0
[19728.765222] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=76.13.32.152 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=47 ID=0 DF PROTO=TCP SPT=443 DPT=40180 WINDOW=0 RES=0x00 RST URGP=0
[19729.859153] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=1c:1b:0d:ea:5e:10:00:00:ca:11:22:33:08:00 SRC=104.244.37.20 DST=10.0.0.5 LEN=40 TOS=0x00 PREC=0x20 TTL=53 ID=24424 DF PROTO=TCP SPT=443 DPT=34682 WINDOW=0 RES=0x00 RST URGP=0
[19784.936454] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=01:00:5e:00:00:01:00:00:ca:11:22:33:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=23165 PROTO=2
[19909.939196] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=01:00:5e:00:00:01:00:00:ca:11:22:33:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=23170 PROTO=2

After folder creation (and subsequent unmount):
[20133.419652] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=fe80:0000:0000:0000:7bfc:c6eb:90e4:60cb DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=889152 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[20133.419657] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=fe80:0000:0000:0000:7bfc:c6eb:90e4:60cb DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=641961 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[20133.429784] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=2601:02c1:8500:e580:2c9e:61d1:52e3:392a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=872303 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[20133.429803] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=2601:02c1:8500:e580:2c9e:61d1:52e3:392a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=264271 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[20133.429808] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=2601:02c1:8500:e580:31b5:3103:c3a2:f590 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=573907 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[20133.429813] [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=2601:02c1:8500:e580:31b5:3103:c3a2:f590 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=663509 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[20133.786777] sdo: sdo1 sdo2
[20133.788548] sd 5:0:0:0: [sdo] supports TCG Opal
[20133.788553] sd 5:0:0:0: [sdo] Attached SCSI disk
[20159.944404] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=01:00:5e:00:00:01:00:00:ca:11:22:33:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=23180 PROTO=2

After I create the folder, I do not get an error message. It just removes the folder and unmounts the drive. It then moves the MiniPro to the bottom of the list of Devices.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
2,180
I can't see your disk show up in the first one because of your firewall log file entries. Can you do it for both again but instead this time do it like this:
Code:
dmesg | grep -v UFW | tail -n 10
 

ciresmis

New Member
Credits
159
After plugged in:
[ 8.946922] intel_rapl: Found RAPL domain core
[ 8.946923] intel_rapl: Found RAPL domain dram
[ 8.962318] nvidia-uvm: Loaded the UVM driver, major device number 236.
[ 9.447442] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 9.576405] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[ 9.576485] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
[ 9.576549] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[ 9.632254] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 13.662761] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 13.662821] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready

After folder:
[ 516.331397] scsi 5:0:0:0: Direct-Access ATA ST4000LM024-2AN1 0001 PQ: 0 ANSI: 5
[ 516.331603] sd 5:0:0:0: Attached scsi generic sg4 type 0
[ 516.331741] sd 5:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 516.331742] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[ 516.332245] sd 5:0:0:0: [sdd] Write Protect is off
[ 516.332247] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 516.332335] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 516.406545] sdd: sdd1 sdd2
[ 516.408390] sd 5:0:0:0: [sdd] supports TCG Opal
[ 516.408398] sd 5:0:0:0: [sdd] Attached SCSI disk
 

f33dm3bits

Gold Member
Gold Supporter
Credits
2,180
I think it's sdd, can you do this to check if it's the right disk, checking the size and brand:
Code:
sudo fdisk -l | grep sdd
 

ciresmis

New Member
Credits
159
This is what I got from this:
Disk /dev/sdd: 931.5 GiB, 1000204885504 bytes, 1953525167 sectors
/dev/sdd1 2048 1953521663 1953519616 931.5G 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.

The drive is 4TB.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
2,180
This is what I got from this:
Disk /dev/sdd: 931.5 GiB, 1000204885504 bytes, 1953525167 sectors
/dev/sdd1 2048 1953521663 1953519616 931.5G 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.

The drive is 4TB.
Can you run this in the terminal:
Code:
lsblkd
mount | grep sdd
The first command will show all your block devices connected to your system and how they are partitioned, and the second one how drive sdd is mounted.
 

ciresmis

New Member
Credits
159
This first command "lsblkd" is not found.

Here is the second:
/dev/sdd1 on /media/frynk/Seagate Expansion Drive 1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

I am not having problems with any of my Seagate 1TB Drives. The trouble is with an Oyen MiniPro 4TB Drive. I am using the eSata connection on this drive.

I have attached a list of my drives. There is one 120GB SSD that no longer is found using Linux, but it is available on Windows 7. I have not rebooted into Windows 7 since I installed the MiniPro. No other problems with the other drives.
 

Attachments

Last edited:

ciresmis

New Member
Credits
159
Here is "lsblk" result:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
└─sda1 8:1 0 465.8G 0 part /media/frynk/Blueendless
sdb 8:16 0 119.2G 0 disk
└─sdb1 8:17 0 119.2G 0 part /
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 499M 0 part
├─sdc2 8:34 0 128M 0 part
├─sdc3 8:35 0 918.2G 0 part /media/frynk/BarryDrive
├─sdc4 8:36 0 450M 0 part
└─sdc5 8:37 0 12.3G 0 part
sdd 8:48 0 931.5G 0 disk
└─sdd1 8:49 0 931.5G 0 part /media/frynk/Seagate Expansion Drive 1
sde 8:64 0 931.5G 0 disk
└─sde1 8:65 0 931.5G 0 part /media/frynk/Seagate Backup Plus Drive 0
sdf 8:80 0 931.5G 0 disk
└─sdf1 8:81 0 931.5G 0 part /media/frynk/Seagate Expansion Drive 2
sdg 8:96 1 125G 0 disk
└─sdg1 8:97 1 125G 0 part /media/frynk/REAR_BLUE1
sdl 8:176 1 125G 0 disk
└─sdl1 8:177 1 125G 0 part /media/frynk/FRONT_BLUE
sdm 8:192 0 232.9G 0 disk
└─sdm1 8:193 0 232.9G 0 part
sdn 8:208 0 298.1G 0 disk
└─sdn1 8:209 0 298.1G 0 part /media/frynk/BAR_320
sdo 8:224 0 3.7T 0 disk
├─sdo1 8:225 0 16M 0 part
└─sdo2 8:226 0 3.7T 0 part /media/frynk/MiniPro
sdp 8:240 1 489.1G 0 disk
└─sdp1 8:241 1 489G 0 part /media/frynk/SSD_525
sr0 11:0 1 1024M 0 rom
sdq 65:0 1 465.8G 0 disk
└─sdq1 65:1 1 465.8G 0 part /media/frynk/SSD_500
sdr 65:16 1 223.6G 0 disk
└─sdr1 65:17 1 223.6G 0 part /media/frynk/INTEL_240
 

ciresmis

New Member
Credits
159
One thing I just tried was to review the permissions on the drive. The "File access:" was set to nothing "---", so I changed them all to "Read and write". So far it has kept a folder I created longer than ever before. However, when I reviewed the settings again, they had all reset to "---". Not sure if this means anything, but the folder is still there.

Ah, trying to copy a file over caused it to unmount. Back to square one.
 

ciresmis

New Member
Credits
159
I rebooted my machine into Windows 7. Trying to access the drive gave the following error - 0x80071AC3. Ran out of time to investigate what this means.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
2,180
mount | grep sdo

Nothing happens.
Then that means it is not connected right now which it was before since it was showing up when you posted the output of lsblk
Code:
sdo 8:224 0 3.7T 0 disk 
├─sdo1 8:225 0 16M 0 part 
└─sdo2 8:226 0 3.7T 0 part /media/frynk/MiniPro
Otherwise you wouldn't have seen that. So connect it again make sure you see it again by using lsblk.
And then try it again with:
Code:
dmesg | grep with sdX
X being whatever letter it shows up as from the lsblk command. As for your error code 0x80071AC3. Just in case you didn't know Windows 7 is End of Life and not getting anymore updates.
 

ciresmis

New Member
Credits
159
The Windows 7 End-of-Life is what brought me to Linux.

Well, I broke down and contacted the manufacturer. They suggested I try the USB port instead of eSata, and the drive is working fine on USB3. I recall there being an advantage to using eSata, but I am not sure what it is.

So I guess the eSata port is messed up. Not sure how to fix it. It is just an extension off the MB.
 


Members online


Latest posts

Top