Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Automounting in userspace with ivman
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 19, 20, 21 ... 27, 28, 29  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
phranzee
Guru
Guru


Joined: 22 Nov 2003
Posts: 397
Location: katowice/pl

PostPosted: Wed Feb 09, 2005 1:23 pm    Post subject: Reply with quote

hi. i have following problem: when the drive is mounted by ivman some files are often broken (i/o error), but when i mount it by hand everything is ok. where's the problem? i've had it with almost every version of ivman/hal/dbus.

ivman 0.5_pre2
dbus 0.23-r2
hal 0.4.5-r2
_________________
signature fault
post dumped ;]
Back to top
View user's profile Send private message
pjj
Apprentice
Apprentice


Joined: 30 Apr 2004
Posts: 165
Location: The Netherlands

PostPosted: Wed Feb 09, 2005 5:08 pm    Post subject: Reply with quote

Going to test this out soon :D
_________________
Pjj's Weblog
Back to top
View user's profile Send private message
rohan28
Tux's lil' helper
Tux's lil' helper


Joined: 12 Dec 2004
Posts: 84
Location: Australia

PostPosted: Thu Feb 10, 2005 3:43 am    Post subject: Reply with quote

phranzee: your problem is very odd. Ivman only calls the 'mount' command, it doesn't do anything which could cause the errors you're seeing. When you say you mount it by hand, do you mean with your own fstab entry, or with the one created by fstab-sync? It's possible that fstab-sync puts some options in the fstab rule which your system doesn't like for some reason...

Does this occur for devices for which an fstab rule is created by HAL (i.e., USB drives etc) and not for things with your own fstab rules (i.e., CD/DVD drives etc)? If so, it seems like weird fstab-sync rules are indeed the culprit, although I am not sure exactly how they'd be messing it up...
Back to top
View user's profile Send private message
phranzee
Guru
Guru


Joined: 22 Nov 2003
Posts: 397
Location: katowice/pl

PostPosted: Thu Feb 10, 2005 7:14 am    Post subject: Reply with quote

rohan28 wrote:
When you say you mount it by hand, do you mean with your own fstab entry, or with the one created by fstab-sync? It's possible that fstab-sync puts some options in the fstab rule which your system doesn't like for some reason...
mount + fstab w/ my own entry.
rohan28 wrote:
Does this occur for devices for which an fstab rule is created by HAL (i.e., USB drives etc) and not for things with your own fstab rules (i.e., CD/DVD drives etc)? If so, it seems like weird fstab-sync rules are indeed the culprit, although I am not sure exactly how they'd be messing it up...
fstab-sync adds only this line:
Code:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
it doesn't change any entry. i get these errors for my dvd drive (afair for cd too, but now it's disconnected). corresponding entry:
Code:
/dev/hdc      /mnt/dvd      iso9660         noauto,ro,speed=4,user              0 0
i haven't tested it with usb drive yet.

