NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Tue Jul 01, 2025 6:10 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 8 posts ] 
Author Message
PostPosted: Thu Jul 27, 2006 7:39 pm 
Offline

Joined: Wed Oct 26, 2005 8:42 am
Posts: 135
Location: Arkansas, USA
A straightforward change from v1.5 USB to v2.01 USB. First NASLite would no longer boot from the USB drive as a SuperFloppy, I had to change it to Bootable Partition then it booted. But a few hard drive error messages appeared in the SysLog (that follows), and althoug SMART test is set to ON, and the HTML page shows it ON, the Storage page shows all drives SMART disabled.
---
Jul 27 23:29:24 syslog.info syslogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
Jul 27 23:29:24 daemon.info init: ^MStarting pid 2237, console /dev/null: '/sbin/klogd'
Jul 27 23:29:24 user.notice kernel: klogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
Jul 27 23:29:24 user.warn kernel: Linux version 2.4.32.NASLite (root@TZT) (gcc version 3.3.6) #2 Sat Jul 22 04:08:30 UTC 2006
Jul 27 23:29:24 user.info kernel: BIOS-provided physical RAM map:
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 0000000000100000 - 000000001dff0000 (usable)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 000000001dff0000 - 000000001dff3000 (ACPI NVS)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 000000001dff3000 - 000000001e000000 (ACPI data)
Jul 27 23:29:24 user.warn kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 27 23:29:24 user.notice kernel: 479MB LOWMEM available.
Jul 27 23:29:24 user.warn kernel: On node 0 totalpages: 122864
Jul 27 23:29:24 user.warn kernel: zone(0): 4096 pages.
Jul 27 23:29:24 user.warn kernel: zone(1): 118768 pages.
Jul 27 23:29:24 user.warn kernel: zone(2): 0 pages.
Jul 27 23:29:24 user.info kernel: ACPI: RSDP (v000 VIAP4M ) @ 0x000f6c20
Jul 27 23:29:24 user.info kernel: ACPI: RSDT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff3040
Jul 27 23:29:24 user.info kernel: ACPI: FADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff30c0
Jul 27 23:29:24 user.info kernel: ACPI: MADT (v001 VIAP4M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff8000
Jul 27 23:29:24 user.info kernel: ACPI: DSDT (v001 VIAP4M AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
Jul 27 23:29:24 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
Jul 27 23:29:24 user.info kernel: Initializing CPU#0
Jul 27 23:29:24 user.warn kernel: Detected 2933.592 MHz processor.
Jul 27 23:29:24 user.warn kernel: Console: colour VGA+ 80x25
Jul 27 23:29:24 user.warn kernel: Calibrating delay loop. 5845.81 BogoMIPS
Jul 27 23:29:24 user.info kernel: Memory: 480448k/491456k available (2187k kernel code, 10620k reserved, 734k data, 536k init, 0k highmem)
Jul 27 23:29:24 user.info kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 23:29:24 user.info kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Jul 27 23:29:24 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Jul 27 23:29:24 user.info kernel: Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Jul 27 23:29:24 user.warn kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Jul 27 23:29:24 user.info kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Jul 27 23:29:24 user.info kernel: CPU: L2 cache: 256K
Jul 27 23:29:24 user.debug kernel: CPU: After generic, caps: bfebfbff 00000000 00000000 00000000
Jul 27 23:29:24 user.debug kernel: CPU: Common caps: bfebfbff 00000000 00000000 00000000
Jul 27 23:29:24 user.warn kernel: CPU: Intel(R) Celeron(R) CPU 2.93GHz stepping 01
Jul 27 23:29:24 user.info kernel: Enabling fast FPU save and restore. done.
Jul 27 23:29:24 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
Jul 27 23:29:24 user.info kernel: Checking 'hlt' instruction. OK.
Jul 27 23:29:24 user.info kernel: Checking for popad bug. OK.
Jul 27 23:29:24 user.warn kernel: ACPI: IRQ9 SCI: Level Trigger.
Jul 27 23:29:24 user.warn kernel: POSIX conformance testing by UNIFIX
Jul 27 23:29:24 user.info kernel: ACPI: Subsystem revision 20040326
Jul 27 23:29:24 user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbbc0, last bus=1
Jul 27 23:29:24 user.info kernel: PCI: Using configuration type 1
Jul 27 23:29:24 user.info kernel: ACPI: Interpreter enabled
Jul 27 23:29:24 user.info kernel: ACPI: Using PIC for interrupt routing
Jul 27 23:29:24 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S4 S5)
Jul 27 23:29:24 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Jul 27 23:29:24 user.warn kernel: PCI: Probing PCI hardware (bus 00)
Jul 27 23:29:24 user.info kernel: PCI: Via IRQ fixup
Jul 27 23:29:24 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12)
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 11 12) *5
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 *10 11 12)
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [ALKA] (IRQs *20), disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [ALKB] (IRQs *21)
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [ALKC] (IRQs *22), disabled.
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled.
Jul 27 23:29:24 user.info kernel: PCI: Probing PCI hardware
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
Jul 27 23:29:24 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
Jul 27 23:29:24 user.info kernel: PCI: Using ACPI for IRQ routing
Jul 27 23:29:24 user.info kernel: Linux NET4.0 for Linux 2.4
Jul 27 23:29:24 user.info kernel: Based upon Swansea University Computer Society NET3.039
Jul 27 23:29:24 user.warn kernel: Initializing RT netlink socket
Jul 27 23:29:24 user.warn kernel: Starting kswapd
Jul 27 23:29:24 user.info kernel: Journalled Block Device driver loaded
Jul 27 23:29:24 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Jul 27 23:29:24 user.info kernel: devfs: boot_options: 0x1
Jul 27 23:29:24 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jul 27 23:29:24 user.info kernel: ACPI: Power Button (FF) [PWRF]
Jul 27 23:29:24 user.info kernel: ACPI: Fan [FAN] (on)
Jul 27 23:29:24 user.info kernel: ACPI: Processor [CPU0] (supports C1)
Jul 27 23:29:24 user.info kernel: ports C1)
Jul 27 23:29:24 user.info kernel: ACPI: Thermal Zone [THRM] (56 C)
Jul 27 23:29:24 user.warn kernel: pty: 256 Unix98 ptys configured
Jul 27 23:29:24 user.info kernel: Real Time Clock Driver v1.10f
Jul 27 23:29:24 user.warn kernel: floppy0: no floppy controllers found
Jul 27 23:29:24 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Jul 27 23:29:24 user.info kernel: loop: loaded (max 8 devices)
Jul 27 23:29:24 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
Jul 27 23:29:24 user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
Jul 27 23:29:24 user.info kernel: dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96 03:45:15
Jul 27 23:29:24 user.warn kernel: FW Version=$Version$
Jul 27 23:29:24 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
Jul 27 23:29:24 user.info kernel: ThunderLAN driver v1.15
Jul 27 23:29:24 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
Jul 27 23:29:24 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Jul 27 23:29:24 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
Jul 27 23:29:24 user.warn kernel: sk98lin: No adapter found.
Jul 27 23:29:24 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.30.
Jul 27 23:29:24 user.info kernel: r8169 Gigabit Ethernet driver 1.2 loaded
Jul 27 23:29:24 user.debug kernel: eth0: Identified chip type is 'RTL8169s/8110s'.
Jul 27 23:29:24 user.info kernel: eth0: RTL8169 at 0xde808000, 00:0f:b5:8d:68:b0, IRQ 11
Jul 27 23:29:24 user.info kernel: eth0: Auto-negotiation Enabled.
Jul 27 23:29:24 user.info kernel: eth0: 1000Mbps Full-duplex operation.
Jul 27 23:29:24 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Jul 27 23:29:24 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jul 27 23:29:24 user.info kernel: VP_IDE: IDE controller at PCI slot 00:0f.0
Jul 27 23:29:24 user.info kernel: VP_IDE: chipset revision 6
Jul 27 23:29:24 user.info kernel: VP_IDE: not 100% native mode: will probe irqs later
Jul 27 23:29:24 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jul 27 23:29:24 user.info kernel: VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci00:0f.0
Jul 27 23:29:24 user.info kernel: ide0: BM-DMA at 0xe100-0xe107, BIOS settings: hda:DMA, hdb:pio
Jul 27 23:29:24 user.info kernel: ide1: BM-DMA at 0xe108-0xe10f, BIOS settings: hdc:DMA, hdd:DMA
Jul 27 23:29:24 user.warn kernel: hda: ST3200826A, ATA DISK drive
Jul 27 23:29:24 user.warn kernel: blk: queue c048ac00, I/O limit 4095Mb (mask 0xffffffff)
Jul 27 23:29:24 user.warn kernel: hdc: WDC WD2000JB-00GVA0, ATA DISK drive
Jul 27 23:29:24 user.warn kernel: hdd: WDC WD2000JB-00KFA0, ATA DISK drive
Jul 27 23:29:24 user.warn kernel: blk: queue c048b054, I/O limit 4095Mb (mask 0xffffffff)
Jul 27 23:29:24 user.warn kernel: blk: queue c048b190, I/O limit 4095Mb (mask 0xffffffff)
Jul 27 23:29:24 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jul 27 23:29:24 user.warn kernel: ide1 at 0x170-0x177,0x376 on irq 15
Jul 27 23:29:24 user.warn kernel: hda: attached ide-disk driver.
Jul 27 23:29:24 user.warn kernel: hda: host protected area => 1
Jul 27 23:29:24 user.info kernel: hda: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
Jul 27 23:29:24 user.warn kernel: hdc: attached ide-disk driver.
Jul 27 23:29:24 user.warn kernel: hdc: host protected area => 1
Jul 27 23:29:24 user.info kernel: hdc: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
Jul 27 23:29:24 user.warn kernel: hdd: attached ide-disk driver.
Jul 27 23:29:24 user.warn kernel: hdd: host protected area => 1
Jul 27 23:29:24 user.info kernel: hdd: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
Jul 27 23:29:24 user.info kernel: Partition check:
Jul 27 23:29:24 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
Jul 27 23:29:24 user.info kernel: /dev/ide/host0/bus1/target0/lun0: p1
Jul 27 23:29:24 user.info kernel: /dev/ide/host0/bus1/target1/lun0: p1
Jul 27 23:29:24 user.info kernel: SCSI subsystem driver Revision: 1.00
Jul 27 23:29:24 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
Jul 27 23:29:24 user.info kernel: Detecting Adaptec I2O RAID controllers.
Jul 27 23:29:24 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Jul 22 2006 04:09:13)
Jul 27 23:29:24 user.warn kernel: scsi: Detection failed (no card)
Jul 27 23:29:24 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
Jul 27 23:29:24 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
Jul 27 23:29:24 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
Jul 27 23:29:24 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
Jul 27 23:29:24 user.warn kernel: 3w-xxxx: No cards found.
Jul 27 23:29:24 user.debug kernel: libata version 1.11 loaded.
Jul 27 23:29:24 user.info kernel: raw1394: /dev/raw1394 device initialized
Jul 27 23:29:24 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
Jul 27 23:29:24 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Jul 27 23:29:24 user.info kernel: usb.c: registered new driver usbdevfs
Jul 27 23:29:24 user.info kernel: usb.c: registered new driver hub
Jul 27 23:29:24 user.info kernel: ehci_hcd 00:10.4: PCI device 1106:3104
Jul 27 23:29:24 user.info kernel: ehci_hcd 00:10.4: irq 10, pci mem de80c000
Jul 27 23:29:24 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
Jul 27 23:29:24 user.info kernel: ehci_hcd 00:10.4: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
Jul 27 23:29:24 user.info kernel: hub.c: USB hub found
Jul 27 23:29:24 user.info kernel: hub.c: 8 ports detected
Jul 27 23:29:24 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
Jul 27 23:29:24 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe200, IRQ 11
Jul 27 23:29:24 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
Jul 27 23:29:24 user.info kernel: hub.c: USB hub found
Jul 27 23:29:24 user.info kernel: hub.c: 2 ports detected
Jul 27 23:29:24 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe300, IRQ 11
Jul 27 23:29:24 user.info kernel: usb.c: new USB bus registered, assigned bus number 3
Jul 27 23:29:24 user.info kernel: hub.c: USB hub found
Jul 27 23:29:24 user.info kernel: hub.c: 2 ports detected
Jul 27 23:29:24 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe400, IRQ 10
Jul 27 23:29:24 user.info kernel: bus registered, assigned bus number 4
Jul 27 23:29:24 user.info kernel: hub.c: USB hub found
Jul 27 23:29:24 user.info kernel: hub.c: 2 ports detected
Jul 27 23:29:24 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe500, IRQ 10
Jul 27 23:29:24 user.info kernel: usb.c: new USB bus registered, assigned bus number 5
Jul 27 23:29:24 user.info kernel: hub.c: USB hub found
Jul 27 23:29:24 user.info kernel: hub.c: 2 ports detected
Jul 27 23:29:24 user.info kernel: Initializing USB Mass Storage driver.
Jul 27 23:29:24 user.info kernel: usb.c: registered new driver usb-storage
Jul 27 23:29:24 user.info kernel: USB Mass Storage support registered.
Jul 27 23:29:24 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jul 27 23:29:24 user.info kernel: IP Protocols: ICMP, UDP, TCP
Jul 27 23:29:24 user.info kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Jul 27 23:29:24 user.info kernel: TCP: Hash tables configured (established 32768 bind 65536)
Jul 27 23:29:24 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jul 27 23:29:24 user.notice kernel: RAMDISK: NASLite file system found at block 0
Jul 27 23:29:24 user.warn kernel: <6>hub.c: new USB device 00:10.4-4, assigned address 2
Jul 27 23:29:24 user.warn kernel: <6>scsi1 : SCSI emulation for USB Mass Storage devices
Jul 27 23:29:24 user.warn kernel: Vendor: LEXAR Model: JUMPDRIVE Rev: 3000
Jul 27 23:29:24 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
Jul 27 23:29:24 user.warn kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
Jul 27 23:29:24 user.warn kernel: .SCSI device sda: 252928 512-byte hdwr sectors (129 MB)
Jul 27 23:29:24 user.warn kernel: sda: Write Protect is off
Jul 27 23:29:24 user.info kernel: /dev/scsi/host1/bus0/target0/lun0:. p1
Jul 27 23:29:24 user.debug kernel: WARNING: USB Mass Storage data integrity not assured
Jul 27 23:29:24 user.debug kernel: USB Mass Storage device found at 2
Jul 27 23:29:24 user.warn kernel: <6>Freeing initrd memory: 1602k freed
Jul 27 23:29:24 user.warn kernel: VFS: Mounted root (ext2 filesystem).
Jul 27 23:29:24 user.info kernel: Mounted devfs on /dev
Jul 27 23:29:24 user.info kernel: Freeing unused kernel memory: 536k freed
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.info kernel: kjournald starting. Commit interval 5 seconds
Jul 27 23:29:24 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
Jul 27 23:29:24 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 27 23:29:24 user.info kernel: kjournald starting. Commit interval 5 seconds
Jul 27 23:29:24 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
Jul 27 23:29:24 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 27 23:29:24 user.info kernel: kjournald starting. Commit interval 5 seconds
Jul 27 23:29:24 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,65), internal journal
Jul 27 23:29:24 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:29:24 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:30:01 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:30:01 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:30:01 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:30:01 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:30:01 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:30:01 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:31:01 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:31:01 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:31:01 user.warn kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:31:01 user.warn kernel: hdc: drive_cmd: error=0x04 { DriveStatusError }
Jul 27 23:31:01 user.warn kernel: hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jul 27 23:31:01 user.warn kernel: hdd: drive_cmd: error=0x04 { DriveStatusError }
---
Any ideas?


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 7:58 pm 
Offline

