vfat disk D a supermount::nepracuje to spravne

Sekcia: Konfigurácia 09.06.2005 | 18:14
dobinko   Návštevník
Ahoj všetci. Mam problem s dalsim diskom VFAT menovka D vo Windoze. Ide o to že mi ho system sice aj primountuje ale nic na disku nieje. Taktiez nemozem ani ako root ani ako user zapisovat na disk. Mozte mi napisat co mam dat do fstab? presny riadok. Od instalacie tam mam toto: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/hda6 / reiserfs notail,defaults 1 1 /dev/hdb /mnt/cdrom auto umask=0,user,iocharset=iso8859-2,sync,codepage=852,noauto,ro,exec,users 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-2,sync,codepage=852 0 0 none /proc proc defaults 0 0 /dev/hda1 /windows/C ntfs umask=0,nls=iso8859-2,ro,gid=users,users 0 0 /dev/hda2 /windows/D vfat umask=0,users 0 0
    • Re: vfat disk D a supermount::nepracuje to spravne 06.06.2005 | 16:51
      peter golis   Návštevník
      je te disk pripojeny? vidis ho vo vystupe prikazov mount, alebo df -h ? bolo na tom disku nieco nahrate? jedna sa o disk s FAT a nie NTFS?
      • Re: Re: vfat disk D a supermount::nepracuje to spr 06.06.2005 | 16:59
        dobinko   Návštevník
        Ano je to disk FAT, bolo na tom nieco nahrate, ale aj som to sformatoval a nic. ako mount je pripojeny, Niekedy sa mu zachce pisat v tom zmysle ze bad superblock ....alebo že je primount vela filesystemov. Tomu fakt nerozumiem. Myslim ze nemusim hadzat vypis, vypise to čo som písal. Ale zase niekedy mi ho pripoji a mozem zapisovat ale ked ho propojim cez diskdrake co je trohu riziko robit to takymto sposobom. (Mandriva LE 2005 a disk 80GB - 30FAT 20NTFS a 30je linux. ak som nespomenul. Nebude to podporou FAT nieco v tom zmysle ze 30GB je na FAT vela? (podpora velkych diskov)
        • Re: Re: Re: vfat disk D a supermount::nepracuje to 06.06.2005 | 17:48
          peter Golis   Návštevník
          no, najlepsie by bolo poslat sem vypis z dmesg a fdisk -l. inac, kedysi bolo obmedzenie velkosti na FAT a v linuxe to robilo problemy, ale nemozem potvrdit. nemam mandrivu a ani taky velky disk.
          • Re: Re: Re: Re: vfat disk D a supermount::nepracuj 06.06.2005 | 18:00
            dobinko   Návštevník
            ubsystem revision 20050211 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) Uncovering SIS963 that hid as a SIS503 (compatible=0) Enabling SiS 96x SMBus. ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Power Resource [URP1] (off) ACPI: Power Resource [URP2] (off) ACPI: Power Resource [FDDP] (off) ACPI: Power Resource [LPTP] (off) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 *12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 10 devices PnPBIOS: Disabled PCI: Using ACPI for IRQ routing ** PCI interrupts are no longer routed automatically. If this ** causes a device to stop working, it is probably because the ** driver failed to call pci_enable_device(). As a temporary ** workaround, the "pci=routeirq" argument restores the old ** behavior. If this argument makes the device work again, ** please email the output of "lspci" to bjorn.helgaas@hp.com ** so I can fix the driver. apm: BIOS not found. audit: initializing netlink socket (disabled) audit(1118068456.957:0): initialized inotify device minor=63 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x0 Initializing Cryptographic API vesafb: framebuffer at 0xc0000000, mapped to 0xcc880000, using 3750k, total 65472k vesafb: mode is 800x600x16, linelength=1600, pages=7 vesafb: protected mode interface info at c704:0000 vesafb: scrolling: redraw vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 35024 bytes,<6>...found (800x600, 34976 bytes, v3). Console: switching to colour frame buffer device 92x32 fb0: VESA VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe@suse.de) and petero2@telia.com Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SIS5513: IDE controller at PCI slot 0000:00:02.5 SIS5513: chipset revision 0 SIS5513: not 100% native mode: will probe irqs later SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA Probing IDE interface ide0... hda: ST380011A, ATA DISK drive hdb: ASUS CRW-5224A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hda: max request size: 1024KiB hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100) hda: cache flushes supported /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 p6 > mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard on isa0060/serio0 md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 8Kbytes TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) NET: Registered protocol family 1 ACPI wakeup devices: PCI0 PS2K UAR1 USB1 USB2 EHCI LAN MDM AUD ACPI: (supports S0 S1 S4 S5) BIOS EDD facility v0.16 2004-Jun-25, 1 devices found devfs_mk_dev: could not append to parent for md/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). ReiserFS: hda6: found reiserfs format "3.6" with standard journal ReiserFS: hda6: using ordered data mode ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda6: checking transaction log (hda6) ReiserFS: hda6: Using r5 hash to sort names Freeing unused kernel memory: 264k freed usbcore: registered new driver usbfs usbcore: registered new driver hub ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 20 ohci_hcd 0000:00:03.0: OHCI Host Controller ohci_hcd 0000:00:03.0: irq 20, pci mem 0xcfff9000 ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected ACPI: PCI interrupt 0000:00:03.1[B] -> GSI 21 (level, low) -> IRQ 21 ohci_hcd 0000:00:03.1: OHCI Host Controller ohci_hcd 0000:00:03.1: irq 21, pci mem 0xcfffa000 ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 2 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected usb 1-2: new low speed USB device using ohci_hcd and address 2 ACPI: PCI interrupt 0000:00:03.2[D] -> GSI 23 (level, low) -> IRQ 23 ehci_hcd 0000:00:03.2: EHCI Host Controller ehci_hcd 0000:00:03.2: irq 23, pci mem 0xcfffb000 ehci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 3 PCI: cache line size of 64 is not supported by device 0000:00:03.2 ehci_hcd 0000:00:03.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 3-0:1.0: USB hub found hub 3-0:1.0: 6 ports detected usbcore: registered new driver hiddev usb 1-2: USB disconnect, address 2 usb 1-2: new low speed USB device using ohci_hcd and address 3 input: USB HID v1.00 Mouse [04b3:310b] on usb-0000:00:03.0-2 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver usbcore: registered new driver usbmouse drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver ts: Compaq touchscreen protocol output Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected SiS 741 chipset agpgart: Maximum main memory to use for agp memory: 149M agpgart: AGP aperture is 64M @ 0xd0000000 Supermount version 2.0.4 for kernel 2.6 ntfs: Ignoring new-style parameters in presence of obsolete ones NTFS driver 2.1.22 [Flags: R/O DEBUG MODULE]. NTFS volume version 3.1. loop: loaded (max 8 devices) hdb: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 sis900.c: v1.08.07 11/02/2003 ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 19 (level, low) -> IRQ 19 0000:00:04.0: Realtek RTL8201 PHY transceiver found at address 1. 0000:00:04.0: Using transceiver found at address 1 as default eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 19, 00:0b:6a:b2:0e:b8. eth0: Media Link Off ACPI: Power Button (FF) [PWRF] Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 NET: Registered protocol family 17 ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 intel8x0_measure_ac97_clock: measured 49659 usecs intel8x0: clocking to 48000 NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timeout, status 00000004 00000000 Bluetooth: Core ver 2.7 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.7 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM ver 1.5 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized eth0: Media Link On 100mbps full-duplex NET: Registered protocol family 10 Disabled Privacy Extensions on device c03b26e0(lo) IPv6 over IPv4 tunneling driver Disabled Privacy Extensions on device c962f800(sit0) mtrr: 0xc0000000,0x4000000 overlaps existing 0xc0000000,0x2000000 Installing knfsd (copyright (C) 1996 okir@monad.swb.de). eth0: no IPv6 routers present portmap: server localhost not responding, timed out RPC: failed to contact portmap (errno -5). portmap: server localhost not responding, timed out RPC: failed to contact portmap (errno -5). portmap: server localhost not responding, timed out RPC: failed to contact portmap (errno -5). bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 0 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 1 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 2 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 3 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 4 changed to on bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3). bootsplash: status on console 5 changed to on smb_add_request: request [c8fa1e40, mid=16458] timed out! smb_add_request: request [c8fa1e40, mid=16459] timed out! smb_add_request: request [c8fa1e40, mid=14627] timed out! smb_add_request: request [c8fa1e40, mid=14628] timed out! SMB connection re-established (-5) SMB connection re-established (-5) smb_add_request: request [c8fa1e40, mid=16460] timed out!
            • Re: Re: Re: Re: Re: vfat disk D a supermount::nepr 06.06.2005 | 19:42
              dobinko   Návštevník
              Pridám že to byť dmesg výpis a ten druhý fdisk -l je aspom u mna nefunkčný
              • Re: Re: Re: Re: Re: Re: vfat disk D a supermount:: 07.06.2005 | 12:49
                peter golis   Návštevník
                vypis fdisk -l je funkcny, ale vecsinou iba pod rootom. uzivatel to moze (obcas) spustit cez /sbin/fdisk -l to ti vylistuje rozdelenie diskov v ludsky citatelnej forme. obcas aj s rozdelenim roznych usb klucov co tam uz nie su pripojene ;-) ps.: ten disk d: je na tom istom pocitaci alebo cez siet?
                • Re: Re: Re: Re: Re: Re: Re: vfat disk D a supermou 07.06.2005 | 13:21
                  dobinko   Návštevník
                  áno to je všetko ten jeden 80GB disk, a rozdelený ako som to písal vyžšie ale napíšem to znovu aby ste nemusely pozerať hore: 80GB>>30FAT, 30Linux,20NTFS}windows 30GBFAT prázdny dátovy disk 30GBLinux OS Linux Mandriva 20GBNTFS Microsoft Windows XP nie na dlho. Ak sa to spravý ten disk D môžem si preniesť údaje na FAT a tým pádom Windows chcem spláchnuť. Len ma to hnevá že nieviem prečo mi ho nechce čítať, zapisovať..
                  • Re: Re: Re: Re: Re: Re: Re: Re: vfat disk D a supe 07.06.2005 | 13:45
                    peter golis   Návštevník
                    pretoze to asi nie je hda2, ale hda5. skus ako root napisat fdisk -l a uvidis. zatial som este nevidel aby windows standardne vytvorilo disk d v primarnej oblasti. vzdy ho robilo v rozsirenej. vynimka bola, ak si to robil rucne a prestavil si mu standardne hodnoty. ps.: to smb timed out, teda problem pripajania sietoveho disku suvisi z vypnutym pocitacom a nei s tymto problemom.
                    • Re: Re: Re: Re: Re: Re: Re: Re: Re: vfat disk D a 07.06.2005 | 14:19
                      dobinko   Návštevník
                      Ok. Idem na prestávku potom to skúsim. Len dodám že je možné že som to spravil ja ten disk lebo SOm raz daval preč SuSE,(to som moc nevedel s tým robiť ale človek sa učí no nie?) a chcel som tam na čas len windows lebo on poznal ovládače na moj Hardware a taktiež som nevedel v tedy kompilovať. tak som fdiskom v dose odpalil ext partíciu a pridal ju nanovo, sformátoval a bolo. Možno som v tedy spravil chybu, ale opakujem sa že windows mi bere tento disk bez problémov taktiež môžem nan zapisovať. No ved potom ked donesiem výpis fdisk -l zistíme.
                      • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: vfat disk 07.06.2005 | 15:04
                        peter golis   Návštevník
                        pohoda. ale ak to bolo cez windoze fdisk, tak jeho interny wizard robi presne toto. startovaci logicky disk je na primarneh particii (hda1) a vsetko ostatne je automaticky dane ako extended. a disky v extended partition zacinaju 5kou. ps: inac si stastny ze ti este nepoprehadzoval poradie particii. to urobily windows mne a zuril som. cdrom pokazena, na floppy som nemal media, windows na ntfs a zrazu mi linux nestartoval. musel som hladat kde mam root, nasiel som ho na /dev/hda8. predtym bol hda5 a windows si z nicoho nic poprehoadzovalo particie. nikto to po nom nechcel, nikto mu to nekazal. grrr.
                        • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: vfat d 07.06.2005 | 21:48
                          willda   Návštevník
                          Nedá se to udělat nějak dodatečně? Mám nainstalovaný Fedora Core 3 a mám malý "komunikační" logický oddíl ve formatu FAT32 (290MB). Jak se to dá připojit nebo co se s tím dá vlastně dělat? A jestli jsem to správně pochopil, tak vfat je vlastně FAT. PS: Možná to zní trochu blbě, ale nějak jsem ty výše uvedené věci asi nepochopil, má chyba.
                          • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: vf 08.06.2005 | 13:57
                            peter golis   Návštevník
                            samozrejme sa to da pripojit. najprv si treba vylistovat oddiel rozdelenia disku aby clovek vedel ako ma mapovane disky: ako root spustit fdisk -l a clovek uvidi danu tabulku. potom moze pripojit disk prikazom mount /dev/hda5 /mnt/vymennik -t vfat pricom: /dev/hda5 je oddiel s FAT adresar /mnt/vymennik musi existovat. a tam najdes obsah daneho disku. PS.: vfat je ovladac suboroveho systemu FAT s rozsirenim dlhych nazvov.
                            • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 08.06.2005 | 14:06
                              dobinko   Návštevník
                              Včera som si to vyriešil nasledovne. zobral som spustacu disketu w98, pustil fdisk, odpalil ten fatkovy disk D, isiel do linuxu, spustil diskdrake, sformatoval som disk d do fatka, nastavil pribojny bod, potvrdil, napisalo mi že nejaké hda sa zmeni na hdax, a dalsi hday, sa zmeni na hda.. a že potrebujem reštart PC. tak som reštartoval, a zrazu nešlo pustit linux. No samozremjme ked mi hda zmenilo na iny hda (hda6 na hda7) kde bol na hda6 Linux FS. Teda init si nepomohol. Takže som ostal v nemom úžase. Ale teraz mi to je všetko smiešne lebo som len nahodil Mandriva boot cd(teda 1cd) a dal upgrade systemu. Pak som spustil system normalne a teraz do fat disku možem zapisovat, čítať, ale hlavne pripojiť ho správne. Ty fakt som dobrý...možno existovalo lepšie riešenie ale takto som neprišiel o žiadne dáta, a spravil som čo bolo mojim cielom. Dakujem.....ps fdisk-l funguje ako root u mna a ukazuje už disk fat ako hda5. Vdaka..
                              • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 08.06.2005 | 14:08
                                dobinko   Návštevník
                                teda prišiel som akurát o dáta na disku D ktoré som odpalil, ale tie som si predtý zálohoval takže som vedel do čoho idem.
                                • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 08.06.2005 | 16:21
                                  peter golis   Návštevník
                                  pohoda. ak to staci takto, tak nie je co riesit.
                                  • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 08.06.2005 | 17:03
                                    willda   Návštevník
                                    Výborné, funguje to excelentne. Moc díky za radu.
                                    • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 09.06.2005 | 16:56
                                      dobinko   Návštevník
                                      Mimochodom Peter, som "štastný" že mi to poprehadzovalo. Smiem vedieť ako si to vyriešil ty?
                                      • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 09.06.2005 | 18:11
                                        peter golis   Návštevník
                                        ty si mal moznost nastartovat z startovacieho media (boot z instalacneho cd) a dat recowery. ja som to stastie nemal (diskety neboli k dispozicii a cdrom bola pokazena), tak som to robil metodou pokus omyl. boot manager ma moznost zadavat startovacie parametre jadru. postupne som zadaval linux root=/dev/hdaX kde X som hladal z rozsahu 1 az nekonecno. chytil sa niekde okolo osmicky, potom som prepisal zodpovedajuce konfiguraky (/etc/ - fstab, lilo.conf - grub nepouzivam) a spustil lilo. to bolo vsetko. ale tie nervy co som pritom mal ... no skoda reci.
                                        • Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re 09.06.2005 | 18:14
                                          dobinko   Návštevník
                                          Dik, toto je ako sa zdá tiež lahké riešenie, avšak som o nom nevedel. super dik moc.