March 5, 200719 yr I'm using a kicker disk to kick start loading unRaid and I need to edit the autoexec.bat file and remove a "Press any key to continue..." line I had placed there for testing. Unfortunatly, at home, I have no other machine with a floppy drive attached to it and I am now leary of bringing down my unRaid server because it is now being used by three other PCs as a file server and media server. I need to be able to mount it and use vi to edit the batch file but for some reason, typing "mount /dev/fd0 /mnt/floppy" comes up with the error "mount point /mnt/floppy does not exist". Any help would be greatly appreciated. Thanks! Aaron
March 5, 200719 yr I'm using a kicker disk to kick start loading unRaid and I need to edit the autoexec.bat file and remove a "Press any key to continue..." line I had placed there for testing. Unfortunatly, at home, I have no other machine with a floppy drive attached to it and I am now leary of bringing down my unRaid server because it is now being used by three other PCs as a file server and media server. I need to be able to mount it and use vi to edit the batch file but for some reason, typing "mount /dev/fd0 /mnt/floppy" comes up with the error "mount point /mnt/floppy does not exist". Any help would be greatly appreciated. Thanks! Aaron Easy... create an empty directory /mnt/floppy first. Then retry your mount command. mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy That should do it, although I'm not sure if you also need to specify the file sysytem type for the floppy in the mount command, as it currently has none in the system. Joe L
March 5, 200719 yr You might need to spepcify the file system type on the floppy being mounted mkdir /mnt/floppy mount -t vfat /dev/fd0 /mnt/floppy
March 5, 200719 yr Author Thanks for replying so fast. I tried as you suggested, here's what I get: Tower login: root Linux 2.4.33. root@Tower:~# mkdir /mnt/floppy root@Tower:~# mount -t vfat /dev/fd0 /mnt/floppy mount: /dev/fd0 is not a valid block device root@Tower:~#
March 5, 200719 yr It appears as if the floppy was not detected when your unRaid server booted up, or you typed fd "letter o" instead of fd "numeric zero' Was the floppy drive plugged in when you booted up the server? I've no idea what Tom has done with the floppy driver, but I would have guessed it would still be there... you are doing something nobody else has tried... Joe L.
March 5, 200719 yr Yes, the floppy was plugged in...I use a kicker disk to jump start unRAID. Check the contents of /var/log/dmesg Perhaps the floppy was detected as something else besides /dev/fd0. Perhaps it is fd1? In any case, the boot log may yeild a clue.
March 6, 200719 yr Author Bootlog was a bit clueless to me: root@Tower:/var/log# more dmesg Linux version 2.4.33 (root@Develop) (gcc version 3.3.6) #19 Tue Nov 14 08:28:09 GMT+8 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003ffec000 (usable) BIOS-e820: 000000003ffec000 - 000000003ffef000 (ACPI data) BIOS-e820: 000000003ffef000 - 000000003ffff000 (reserved) BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. On node 0 totalpages: 229376 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 0 pages. ACPI: RSDP (v000 ASUS ) @ 0x000f85f0 ACPI: RSDT (v001 ASUS A7M266-D 0x30303031 MSFT 0x31313031) @ 0x3ffec000 ACPI: FADT (v001 ASUS A7M266-D 0x30303031 MSFT 0x31313031) @ 0x3ffec100 ACPI: BOOT (v001 ASUS A7M266-D 0x30303031 MSFT 0x31313031) @ 0x3ffec040 ACPI: MADT (v001 ASUS A7M266-D 0x30303031 MSFT 0x31313031) @ 0x3ffec080 ACPI: DSDT (v001 ASUS A7M266-D 0x00001000 MSFT 0x0100000b) @ 0x00000000 Kernel command line: initrd=bzroot ramdisk_size=120000 root=/dev/ram0 Initializing CPU#0 Detected 1600.093 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3191.60 BogoMIPS Memory: 879576k/917504k available (1579k kernel code, 37540k reserved, 516k data , 80k init, 0k highmem) Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode cache hash table entries: 65536 (order: 7, 524288 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 65536 (order: 6, 262144 bytes) Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383fbff c1cbfbff 00000000 00000000 CPU: Common caps: 0383fbff c1cbfbff 00000000 00000000 CPU: AMD Athlon MP 1900+ stepping 02 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. ACPI: IRQ9 SCI: Edge set to Level Trigger. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch ([email protected]) mtrr: detected mtrr type: Intel ACPI: Subsystem revision 20040326 PCI: PCI BIOS revision 2.10 entry at 0xf1f30, last bus=2 PCI: Using configuration type 1 ACPI-0165: *** Error: No object was returned from [\_SB_.PCI0.UAR2._STA] (No de ce743f40), AE_NOT_EXIST ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: System [ACPI] (supports S0 S1 S4 S5) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 *12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 *4 5 6 7 9 10 11 12 14 15) ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] PCI: Probing PCI hardware ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 4 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 12 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 PCI: Using ACPI for IRQ routing BIOS failed to enable PCI standards compliance, fixing this error. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd NTFS driver v1.1.22 [Flags: R/O] ACPI: Power Button (FF) [PWRF] ACPI: Sleep Button (FF) [sLPF] ACPI: Processor [CPU0] (supports C1) ACPI: Processor [CPU1] (supports C1) RAMDISK driver initialized: 16 RAM disks of 120000K size 1024 blocksize loop: loaded (max 8 devices) Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD7441: IDE controller at PCI slot 00:07.1 AMD7441: chipset revision 4 AMD7441: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD7441: 00:07.1 (rev 04) UDMA100 controller ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA hda: ST3500841A, ATA DISK drive hdb: ST3500841A, ATA DISK drive hdc: ST3500841A, ATA DISK drive hdd: ST3500641A, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: host protected area => 1 hda: 976773168 sectors (500108 MB) w/8192KiB Cache, CHS=60801/255/63, UDMA(100) hdb: attached ide-disk driver. hdb: host protected area => 1 hdb: 976773168 sectors (500108 MB) w/8192KiB Cache, CHS=60801/255/63, UDMA(100) hdc: attached ide-disk driver. hdc: host protected area => 1 hdc: 976773168 sectors (500108 MB) w/8192KiB Cache, CHS=60801/255/63, UDMA(100) hdd: attached ide-disk driver. hdd: host protected area => 1 hdd: 976773168 sectors (500108 MB) w/16384KiB Cache, CHS=60801/255/63, UDMA(100) Partition check: hda: hda1 hdb: hdb1 hdc: hdc1 hdd: hdd1 SCSI subsystem driver Revision: 1.00 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 usb.c: registered new driver usbdevfs usb.c: registered new driver hub host/uhci.c: USB Universal Host Controller Interface driver v1.1 host/usb-ohci.c: USB OHCI at membase 0xf8806000, IRQ 4 host/usb-ohci.c: usb-02:00.0, Advanced Micro Devices [AMD] AMD-768 [Opus] USB usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 4 ports detected usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <[email protected]> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 hub.c: new USB device 02:00.0-1, assigned address 2 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: LEXAR Model: JD FIREFLY Rev: 3000 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 1014784 512-byte hdwr sectors (520 MB) sda: Write Protect is off sda: sda1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 Freeing initrd memory: 25262k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 80k freed
March 6, 200719 yr As I suspected.. no mention of a floppy at all. I just typed modprobe --list on my server... no floppy driver module exists on the unRaid system What would have been nice is if had listed /lib/modules/2.4.xx/kernel/drivers/block/floppy.o So... find a floppy.o, then insmod floppy.o, then use /dev/fd0. here is one I found, don't know if it will load, but worth a try. http://www.ibiblio.org/pub/historic-linux/distributions/slackware/3.1/modules/2.0.0/block/ another is here http://ftp.riken.go.jp/Linux/slackware/slackware-7.1/modules/2.2.16/block/?C=M;O=D unfortunately, both are compiled with an earlier version of gcc, so neither will load.. You need a more recent one...(or one compiled with the newer compiler) Perhaps you could ask Tom for a floppy.o module... Joe L.
March 6, 200719 yr Author Aack. Gettin' a little too low level for this Texas bumpkin. Guess I'll just take the little thing to work tomorrow and see if I can scrounge a computer that both works and has a floppy. Lol. Thanks for the assist. Hopefully, Tom will indeed put floppy.o in a future release...along with, mayme, an ftp daemon.
March 21, 200719 yr Right, no floppy support was built into the kernel.... If you can find 3 people who want that feature, I'll add it
March 22, 200719 yr Author Right, no floppy support was built into the kernel.... If you can find 3 people who want that feature, I'll add it Time to register two more accounts.
March 22, 200719 yr Right, no floppy support was built into the kernel.... If you can find 3 people who want that feature, I'll add it since I was the one who was trying to assist... I can be number 2... but as an alternative to making the distribution bigger for a small handful of users... How about putting floppy.o as a loadable module on your web-site in the downloads area. anybody getting that involved and needing it will be able to install it. Also... might be VERY handy as an alternate place to copy the syslog that does NOT go away upon reboot. something like "tail -f /var/log/syslog >>/dev/floppy/logfile" (I'm not sure of the actual name of the floppy device, but you get the idea) Joe L.
March 22, 200719 yr OK, added floppy support in 4.0-beta2. --- Regarding modules - not much ram is saved using modules because in unRAID the root file system is mounted on a ram-disk.
March 22, 200719 yr OK, added floppy support in 4.0-beta2. Wow... thanks... I'll bet it gets some use for logging. --- Regarding modules - not much ram is saved using modules because in unRAID the root file system is mounted on a ram-disk. i was thinking of those with smaller flash drives. I was not thinking of ram used. guess the size was not significant. Again, thanks. Joe L.
Archived
This topic is now archived and is closed to further replies.