OpenQNX :: The QNX Community Portal

 Jul 25, 2008 - 04:48 PM
Google
  Web openqnx.com   
     Create an account Home · Submit News · QNX Forums · QNX Download · Search   
_
Main Menu
Who's Online
There are 24 unlogged users and 4 registered users online.

You can log-in or register for a user account here.
FAQ FAQ  •  Search Search  •  Register Register  •  Log in to check your private messages Log in to check your private messages
Log in Log in

Trouble accessing USB Hard Drive with ext2/ext3 patition
OpenQNX Forum Index » QNX Users » QNX6 - OS
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
kushalkoolwal
Post subject: Trouble accessing USB Hard Drive with ext2/ext3 patition  PostPosted: Apr 16, 2008 - 09:46 PM
Active Member


Joined: Sep 01, 2006
Posts: 23
I installed QNX Neutrino 6.3.2 on my IDE hard drive (Primary Master). Then I connected a USB Hard Drive which has an ext2 and ext3 partition on it. For some reasons I am not able to mount it and I get errors as follow:
Code:

bash-2.05a# ls /dev/hd10*
/dev/hd10          /dev/hd10t130      /dev/hd10t131
bash-2.05a#
bash-2.05a# mount -t ext2 /dev/hd10t131 /fs/usb_drive
mount: Can't mount /fs/usb_drive (type ext2)
mount: Possible reason: Corrupted file system detected
bash-2.05a#


I am not sure why I get that error. I am sure there is no error on my drive because I can boot into Linux from that drive on other systems.

Here are some other relevant outputs:
Code:

bash-2.05a# usb -vv | less
USB 0 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk, Isoch, Low speed, Full speed

USB 1 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk, Isoch, Low speed, Full speed

USB 2 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk, Full speed, High speed

Device Address             : 1
Upstream Host Controller   : 2
Upstream Device Address    : 0
Upstream Port              : 1
Upstream Port Speed        : High
Vendor                     : 0x1058 (Western Digital)
Product                    : 0x0100 (USB Hard Drive)
Device Release             : r11.05
USB Spec Release           : v2.00
Serial Number              : 0B00012105E7C8E5
Class                      : 0x00 (Independant per interface)
Max PacketSize0            : 64
Languages                  : 0x0409 (English)
Configurations             : 1
  Configuration            : 2
    Attributes             : 0xc0 (Self-powered)
    Max Power              : 98 mA
    Interfaces             : 1
      Interface            : 0 / 0
        Class              : 0x08 (Mass Storage)
        Subclass           : 0x06 (SCSI)
        Protocol           : 0x50

(END)


Code:

bash-2.05a# ls /dev/io-usb/
devu-ehci.so    devu-ohci.so    devu-uhci.so    io-usb
bash-2.05a#


Code:

bash-2.05a# devb-umass cam pnp
bash-2.05a#


Code:

sloginfo