Joined: Sun Jul 09, 2006 10:26 am
Posts: 428
Location: UK
The drive does not recognise some commands sent to it. I got some on a older drive I am running.

Edit: further reading.

http://www.captain.at/howto-linux-drive ... serror.php


Last edited by gaiden on Thu Jul 27, 2006 8:09 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 8:06 pm 
Offline

Joined: Wed Oct 26, 2005 8:42 am
Posts: 135
Location: Arkansas, USA
This is the conflicting SMART information I am getting (this is all new since v2.01):
=== START OF INFORMATION SECTION ===
Device Model: ST3200826A
Serial Number: 3ND24X28
Firmware Version: 3.03
User Capacity: 200,049,647,616 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Jul 28 00:00:01 2006 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument 'on' to enable it.
---
Yet NASLite shows SMART set to ON ????


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 8:42 pm 
Offline

Joined: Wed Oct 26, 2005 8:42 am
Posts: 135
Location: Arkansas, USA
I just took the server back to v1.5 ... no errors reported, no SMART test problems, SMART enabled on all drives, and working ... what could be different between v1.5 and v2.01 that would cause the conflicting reporting and SMART status ???


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 8:48 pm 
Offline

Joined: Sun Jul 09, 2006 10:26 am
Posts: 428
Location: UK
mmm, been reading about this for the last 20 mins. what happens if you perfrom a smart test? in v2.1.


