Newsgroup: it.comp.os.linux.iniziare
Titolo: Mount usb drive all'avvio

Ciao al gruppo,
sto cercando di fare il mount di un hard disk esterno all'avvio.
L'hard disk ha un filesystem ext3 e monta correttamente da linea di
comando:
mount -t auto /dev/sda1 /media/usbdrive/
Ho aggiunto una riga /etc/fstab:
/dev/sda1       /media/usbdrive auto    defaults,users  0       0
ma non funzia: all'avvio il drive non monta. Il comando
mount -a
dato una volta avviato, funziona. Il drive si monta.
Un'ipotesi è che i driver per il corretto funzionamento dell'hard disk
vengano caricati dal sistema dopo che fstab è sto letto. Ho cercato un
po' in giro con Google. Qualcuno suggerisce l'uso di udev o hal ma non
so se sia la scelta giusta. Prima di installare e configurare vorrei
qualche dritta. Mi fate sapere che ne pensate, eventualmente
reindirizzandomi verso qualche risorsa?
TN



Udev è un'altra cosa e serve a creare dei device fittizi in base non
solo alle connessioni fisiche ma anche alle caratteristiche dell'unità
stessa. In pratica se attacchi un hard disk esterno o una penna USB il
device sarà /dev/sda. Un'eventuale seconda unità sarà /dev/sdb. Quindi
il nome dipende solo dall'ordine di collegamento, quindi se attacchi
sia l'hard disk che la penna allora non saprai a cosa
corrisponde /dev/sda. Cosa ancora più grave e se ad esempio l'hard disk
presenta più partizioni, in questo caso /dev/sda2 corrisponderà ad una
partizione o no a seconda che attacchi l'hard disk o la penna.
Con udev tu puoi decidere ad esempio di utilizzare un device /dev/penna
per la penna USB, /dev/backup per una partizione di backup sull'hard
disk esterno e /dev/archivio per una partizione per l'archiviazione
sempre sull'hard disk esterno, e magari /dev/foto per la macchina
fotografica. In questo modo potrai scrivere di conseguenza il
file /etc/fstab in modo da gestire correttamente tutte le unità e le
partizioni.
Nel tuo caso non stai utilizzando udev, e comunque udev non ti
risolverebbe il problema.
L'ipotesi che tu fai invece forse è proprio quella giusta... magari la
directory /lib dove si trovano i moduli si trova in una partizione a
parte...  Prova a guardare il tuo file /etc/fstab, o magari postalo.
Per risolvere il problema potresti far montare il disco con uno script
specifico in /etc/rc2.d oppure al momento del login del tuo utente
utilizzando il file ~/.bashrc oppure la directory ~/.config/autostart
Se l'ipotesi è giusta, un'altra strada è quella di compilare
staticamente nel kernel i driver necessari per accedere e montare la
partizione.

 vengano caricati dal sistema dopo che fstab è sto letto. Ho cercato un
La stessa cosa succede con il mio Western Digital.
Per caso anche il tuo ha una funzione tipo "smart-power-on", che accende 
il disco solo quando serve? Durante il boot, io sento proprio il rumore 
del disco che viene attivato, ma purtroppo il file fstab a quel punto è 
già stato letto.
Ho risolto montandolo tramite /etc/rc.d/rc.local
Ciao

 partizione.
Se avesse postato i messaggi di errore usando dmesg o guardando in /var/log
ci sarebbe stata qualche prova in più

i servizi HAL e DBUS li hai avviati ?

 ci sarebbe stata qualche prova in più
FSTAB:
porcone:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro
0       1
/dev/hda9       /home           ext3    defaults        0       2
/dev/hda8       /tmp            ext3    defaults        0       2
/dev/hda5       /usr            ext3    defaults        0       2
/dev/hda6       /var            ext3    defaults        0       2
/dev/hda7       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
/dev/sda1       /media/usbdrive auto    defaults,users  0       0
DMESG: Un po' lungo ma...
Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1)
(
wa...@debian.org
) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Sun Feb 10 22:11:31 UTC 2008
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000007ff0000 (usable)
 BIOS-e820: 0000000007ff0000 - 0000000007ff8000 (ACPI data)
 BIOS-e820: 0000000007ff8000 - 0000000008000000 (ACPI NVS)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