Apr 13 16:00:57    2    19     0 devb-eide 1.00A (Jul 27 2007 14:49:50)
Apr 13 16:00:57    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:00:57    2    19     0 eide_mmap_device_io:  (contig) status 50 != altstatus ff
Apr 13 16:00:57    2    19     0 eide_identify_devices: Generic IDE vid 0, did 0, class 0 rev 0, busno 0, dfunc 0
Apr 13 16:00:57    2    19     0 eide_identify_devices: cmd_addr 1f0, cntl_addr 3f4, irq e, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Apr 13 16:00:57    2    19     0 eide_identify_devices: probing dev 0 status 50, error 0
Apr 13 16:00:57    2    19     0 eide_identify_devices: probing dev 1 status 50, error 0
Apr 13 16:00:57    2    19     0 eide_display_devices: mdl WDC WD153AA-00BAA0 sn WD-WMA2L335193 fw 10.09K11 tid 0, cable 80, max udma 4, cur udma 2, max mdma 2, cur mdma 0, max s
dma -1, cur sdma -1, pio 4, mblk 16
Apr 13 16:00:57    2    19     0 eide_identify: chk 4 cmd ec, tid 1, status 51, astatus 51, error 4
Apr 13 16:00:57    2    19     0 eide_display_devices: mdl LITE-ON DVD SOHD-16P9S sn  fw FS09 tid 1, cable 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma -1, cur sd
ma -1, pio 4, mblk 0
Apr 13 16:00:57    2    19     0 eide_init_devices: WDC WD153AA-00BAA0 path 0, tid 0, udma -1, mdma -1, sdma -1, pio 4, mblk 16
Apr 13 16:00:57    2    19     0 eide_init_devices: LITE-ON DVD SOHD-16P9S path 0, tid 1, udma -1, mdma -1, sdma -1, pio 4, mblk 0
Apr 13 16:00:57    2    19     0 eide_mmap_device_io:  (contig) status 0 != altstatus ff
Apr 13 16:00:57    2    19     0 eide_identify_devices: Generic IDE vid 0, did 0, class 0 rev 0, busno 0, dfunc 0
Apr 13 16:00:57    2    19     0 eide_identify_devices: cmd_addr 170, cntl_addr 374, irq f, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Apr 13 16:00:57    2    19     0 eide_identify_devices: probing dev 0 status 1, error 1
Apr 13 16:00:57    2    19     0 eide_identify_devices: probing dev 1 status 1, error 1
Apr 13 16:00:57    2     5   100 cam-disk.so (Aug 22 2007 14:29:05)
Apr 13 16:00:57    2     5     0 scsi_interpret_sense:  path=0, target=0, lun=0, cam_status=c4, scsi_status=2, flag=00000040, vuflag=0000, cmd=5a, error=70, sense=5, asc=24, ascq
=0
Apr 13 16:00:57    2     5   200 cam-cdrom.so (Jul 27 2007 14:27:22)
Apr 13 16:00:57    2     5     0 scsi_interpret_sense:  path=0, target=1, lun=0, cam_status=c4, scsi_status=2, flag=00000040, vuflag=0000, cmd=5a, error=70, sense=6, asc=29, ascq
=0
Apr 13 16:07:01    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:07:13    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:09:39    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:10:24    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:11:11    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
Apr 13 16:11:42    2     5     0 libcam.so (Jul 27 2007 14:27:15) bver 42000001
(END)


Can anybody please guide me?
 
 View user's profile Send private message  
Reply with quote Back to top
Tim
Post subject:   PostPosted: Apr 17, 2008 - 02:02 PM
Senior Member


Joined: Mar 10, 2004
Posts: 544
kushalkoolwal,

Read the ext2 stuff at this link and see if it applies to your harddrive.

http://www.qnx.com/developers/docs/6.3.0SP3/neutrino/user_guide/fsystems.html


Tim
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
kushalkoolwal
Post subject:   PostPosted: Apr 17, 2008 - 04:35 PM
Active Member


Joined: Sep 01, 2006
Posts: 23
Tim wrote:
kushalkoolwal,

Read the ext2 stuff at this link and see if it applies to your harddrive.

http://www.qnx.com/developers/docs/6.3.0SP3/neutrino/user_guide/fsystems.html

Tim


Thanks Tim.

Actually I did read that piece of information before I posted the query but I was not sure if it really applies to my file system or not. Also does it applies to ext3 also?
 
 View user's profile Send private message  
Reply with quote Back to top
Tim
Post subject:   PostPosted: Apr 17, 2008 - 08:20 PM
Senior Member


Joined: Mar 10, 2004
Posts: 544
kushalkoolwal,

Out of curiosity, what does a 'df' command show?

Also, it doesn't appear to me that ext3 is supported. Is there any chance that /dev/hd10t131 is the ext3 partition?

What happens if you try to mount the /dev/hd10t130 partition with

mount -t ext2 /dev/hd10t130 /fs/usb_drive

Does that parition mount correctly?

Tim
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
micro
Post subject:   PostPosted: Apr 18, 2008 - 12:00 PM
Senior Member


Joined: Jul 22, 2004
Posts: 333
ext3 is actually fully ext2 compatible

So you can mount it and read from it.

But i urge you to NOT write on ext3 in ext2 mode.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
 OpenQNX Forum Index » QNX Users »  QNX6 - OS
Powered by PNphpBB2 © 2003-2007 The PNphpBB Group
Credits
All logos and trademarks in this site are property of their respective owners. The comments are property of their posters.
Powered by OpenQNX: The QNX Community Portal Site
QNX and the QNX logo are registered trademarks of QNX Software Systems.