http://www.seagate.com/support/disc/man ... 008_pm.pdf
page 34..


http://www.captain.at/howto-linux-smart ... artctl.php


still looking for answers


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 8:51 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Grumpa wrote:
This is the conflicting SMART information I am getting (this is all new since v2.01):
=== START OF INFORMATION SECTION ===
Device Model: ST3200826A
Serial Number: 3ND24X28
Firmware Version: 3.03
User Capacity: 200,049,647,616 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Jul 28 00:00:01 2006 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument 'on' to enable it.
---
Yet NASLite shows SMART set to ON ????


SMART needs to be enabled in the drive itself. The NASLite option simply enables or disables the utility to check the drive. SMART needs to be enabled in the drive BIOS.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jul 27, 2006 9:02 pm 
Offline

Joined: Wed Oct 26, 2005 8:42 am
Posts: 135
Location: Arkansas, USA
OK ... enable SMART in drive Bios ... just how does a Windows XP guy do that? AND why does v1.5 show the same drives as SMART enabled and testing?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Aug 11, 2006 3:20 pm 
Offline

Joined: Fri Aug 11, 2006 11:14 am
Posts: 1
Location: McLean
Grumpa wrote:
I just took the server back to v1.5 ... no errors reported, no SMART test problems, SMART enabled on all drives, and working ... what could be different between v1.5 and v2.01 that would cause the conflicting reporting and SMART status ???

Hi,

Doesn't answer the Q, but on a practical note, I have turned SMART (Self Monitoring Analysis & Reporting Technology) back on with this command:

C:\Archives\bin> smartctl -s on -T verypermissive -a /dev/hda

SYNTAX NOTES:
1. Case sensitive
2. the parameters must go before the device spec
3. the help file shows yes/no booleans as set with an equal sign, but the equals sign won't parse so say -s on instead of -s=on

T is the tolerance parameter.

This of course is Bruce Allen's smart control program from http://smartmontools.sourceforge.net/

Thanks for your post. I get drives from eBay, from sellers who are probably clueless about SMART, not maliciously turning off monitoring. So it is interesting that some environments cause SMART monitoring to shut down. Not very helpful for "court of last resort" monitoring firmware, is it?
--jerry-VA


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 8 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Bing [Bot] and 13 guests


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 post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group