i have no idea why, but i can't get this error atm, strange ;)
it looked like this:
Code:
md5sum /mnt/dvd/*
xxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxx
(i/o error)
(i/o error)
(i/o error)
always n last files were broken.
_________________
signature fault
post dumped ;]
Back to top
View user's profile Send private message
rohan28
Tux's lil' helper
Tux's lil' helper


Joined: 12 Dec 2004
Posts: 84
Location: Australia

PostPosted: Thu Feb 10, 2005 11:43 am    Post subject: Reply with quote

Quote:
i have no idea why, but i can't get this error atm, strange :wink:


Maybe it was just a pathological occurence which will never happen again...? (my fingers are crossed :wink: )

Seriously... I cannot think of a single reason why Ivman should be causing this problem. Ivman mounts something purely by calling the 'mount' command... there is a possibility that Ivman or HAL could be triggering a bug elsewhere though. For instance, the mount options Ivman uses (probably umask=0007,gid=100 or similar - check logs) might be causing a problem in the kernel for some odd reason.

See if you can get this bug to occur with HAL running, but not Ivman. See if the kernel gives any messages around the time of these errors.
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 2:04 pm    Post subject: ivman usb device problem Reply with quote

Hi there

first of all, ivman worked just fine on my Gentoo Box for my DVD and DVD-R Drive Mount, Eject etc works out of the box

I'm using

ivman 0.5_pre2
dbus 0.23-r2
hal 0.4.5-r2
udev
hotplug
coldplug

but i got a problem with USB devices like USB Sticks or Drives.

I have: a 20GB Freecom USB Drive (fat32)
60GB SiteCom USB Drive (fat32)
200GB WB USB Drive (still NTFS but will change soon)

If i'm plug one of the drives into my USB Port ivman is mounting them just fine and i can see them in fstab
like:


none /dev/shm tmpfs defaults 0 0

/dev/hdb /media/cdrecorder auto umask=0000,exec,user,noauto,managed 0 0
/dev/hda /media/cdrom auto umask=0000,exec,user,noauto,managed 0 0
/dev/floppy/0 /media/floppy auto umask=0000,exec,user,noauto,managed 0 0
/dev/sdc1 /media/FHD2-PRO vfat umask=0000,exec,user,noauto,managed 0 0
/dev/sdd1 /media/usbdisk reiserfs umask=0000,exec,user,noauto,managed 0 0

and i also can see them in the Konqueror but if i click on one of the drives i got the following Errormessage:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
or too many mounted file systems
Please check that the disk is entered correctly.

Clicking on "OK" i got this again:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
or too many mounted file systems
Please check that the disk is entered correctly.

for sdd1 i know the problem is, that fstab is saying it is a reiserfs but it is really a NTFS drive

but sdc1 is formated with FAT32 and in fstab it is mounted as vfat
so should be all right but i havn't any access to the drive.

Any Idea ?????

Again my DVD and DVD-R Drive is working fine
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 2:04 pm    Post subject: ivman usb device problem Reply with quote

Hi there

first of all, ivman worked just fine on my Gentoo Box for my DVD and DVD-R Drive Mount, Eject etc works out of the box

I'm using

ivman 0.5_pre2
dbus 0.23-r2
hal 0.4.5-r2
udev
hotplug
coldplug

but i got a problem with USB devices like USB Sticks or Drives.

I have: a 20GB Freecom USB Drive (fat32)
60GB SiteCom USB Drive (fat32)
200GB WB USB Drive (still NTFS but will change soon)

If i'm plug one of the drives into my USB Port ivman is mounting them just fine and i can see them in fstab
like:


none /dev/shm tmpfs defaults 0 0

/dev/hdb /media/cdrecorder auto umask=0000,exec,user,noauto,managed 0 0
/dev/hda /media/cdrom auto umask=0000,exec,user,noauto,managed 0 0
/dev/floppy/0 /media/floppy auto umask=0000,exec,user,noauto,managed 0 0
/dev/sdc1 /media/FHD2-PRO vfat umask=0000,exec,user,noauto,managed 0 0
/dev/sdd1 /media/usbdisk reiserfs umask=0000,exec,user,noauto,managed 0 0

and i also can see them in the Konqueror but if i click on one of the drives i got the following Errormessage:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
or too many mounted file systems
Please check that the disk is entered correctly.

Clicking on "OK" i got this again:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
or too many mounted file systems
Please check that the disk is entered correctly.

for sdd1 i know the problem is, that fstab is saying it is a reiserfs but it is really a NTFS drive

but sdc1 is formated with FAT32 and in fstab it is mounted as vfat
so should be all right but i havn't any access to the drive.

Any Idea ?????

Again my DVD and DVD-R Drive is working fine
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 4:29 pm    Post subject: Some more input Reply with quote

dmesg outputs this

: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66)
libata version 1.10 loaded.
sata_nv version 0.5
ACPI: PCI Interrupt Link [LTID] BIOS reported IRQ 0, using IRQ 22
ACPI: PCI Interrupt Link [LTID] enabled at IRQ 22
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:0a.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD400 irq 22
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD408 irq 22
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 88:007f
ata1: dev 0 ATA, max UDMA/133, 398297088 sectors: lba48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 88:007f
ata2: dev 0 ATA, max UDMA/133, 398297088 sectors: lba48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 18
ACPI: PCI interrupt 0000:02:0b.0[A] -> GSI 18 (level, low) -> IRQ 18
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[18] MMIO=[feadf800-feadffff] Max Packet=[2048]
ieee1394: raw1394: /dev/raw1394 device initialized
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 21
ACPI: PCI interrupt 0000:00:02.2[C] -> GSI 21 (level, low) -> IRQ 21
ehci_hcd 0000:00:02.2: PCI device 10de:00e8 (nVidia Corporation)
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 21, pci mem 0xfebffc00
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 20
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 20 (level, low) -> IRQ 20
ohci_hcd 0000:00:02.0: PCI device 10de:00e7 (nVidia Corporation)
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 20, pci mem 0xfebfd000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 22
ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 22 (level, low) -> IRQ 22
ohci_hcd 0000:00:02.1: PCI device 10de:00e7 (nVidia Corporation)
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: irq 22, pci mem 0xfebfe000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.2
usb 1-3: new high speed USB device using ehci_hcd and address 4
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 4 ports detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usb 2-1: new low speed USB device using ohci_hcd and address 2
usb 2-2: new low speed USB device using ohci_hcd and address 3
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e018000089807b]
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: USB HID v1.00 Keyboard [Darfon USB Combo Keyboard] on usb-0000:00:02.0-1
input: USB HID v1.00 Device [Darfon USB Combo Keyboard] on usb-0000:00:02.0-1
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:02.0-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
Bluetooth: BlueFRITZ! USB driver ver 1.1
usbcore: registered new driver bfusb
Advanced Linux Sound Architecture Driver Version 1.0.6 (Sun Aug 15 07:17:53 2004 UTC).
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 17
ACPI: PCI interrupt 0000:02:09.0[A] -> GSI 17 (level, low) -> IRQ 17
ALSA device list:
#0: Sound Blaster Live! (rev.7) at 0xc400, irq 17
oprofile: using NMI interrupt.
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
powernow-k8: 0 : fid 0x0 (800 MHz), vid 0xa (1300 mV)
powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8: 2 : fid 0xc (2000 MHz), vid 0x2 (1500 mV)
cpu_init done, current fid 0xc, vid 0x0
powernow-k8: ph2 null fid transition 0xc
ACPI wakeup devices:
UAR1 UAR2 USB0 MAC USB1 USB2 P0P1
ACPI: (supports S0 S1 S3 S4 S5)
UDF-fs: No VRS found
XFS mounting filesystem sda3
Ending clean XFS mount for filesystem: sda3
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 196k freed
Adding 3911816k swap on /dev/sda2. Priority:-1 extents:1
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 16
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-6629 Wed Nov 3 13:12:51 PST 2004
XFS mounting filesystem sda4
Ending clean XFS mount for filesystem: sda4
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
cdrom: open failed.
cdrom: open failed.
fbsplash: switching to verbose mode
fbsplash: console 0 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 0
fbsplash: console 1 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 1
fbsplash: console 2 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 2
fbsplash: console 3 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 3
fbsplash: console 4 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 4
fbsplash: console 5 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 5
fbsplash: console 6 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 6
fbsplash: console 7 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 7
fbsplash: console 8 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 8
fbsplash: console 9 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 9
fbsplash: console 10 using theme 'gentoo'
fbsplash: switched splash state to 'on' on console 10
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
drivers/usb/input/hid-input.c: event field not found
drivers/usb/input/hid-input.c: event field not found
NVRM: Xid: 24, L2 -> L1
usb 1-8: new high speed USB device using ehci_hcd and address 5
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: MK2023GAS Rev: MA01
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
sdc: sdc1
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
Unable to load NLS charset cp437
FAT: codepage cp437 not found
VFS: busy inodes on changed media.
Unable to load NLS charset cp437
FAT: codepage cp437 not found
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
hda: tray open
end_request: I/O error, dev hda, sector 6728860
Buffer I/O error on device hda, logical block 1682215
hda: tray open
end_request: I/O error, dev hda, sector 6728864
Buffer I/O error on device hda, logical block 1682216
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
VFS: busy inodes on changed media.
usb 1-8: USB disconnect, address 5
usb 1-8: new high speed USB device using ehci_hcd and address 6
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: MK2023GAS Rev: MA01
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
sdc: sdc1
Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi3, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
usb 1-8: USB disconnect, address 6
usb 1-8: new high speed USB device using ehci_hcd and address 7
usb 1-8: device descriptor read/64, error -71
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
Vendor: Model: USB DISK 2.0 Rev: 1.01
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdc: 243712 512-byte hdwr sectors (125 MB)
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
SCSI device sdc: 243712 512-byte hdwr sectors (125 MB)
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
sdc: sdc1
Attached scsi removable disk sdc at scsi4, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi4, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
usb 1-8: USB disconnect, address 7
usb 1-6: new high speed USB device using ehci_hcd and address 8
usb 1-6: device descriptor read/64, error -71
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb 1-4: new high speed USB device using ehci_hcd and address 9
usb 1-4: device descriptor read/64, error -71
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
Vendor: TOSHIBA Model: MK2023GAS Rev: MA01
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
SCSI device sdc: 39070080 512-byte hdwr sectors (20004 MB)
sdc: assuming drive cache: write through
sdc: sdc1
Attached scsi disk sdc at scsi5, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi5, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Vendor: WDC WD20 Model: 00JB-32EVA0 Rev: 0 0
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdd: 390721968 512-byte hdwr sectors (200050 MB)
sdd: assuming drive cache: write through
SCSI device sdd: 390721968 512-byte hdwr sectors (200050 MB)
sdd: assuming drive cache: write through
sdd: sdd1
Attached scsi disk sdd at scsi6, channel 0, id 0, lun 0
Attached scsi generic sg3 at scsi6, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
usb 1-6: USB disconnect, address 8
usb 1-4: USB disconnect, address 9
usb 1-8: new high speed USB device using ehci_hcd and address 10
usb 1-8: device descriptor read/64, error -71
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
Vendor: IC25N060 Model: ATMR04-0 Rev: 0811
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdc: 117210240 512-byte hdwr sectors (60012 MB)
sdc: assuming drive cache: write through
SCSI device sdc: 117210240 512-byte hdwr sectors (60012 MB)
sdc: assuming drive cache: write through
sdc: sdc1
Attached scsi disk sdc at scsi7, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi7, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
ISO 9660 Extensions: RRIP_1991A
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
Unable to load NLS charset cp437
FAT: codepage cp437 not found
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
nightfrost
Apprentice
Apprentice


Joined: 07 Dec 2004
Posts: 293
Location: Sweden

PostPosted: Fri Feb 11, 2005 4:41 pm    Post subject: Reply with quote

Quote:
Unable to load NLS charset cp437
FAT: codepage cp437 not found


I assume you can't mount those partitions even when you're not using ivman (correct?). I had this problem I while back and managed to fix it through a kernel recompile. Check out Filesystems --> DOS/FAT/NT Filesystems -->, and perhaps Filesystems --> Native language support as well. You might need to change the charset. I managed to solve my problem by changing to cp850 (Europe). Try that...

N.B: if you can mount those partitions manually, i.e. while ivman is not running. Then you should probably ignore this post...
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 4:55 pm    Post subject: Manual Mounting Reply with quote

Hi
You are right i can't mount by hand
I'll go right now and check my Kernel for cp 437 and cp 850
maybe this is also the problem !

thank You

I will post how it works
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 5:11 pm    Post subject: Reply with quote

Hurra !!!!!

the Codepage 437 fixed the problem !!!

It si working now

I love this Forum and i love Gentoo !!!

Thank you
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 5:13 pm    Post subject: Still trouble on my NTFS Drive Reply with quote

But it si still not working on my NTFS formated Drive
(Yes NTFS Support is in the Kernel)

Errormessage:

mount: unknown filesystem type 'reiserfs'
Please check that the disk is entered correctly.

Reiser ??? I'm not using Reiser at all

Any Ideas
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
nightfrost
Apprentice
Apprentice


Joined: 07 Dec 2004
Posts: 293
Location: Sweden

PostPosted: Fri Feb 11, 2005 5:23 pm    Post subject: Reply with quote

You sure the partition works under Windows?
Can you post the relevant line from /etc/fstab? Is that line generated automatically? is ntfs compiled in the kernel or as a module?
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 5:32 pm    Post subject: Fstab Reply with quote

Yep NTFS is in the kernel and the frive works fine with Windows.

here the fstab line
/dev/sdc1 /media/usbdisk reiserfs exec,user,noauto,managed 0 0

It will be inserted automaticly by ivman !
thinks it is reiser for some reason
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
nightfrost
Apprentice
Apprentice


Joined: 07 Dec 2004
Posts: 293
Location: Sweden

PostPosted: Fri Feb 11, 2005 5:55 pm    Post subject: Reply with quote

yeah, that is weird... As far as i know, that line is generated by hald and not ivman. So, for some reason hald thinks that your drive is reiser. You could try searching hal buglists. I really don't know why it would behave like that...

(By the way, I assume you're using the latest versions of dbus, hal, and ivman, i.e. ~arch)
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Fri Feb 11, 2005 6:55 pm    Post subject: Version Reply with quote

I will look into the hald stuff

I guess i use the latest versions of

dbus
hald
ivman

I hope
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
rohan28
Tux's lil' helper
Tux's lil' helper


Joined: 12 Dec 2004
Posts: 84
Location: Australia

PostPosted: Sat Feb 12, 2005 12:43 am    Post subject: Reply with quote

Rusty1973: Yes, it's definitely a HAL problem, not Ivman. It's very odd that HAL thinks your drive is reiserfs. Here are some ideas for fixing it:

* In /etc/filesystems (you may have to create it), put ntfs before reiserfs. This makes 'mount -t auto' try the NTFS filesystem before ReiserFS; I'm hoping HAL might also respect this file. For more info, do 'man mount' and find the bit about /etc/filesystems .
* Mess around with whether or not filesystems are compiled as modules. If NTFS is a module, try compiling it in... or vice versa, if it's currently built in :-) Maybe try ReiserFS as a module too, if possible (although if you use it for / as I do, you can't of course...)

And, of course, keep trying new versions of HAL as they come out... :-)
Back to top
View user's profile Send private message
G2k
l33t
l33t


Joined: 06 Mar 2004
Posts: 672
Location: Rome, Italy

PostPosted: Sat Feb 12, 2005 4:37 pm    Post subject: Reply with quote

strange I was getting this same error message
Code:
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
or too many mounted file systems
Please check that the disk is entered correctly.
with my usb stick but somehow everything fixed itself on its own @_@ anyways, my questions is how should one unmount a usb stick? when i plug it in it automatically mounts, but then do i have to just pull the stick out or do i have to manually umount /media/usbdisk?
_________________
Animula vagula blandula,
Hospes comesque corporis,
Quae nunc abibis in loca
Pallidula rigida nudula,
Nec ut soles dabis iocos...
- Imp. Caesar Hadrianus
Back to top
View user's profile Send private message
Rusty1973
n00b
n00b


Joined: 20 Jan 2005
Posts: 67
Location: Hamburg Germany

PostPosted: Sat Feb 12, 2005 4:50 pm    Post subject: filesystems Reply with quote

I tryed to change /etc/filesystems
It is a symbolic link to ../proc/filesystems.

I can't change this file at all, even not as root user
but your idea sounds like the problem. Reiserfs isn't in there.
I'll go and put reiser in my kernel.
I'm not using it my system is running on ext2 for /boot and everthing else is xfs

Hi G2K i had this problem too with vfat and it was a problem of the codepage setting in my kernel, i disabled the codepage 437 (default for fat filesystems) just enabled it and it worked!

Thanks a lot for all you guys help !

What a great forum
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"
Back to top
View user's profile Send private message
d4rk74m4
Arch/Herd Tester
Arch/Herd Tester


Joined: 22 Feb 2004
Posts: 151

PostPosted: Sat Feb 12, 2005 5:01 pm    Post subject: Reply with quote

phranzee wrote:
hi. i have following problem: when the drive is mounted by ivman some files are often broken (i/o error), but when i mount it by hand everything is ok. where's the problem? i've had it with almost every version of ivman/hal/dbus.

ivman 0.5_pre2
dbus 0.23-r2
hal 0.4.5-r2


Okay, I also have the same problem when using ivman for automounting. I just did a complete backup to about 30-40 dvd's, reinstalled Gentoo and found that I couldn't restore my backups. I was extremely worried at this point.

I was getting i/o errors about accessing beyond the end of the device. I removed ivman, dbus and hal from startup, rebooted, then mounted the devices myself and everything was fine... thankfully!
Back to top
View user's profile Send private message
rohan28
Tux's lil' helper
Tux's lil' helper


Joined: 12 Dec 2004
Posts: 84
Location: Australia

PostPosted: Sun Feb 13, 2005 1:47 am    Post subject: Reply with quote

d4rk74m4, phranzee: Does the I/O problem occur with the first CD/DVD inserted, or only with subsequent ones? I'm thinking it might be a problem with unmounting (if you are using Ivman and just hitting the 'eject' button for CDs/DVDs, maybe you should try manually unmounting them first). One of the places Ivman could really use some work is on ejecting CDs/DVDs; the kernel seems to break a bit when you eject CDs without unmounting them first (which is fair enough), and we need to fix this in userspace somehow. Unfortunately HAL doesn't/can't send any message to Ivman when the eject button is pressed on most drives, so I'm not sure how to go about this.

Edit: I have been able to reproduce this, and I'm convinced it's a kernel bug. It seems like the kernel gets confused about the size of discs; if you put in a small disc, then eject it without unmounting first, and then put in a larger one, the kernel refuses to read past the size of the smaller disc. That's why it's always the last files which have I/O errors (i.e. the ones nearest the end of the disc). I'm going to do more testing; for now, just unmount CDs/DVDs before ejecting, and that should take care of the problem.

Which kernel versions are you each using? I'm using gentoo-dev-sources 2.6.10; I've got my fingers crossed this is already fixed in 2.6.11_rc3, though I don't really expect it will be, since ejecting without unmounting is officially the wrong thing to do. But, we shall see.


Last edited by rohan28 on Sun Feb 13, 2005 3:15 am; edited 1 time in total
Back to top
View user's profile Send private message
rohan28
Tux's lil' helper
Tux's lil' helper


Joined: 12 Dec 2004
Posts: 84
Location: Australia

PostPosted: Sun Feb 13, 2005 1:58 am    Post subject: Reply with quote

G2k: Sorry for neglecting this in my last post... yes, you should always unmount a USB disk manually before yanking it, regardless of whether or not you're using Ivman. Sometimes things will be OK if you just yank it, but sometimes they won't - and udev, HAL and the kernel don't like it in any case, so even if your data remains OK, you might see weird things like HAL not cleaning up mount points, udev not removing device node etc. (this is somewhat related to the CD/DVD unmounting problem - we're used to just ejecting CDs/DVDs because they're mounted read-only, so we don't care so much about unmounting them.)
Back to top
View user's profile Send private message
nightfrost
Apprentice
Apprentice


Joined: 07 Dec 2004
Posts: 293
Location: Sweden

PostPosted: Sun Feb 13, 2005 10:44 am    Post subject: Reply with quote

G2k: you could edit this file /usr/share/hal/fdi/90defaultpolicy/storage-policy.fdi and change the following line (it's in the beginning, line 14 or something):

Code:
      <merge key="storage.policy.default.mount_option.user" type="bool">true</merge>


to

Code:
      <merge key="storage.policy.default.mount_option.users" type="bool">true</merge>


That is, you change "user" to "users". This gives all your users permission to unmount drives. And so you can easily do this e.g. in konqueror by right clicking the proper device under the device list and choose unmount...
Back to top
View user's profile Send private message
G2k
l33t
l33t


Joined: 06 Mar 2004
Posts: 672
Location: Rome, Italy

PostPosted: Sun Feb 13, 2005 11:13 am    Post subject: Reply with quote

k, thanks!:)
_________________
Animula vagula blandula,
Hospes comesque corporis,
Quae nunc abibis in loca
Pallidula rigida nudula,
Nec ut soles dabis iocos...
- Imp. Caesar Hadrianus
Back to top
View user's profile Send private message
nightfrost
Apprentice
Apprentice


Joined: 07 Dec 2004
Posts: 293
Location: Sweden

PostPosted: Sun Feb 13, 2005 4:49 pm    Post subject: Reply with quote

With the latest hald (I must have upgraded it with emerge -Du without noticing it), I had problems mounting usb sticks. I solved it by commenting out the utf8 bit in /usr/share/hal/fdi/90defaultpolicy/storage-policy.fdi (line 168 in my file):

Code:
          <!-- UTF-8 business commented out by nightfrost
          <!-- Use UTF-8 charset for vfat -->
          <match key="volume.fstype" string="vfat">
            <merge key="volume.policy.mount_option.iocharset=utf8" type="bool">true</merge>
          </match>
-->


I don't really know why it's there and I don't think it was there before (in the older version). Anyway, if anyone has the same problem (I don't remember the error I got - perhaps it was: bad block something, or too many mounted something something) this might help them...
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... 19, 20, 21 ... 27, 28, 29  Next
Page 20 of 29

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum