I could not mount an eSATA drive

Asked by Ed Mallett

I'm trying to do a ls -lat on a used Directv eSATA drive using Ubuntu Linux.
It was "going well" I thought, Linux recognized the drive as a WD20EADS,
but the XFS: RT mount failed.
Anyone have a suggestion??

dmesg output follows:

dmesg output 26.588013] eth0: no IPv6 routers present
[ 30.518037] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 30.519554] SGI XFS Quota Management subsystem
[ 30.904363] XFS: This filesystem has a realtime volume, use rtdev=device option
[ 30.904367] XFS: RT mount failed
[ 121.614458] usb 1-4: USB disconnect, address 4
[ 129.044015] usb 1-4: new high speed USB device using ehci_hcd and address 7
[ 129.179558] usb 1-4: configuration #1 chosen from 1 choice
[ 129.182313] scsi9 : SCSI emulation for USB Mass Storage devices
[ 129.182595] usb-storage: device found at 7
[ 129.182597] usb-storage: waiting for device to settle before scanning
[ 134.180303] usb-storage: device scan complete
[ 134.188509] scsi 9:0:0:0: Direct-Access WDC WD20 EADS-00R6B0 PQ: 0 ANSI: 2 <<<<< looking good
[ 134.189113] sd 9:0:0:0: Attached scsi generic sg2 type 0
[ 134.190355] sd 9:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 134.192627] sd 9:0:0:0: [sdb] Write Protect is off
[ 134.192630] sd 9:0:0:0: [sdb] Mode Sense: 38 00 00 00
[ 134.192633] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[ 134.195852] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[ 134.195855] sdb: sdb1 sdb2 sdb3
[ 134.213097] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[ 134.213103] sd 9:0:0:0: [sdb] Attached SCSI disk
[ 134.581680] XFS: This filesystem has a realtime volume, use rtdev=device option
[ 134.581684] XFS: RT mount failed

Thank You very much!!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Ed Mallett
Solved:
Last query:
Last reply:
Revision history for this message
Federico Tello Gentile (federicotg) said :
#1

It is something specific to the XFS filesystem.

XFS: This filesystem has a realtime volume, use rtdev=device option

That opton might be needed in the /etc/fstab file

Revision history for this message
Ed Mallett (lowbird) said :
#2

That dmesg was given at a (what I will call) an "automatic" type mount.
I plugged the eSATA into a USB slot and that "attempt" occurred.
Based on its failure, I am now suspecting that I need to do a "manual" mount attempt.
Unfortunately all my unix experience is 20 years old.
I have been using Ubuntu Linux for two days now.
(It is remarkably usable to a rookie.)
I thought it was funny that Linux recognized an USB stick made in Windows 7.
I was running X Windows at the time and the USB stick ran just as it had in Windows 7
(better even),
Then I tried the eSATA with a Linux based content and it failed.
Thanks for your input!!

Revision history for this message
Federico Tello Gentile (federicotg) said :
#3

Do you have an eSATA port in that machine?

Revision history for this message
Ed Mallett (lowbird) said :
#4

I doubt very seriously if I have a eSATA port on this PC. i didn't find one anyway. To my way of thinking, the machine was made before eSATA was popularized. The eSATA drive is in a Antec MX-1 enclosure which has both an HDMI and a USB connector. I'm using the USB connection to connect the eSATA to the PC. There is a eSATA "bracket" that came with the Antec MX-1. It is one of those that you plug into the back of the PC with a flat plat and a connector on it. If that was installed on my PC, I believe I "would have a eSATA port". There is one small picture about 1 inch square showing the installation which implys there is a Mother Board place to plug in the cable from the eSATA bracket.

The information you provided previously -

"It is something specific to the XFS filesystem.
XFS: This filesystem has a realtime volume, use rtdev=device option
That opton might be needed in the /etc/fstab file" -

unfortunately has no meaning to me.

I was told it was a EXT3+XFS partition and I saw in the Dmesg that the mount looked like is was
"going well" until it tried the XFS part.
Linux X Windows "Places" shows a 16 gb File system - "an unknown device"
/dev/sdb2. This was from the what I will call the "automatic mount attempt".
I think I need a mount command to use in what I will call "a manual mount attempt".

I sure apppreciate it if you gave me "your best guess" as to what that "manual mount attempt"
command would look like.

Thank You Very Much!!!

Revision history for this message
Ed Mallett (lowbird) said :
#5

Well I looked about at DBSTALK and they showed some commands that did an XFSDUMP of one device to another. The command string did several mkdirs, making directories, I thought.
Were they somehow creating "mount points"????
I tried "my best guess" of a manual mount command which was
sudu mount -t xfs -o rtdev=/dev/sdb2 /dev/hr20
The /dev/hr20 was a mount point, I now guess, not a "nickname" for the device.
Because I got "Mount Point Does not Exist".
 And the dmesg looked about the same
I am stumped.
Your thoughts
TYVM!!

Revision history for this message
Ed Mallett (lowbird) said :
#6

Well I thought I had "broken the code" ---- WRONG AGAIN

I tried:ed@ubuntu:~$ sudo mkdir /mnt/pta
ed@ubuntu:~$ sudo mount -t xfs -o rtdev=/dev/sdb2 /dev/sdb2 /mnt/pta
mount: /dev/sdb2 already mounted or /mnt/pta busy

"places" does show a 16bg file system - unknown device/dev/sdb2

ed@ubuntu:~$ umount /dev/sdb2
umount: /dev/sdb2 is not mounted (according to mtab)
ed@ubuntu:~$ sudo mount -t xfs -o rtdev=/dev/sdb2 /dev/sdb2 /mnt/pta
mount: /dev/sdb2 already mounted or /mnt/pta busy

I was getting "Mount point does not exist" until I did the:mkdir /mnt/pta
How can a directory be busy??
I'm stumped again!

If you smart guys (ie Masters of Linux) can't come up with the command
what chance does a 71 year old who has been using Linux for less than a week have?

I'm just about ready to give up (the fun is gone)!!
Thanks for all the assistance!!

Revision history for this message
Ed Mallett (lowbird) said :
#7

ed@ubuntu:~$ sudo mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/pnta
Is the correct syntax in my case.
I get a "dirty block" in /dev/sdb2.
I now understand the you must do a "graceful shutdown" of the eSATA
or you get that "dirty block" from Linux.
It is not a Linux problem, and it is a DirecTV eSATA shutdown problem.
DirecTV HD-DVRs do a lot of "stuff" even when in the "off" position.
You have to do a DirecTV menu shutdown, and when all the leds go out, unplug it.
I should have done A WHOLE LOT MORE research before I started.
So many folks talked about the copying that I thought it was going to be simple.
Actually I think the process of copying an eSATA should come with a "Warning Label".
Sorry to have bothered you folks!!

Revision history for this message
Ed Mallett (lowbird) said :
#8

Well team, I finally got this problem solved!!
The key to the puzzle was to get a "clean superblock" on the eSATA.
Using the menu, doing a "receiver reset" and unplugging the HD-DVR just as the LEDs go out.
I had turned off the UPS that had both the HD-DVR and the eSATA plugged in, which did not work, ie "dirty superblock".
When just the HD-DVR is unplugged at the "no LEDs" point of reset I got a clean superblock.
I did something like this
sudo mkdir /mnt/pnta
sudo mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/pnta
ls -lat /mnt/pnta
cd /mnt/pnta/mw_data
ls -lat
and I got the directory which showed (among other things) the various lines of recordings, their size and the date they were created.
THAT IS WHAT I WANTED ALL ALONG!!!!
Many Many Thanks for all your assistance!!