127MB LOWMEM available.
On node 0 totalpages: 32752
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 28656 pages, LIFO batch:7
DMI 2.3 present.
Allocating PCI resources starting at 10000000 (gap: 08000000:f7ff0000)
Detected 795.861 MHz processor.
Built 1 zonelists.  Total pages: 32752
Kernel command line: root=/dev/hda1 ro acpi=off no acpi
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01109000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 121892k/131008k available (1541k kernel code, 8568k reserved,
580k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay using timer specific routine.. 1592.95 BogoMIPS
(lpj=3185916)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0387f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0387f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040
00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
CPU0: Intel Pentium III (Coppermine) stepping 0a
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4761k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0200, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00f6610
PnPBIOS: PnP BIOS version 1.0, entry 0xfa000:0x0, dseg 0xf0000
PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Firmware left 0000:00:0a.0 e100 interrupts enabled, disabling
PCI quirk: region f100-f13f claimed by ali7101 ACPI
PCI quirk: region f140-f15f claimed by ali7101 SMB
Boot video device is 0000:01:00.0
pnp: 00:08: ioport range 0x1060-0x106f has been reserved
pnp: 00:08: ioport range 0xf100-0xf13f has been reserved
pnp: 00:08: ioport range 0xf140-0xf15f has been reserved
PCI: Bridge: 0000:00:01.0
  IO window: 8000-8fff
  MEM window: 80600000-820fffff
  PREFETCH window: disabled.
PCI: Bus 2, cardbus bridge: 0000:00:13.0
  IO window: 00001400-000014ff
  IO window: 00001800-000018ff
  PREFETCH window: 10000000-11ffffff
  MEM window: 12000000-13ffffff
PCI: Bus 6, cardbus bridge: 0000:00:13.1
  IO window: 00001c00-00001cff
  IO window: 00002000-000020ff
  PREFETCH window: 14000000-15ffffff
  MEM window: 16000000-17ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Guessed IRQ 11 for device 0000:00:13.0
PCI: Sharing IRQ 11 with 0000:00:13.1
PCI: Guessed IRQ 11 for device 0000:00:13.1
PCI: Sharing IRQ 11 with 0000:00:13.0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1206385099.656:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Activating ISA DMA hang workarounds.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0e: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303,PNP0f13] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
Freeing unused kernel memory: 196k freed
Time: tsc clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
PCI: Guessed IRQ 10 for device 0000:00:0a.0
e100: eth0: e100_probe: addr 0x80100000, irq 10, MAC addr
00:00:E2:4F:D8:DF
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ALI15X3: IDE controller at PCI slot 0000:00:10.0
ALI15X3: chipset revision 195
ALI15X3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x6050-0x6057, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x6058-0x605f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver
(PCI)
hda: IBM-DJSA-210, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: CD-224E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PCI: Guessed IRQ 11 for device 0000:00:14.0
ohci_hcd 0000:00:14.0: OHCI Host Controller
ohci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:14.0: irq 11, io mem 0x82400000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hda: max request size: 128KiB
hda: 19640880 sectors (10056 MB) w/384KiB Cache, CHS=19485/16/63,
UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
usb 1-2: new full speed USB device using ohci_hcd and address 2
Attempting manual resume
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
usb 1-2: configuration #1 chosen from 1 choice
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected ALi M???? chipset
agpgart: AGP aperture is 64M @ 0xe0000000
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ali15x3_smbus 0000:00:11.0: ALI15X3_smb region uninitialized - upgrade
BIOS or use force_addr=0xaddr
ali15x3_smbus 0000:00:11.0: ALI15X3 not detected, module not inserted.
input: PC Speaker as /class/input/input1
Yenta: CardBus bridge found at 0000:00:13.0 [1025:1010]
Yenta O2: res at 0x94/0xD4: ea/00
Yenta O2: enabling read prefetch/write burst
Yenta: ISA IRQ mask 0x0638, PCI irq 11
Socket status: 30000006
Yenta: CardBus bridge found at 0000:00:13.1 [1025:1010]
Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio, version
0.14.10j-2.6, 22:12:05 Feb 10 2008
Yenta: ISA IRQ mask 0x0638, PCI irq 11
Socket status: 30000006
PCI: Guessed IRQ 10 for device 0000:00:06.0
trident: ALi Audio Accelerator found at IO 0x9000, IRQ 10
ac97_codec: AC97  codec, id:  (Unknown)
gameport: Trident 4DWave is pci0000:00:06.0/gameport0, speed 2386kHz
Real Time Clock Driver v1.12ac
Synaptics Touchpad, model: 1, fw: 4.6, id: 0x925ea1, caps: 0x80471b/
0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input2
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
SCSI subsystem initialized
irda_init()
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
ts: Compaq touchscreen protocol output
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x408-0x40f 0x480-0x48f
0x4d0-0x4d7
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x408-0x40f 0x480-0x48f
0x4d0-0x4d7
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
Adding 369452k swap on /dev/hda7.  Priority:-1 extents:1 across:
369452k
EXT3 FS on hda1, internal journal
loop: loaded (max 8 devices)
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-
de...@redhat.com
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
  Vendor: WDC WD25  Model: 00JB-22REA0       Rev: 0000
  Type:   Direct-Access                      ANSI SCSI revision: 00
usb-storage: device scan complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 27 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 27 00 00 00
sda: assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
NET: Registered protocol family 5
Installing knfsd (copyright (C) 1996 
ok...@monad.swb.de
).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: starting 90-second grace period
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
Bluetooth: Core ver 2.10
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
eth0: no IPv6 routers present
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: mounting fs with errors, running e2fsck is
recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.

 EXT3-fs: mounted filesystem with ordered data mode.
]zac[
File system riconosciuto (richiesto e2fsck?) e montato sembrerebbe.

 DMESG: Un po' lungo ma...
]zac[
Ricercare messaggi per sd sda sda1 in /var/log potrebbe essere utile.

 File system riconosciuto (richiesto e2fsck?) e montato sembrerebbe.
ma poi non é montato affatto. Forse  a causa di quegli errori.... sto
eseguendo il fs check. Vediamo se mi risolve qualcosa.
grazie 1000
TN

 il disco solo quando serve? Durante il boot, io sento proprio il rumore
Ho un Toshiba 250 Gb
Ma non so se ha questa funzione.
tentero' con uno script di avvio
grazie
TN

 TN
De nadia.

 De nadia.
E chi è nadia? Una tua amica ;)
TN