NASLite Network Attached Storage

This problem continues with v2.02 USB. Four Hitachi 250GB PATA drives. Disk-0 is shown, but the problem exists with all four disks.

Here is the Telnet config page for Drive 0, showing that SMART is turned on in drive config:



Here is the Server Status page, showing that SMART is enabled on all drives (but note than no temperature info is shown):



And yet here is the Server Storage Disk-0 details page, showing that SMART is available but disabled:

What MB have you got?

You didn't ask me, but I have new MSI and VIA MoBo's and 4 hard drives (Western Digital, Seagate) that have the same problem with SMART in v2. The same drives and MoBo's using v1.5 work fine (SMART).

AOpen i865Gm-IL, Intel 865G chipset, 4 x PATA drives.

Hi Grumpa,

Could you provide the same screenshots as lmoseley with your drives running v1 and v2?


Thanks.

re: screenshots ... will do. I won't be able to post them until tomorrow.

v2 uses smartctl version 5.36 and v1.5 uses smartctl version 5.0-45

Could it be changes in the spec regarding the command set for the ide spec.

Go figure. I went back to v1.5 to take advantage of SMART working on the server's drives. I just went forward to v2.02 to take screenshots, and viola! SMART is reporting on all drives. Now please note this sort of miracle happened once before (I have a old post on working with Seagate techs) ... I ran Seatools, and the Western Digital equivalent on a Windows desktop on the drives v2.01 wouldn't show SMART working. After all tests completed - TOK - SMART started reporting on the drives after booting up v2.01 ... then a week later in v2.02 it all went away ... and now it's back. ( ? ) So Ralph, no screenshots until it happens again.

SMART in v2.02 was updated along with the kernel to support SMART on SATA drives.

Well, if the version of "smartctl" is the thing that changed, maybe that is where the problem likes...

I have the identical problem.

Motherboard is AOpen AX6BC with the most recent BIOS update: 2.59
CPU is Pentium III 450 MHz
NIC is Netgear FA310TX REV-D2
Two identical Seagate Barracuda 7200.8 PATA drives

Much like the standards of USB, example why one usb device will boot and another not, and or onboard usb will not see a device yet a pci card will.

http://en.wikipedia.org/wiki/Self-Monit ... Technology

Standards and implementation
Compaq pioneered S.M.A.R.T., but most major hard-drive and motherboard vendors now support it to some extent. Many motherboards will display a warning message when a disk drive approaches failure. Although an industry standard amongst most major hard drive manufacturers,[2] there are some remaining issues and much proprietary "secret knowledge" held by individual manufacturers as to their specific approach. As a result, S.M.A.R.T. is not always implemented correctly on many computer platforms due to the absence of industry-wide software & hardware standards for S.M.A.R.T. data interchange.

From a legal perspective, the term "S.M.A.R.T." refers only to a signaling method between internal disk drive electromechanical sensors and the host computer — thus a disk drive manufacturer could include a sensor for just one physical attribute and then advertise the product as S.M.A.R.T. compatible. For example, a drive manufacturer might claim to support S.M.A.R.T. but not include a temperature sensor, which the customer might reasonably expect to be present since reliability typically is the inverse of temperature, in which case temperature would be a crucial predictor of failure.

Some S.M.A.R.T.-enabled motherboards and related software may not communicate with certain S.M.A.R.T.-capable drives, depending on the type of interface. Few external drives connected via USB and Firewire correctly send S.M.A.R.T. data over those interfaces. With so many ways to connect a hard drive (e.g. SCSI, Fibre Channel, ATA, SATA, SAS, SSA) it's difficult to predict whether S.M.A.R.T. reports will function correctly.

Even on hard drives and interfaces that support it, S.M.A.R.T. data may not be reported correctly to the computer's operating system. Some disk controllers can duplicate all write operations on a secondary "backup" drive in real-time. This feature is known as "RAID mirroring". However, many programs which are designed to analyze changes in drive behavior and relay S.M.A.R.T. alerts to the operator do not function when a computer system is configured for RAID support, usually because under normal RAID array operational conditions, the computer may not be permitted to 'see' (or directly access) individual physical drives, but only logical volumes, by the RAID array subsystem.

On the Windows platform, many programs designed to monitor and report S.M.A.R.T. information will only function under an administrator account. At present S.M.A.R.T. is implemented individually by manufacturers, and while some aspects are standardized for compatibility, others are not.

One of the other fundamental problems with S.M.A.R.T is that it slows performance and for this reason it is disabled by default in many motherboard BIOSes.


Attributes
Each drive manufacturer defines a set of attributes and selects threshold values which attributes should not go below under normal operation. Attribute values can range from 1 to 253 (1 representing the worst case and 253 representing the best). Depending on the manufacturer, a value of 100 or 200 will often be chosen as the "normal" value. Manufacturers that have supported one or more S.M.A.R.T. attributes in various products include: Samsung, Seagate, IBM (Hitachi), Fujitsu, Maxtor, Western Digital. These manufacturers do not necessarily agree on precise attribute definitions and measurement units; therefore the following list should be regarded as a general reference only. Note that the attribute values are always mapped to the range of 1 to 253 in a way that means higher values are better. For example, the "Reallocated Sectors Count" attribute value decreases as the number of reallocated sectors increases. In this case, the attribute's raw value will often indicate the actual number of sectors that were reallocated, although vendors are in no way required to adhere to this convention.

I have a 3WARE Escalade 7006-2 RAID controller on order. It purports to be S.M.A.R.T. savvy, and even has SMTP capability to send an email as an alert.

I would expect any RAID controller to mask all physical attributes of the underlying volumes from the outside world, so I assume that the NASLite S.M.A.R.T. capability would no longer serve any purpose.

I will report my findings when I get it.

I have no problems with my machine and smart showing the temps. Both drives are Seagates and the MB just some generic thing I found with a processor laying around at a show for $5.00.

System Message Log:

* Aug 26 15:46:58 syslog.info syslogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
* Aug 26 15:46:58 daemon.info init: ^MStarting pid 1877, console /dev/null: '/sbin/klogd'
* Aug 26 15:46:58 user.notice kernel: klogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
* Aug 26 15:46:58 user.warn kernel: Linux version 2.4.31.NASLite (root@TZT) (gcc version 3.3.6) #1 Sat Jul 8 04:34:40 UTC 2006
* Aug 26 15:46:58 user.info kernel: BIOS-provided physical RAM map:
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
* Aug 26 15:46:58 user.warn kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* Aug 26 15:46:58 user.notice kernel: 511MB LOWMEM available.
* Aug 26 15:46:58 user.warn kernel: On node 0 totalpages: 131056
* Aug 26 15:46:58 user.warn kernel: zone(0): 4096 pages.
* Aug 26 15:46:58 user.warn kernel: zone(1): 126960 pages.
* Aug 26 15:46:58 user.warn kernel: zone(2): 0 pages.
* Aug 26 15:46:58 user.notice kernel: ACPI disabled because your bios is from 2000 and too old
* Aug 26 15:46:58 user.notice kernel: You can enable it with acpi=force
* Aug 26 15:46:58 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
* Aug 26 15:46:58 user.info kernel: Initializing CPU#0
* Aug 26 15:46:58 user.warn kernel: Detected 801.829 MHz processor.
* Aug 26 15:46:58 user.warn kernel: Calibrating delay loop. 1599.07 BogoMIPS
* Aug 26 15:46:58 user.info kernel: Memory: 512900k/524224k available (2169k kernel code, 10940k reserved, 727k data, 536k init, 0k highmem)
* Aug 26 15:46:58 user.info kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
* Aug 26 15:46:58 user.info kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
* Aug 26 15:46:58 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Aug 26 15:46:58 user.info kernel: Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
* Aug 26 15:46:58 user.warn kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
* Aug 26 15:46:58 user.info kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
* Aug 26 15:46:58 user.info kernel: CPU: L2 Cache: 256K (64 bytes/line)
* Aug 26 15:46:58 user.debug kernel: CPU: After generic, caps: 0183f9ff c1c7f9ff 00000000 00000000
* Aug 26 15:46:58 user.debug kernel: CPU: Common caps: 0183f9ff c1c7f9ff 00000000 00000000
* Aug 26 15:46:58 user.warn kernel: CPU: AMD Athlon(tm) Processor stepping 02
* Aug 26 15:46:58 user.info kernel: Enabling fast FPU save and restore. done.
* Aug 26 15:46:58 user.info kernel: Checking 'hlt' instruction. OK.
* Aug 26 15:46:58 user.info kernel: Checking for popad bug. OK.
* Aug 26 15:46:58 user.warn kernel: POSIX conformance testing by UNIFIX
* Aug 26 15:46:58 user.info kernel: ACPI: Subsystem revision 20040326
* Aug 26 15:46:58 user.info kernel: ACPI: Interpreter disabled.
* Aug 26 15:46:58 user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=1
* Aug 26 15:46:58 user.info kernel: PCI: Using configuration type 1
* Aug 26 15:46:58 user.info kernel: PCI: Probing PCI hardware
* Aug 26 15:46:58 user.warn kernel: PCI: Probing PCI hardware (bus 00)
* Aug 26 15:46:58 user.warn kernel: Disabling VIA memory write queue (PCI ID 0305, rev 02): [55] 89 & 1f -> 09
* Aug 26 15:46:58 user.info kernel: PCI: Via IRQ fixup
* Aug 26 15:46:58 user.info kernel: PCI: Using IRQ router VIA [1106/0686] at 00:07.0
* Aug 26 15:46:58 user.info kernel: Linux NET4.0 for Linux 2.4
* Aug 26 15:46:58 user.info kernel: Based upon Swansea University Computer Society NET3.039
* Aug 26 15:46:58 user.warn kernel: Initializing RT netlink socket
* Aug 26 15:46:58 user.warn kernel: Starting kswapd
* Aug 26 15:46:58 user.info kernel: Journalled Block Device driver loaded
* Aug 26 15:46:58 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Aug 26 15:46:58 user.info kernel: devfs: boot_options: 0x1
* Aug 26 15:46:58 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Aug 26 15:46:58 user.warn kernel: keyboard: Timeout - AT keyboard not present?(ed)
* Aug 26 15:46:58 user.warn kernel: keyboard: Timeout - AT keyboard not present?(f4)
* Aug 26 15:46:58 user.warn kernel: pty: 256 Unix98 ptys configured
* Aug 26 15:46:58 user.info kernel: Real Time Clock Driver v1.10f
* Aug 26 15:46:58 user.warn kernel: floppy0: no floppy controllers found
* Aug 26 15:46:58 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
* Aug 26 15:46:58 user.info kernel: loop: loaded (max 8 devices)
* Aug 26 15:46:58 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
* Aug 26 15:46:58 user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
* Aug 26 15:46:58 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
* Aug 26 15:46:58 user.warn kernel: FW Version=$Version$
* Aug 26 15:46:58 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Aug 26 15:46:58 user.info kernel: ThunderLAN driver v1.15
* Aug 26 15:46:58 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Aug 26 15:46:58 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Aug 26 15:46:58 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Aug 26 15:46:58 user.info kernel: PCI: Found IRQ 11 for device 00:0d.0
* Aug 26 15:46:58 user.info kernel: PCI: Sharing IRQ 11 with 00:07.2
* Aug 26 15:46:58 user.warn kernel: eth0: ns83820.c: 0x22c: 621a1385, subsystem: 1385:621a
* Aug 26 15:46:58 user.info kernel: eth0: enabling optical transceiver
* Aug 26 15:46:58 user.info kernel: eth0: ns83820 v0.20: DP83820 v1.3: 00:09:5b:22:fd:ae io=0xd1400000 irq=11 f=sg
* Aug 26 15:46:58 user.warn kernel: sk98lin: No adapter found.
* Aug 26 15:46:58 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.30.
* Aug 26 15:46:58 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Aug 26 15:46:58 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Aug 26 15:46:58 user.info kernel: VP_IDE: IDE controller at PCI slot 00:07.1
* Aug 26 15:46:58 user.info kernel: VP_IDE: chipset revision 16
* Aug 26 15:46:58 user.info kernel: VP_IDE: not 100% native mode: will probe irqs later
* Aug 26 15:46:58 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Aug 26 15:46:58 user.info kernel: VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
* Aug 26 15:46:58 user.info kernel: ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
* Aug 26 15:46:58 user.info kernel: ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:DMA
* Aug 26 15:46:58 user.warn kernel: hda: ST3200822A, ATA DISK drive
* Aug 26 15:46:58 user.warn kernel: hdb: ST3300831A, ATA DISK drive
* Aug 26 15:46:58 user.warn kernel: blk: queue c0484c00, I/O limit 4095Mb (mask 0xffffffff)
* Aug 26 15:46:58 user.warn kernel: blk: queue c0484d3c, I/O limit 4095Mb (mask 0xffffffff)
* Aug 26 15:46:58 user.warn kernel: hdd: _NEC NR-7500A, ATAPI CD/DVD-ROM drive
* Aug 26 15:46:58 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Aug 26 15:46:58 user.warn kernel: ide1 at 0x170-0x177,0x376 on irq 15
* Aug 26 15:46:58 user.warn kernel: hda: attached ide-disk driver.
* Aug 26 15:46:58 user.warn kernel: hda: host protected area => 1
* Aug 26 15:46:58 user.info kernel: hda: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(33)
* Aug 26 15:46:58 user.warn kernel: hdb: attached ide-disk driver.
* Aug 26 15:46:58 user.warn kernel: hdb: host protected area => 1
* Aug 26 15:46:58 user.info kernel: hdb: 586072368 sectors (300069 MB) w/8192KiB Cache, CHS=36481/255/63, UDMA(33)
* Aug 26 15:46:58 user.info kernel: Partition check:
* Aug 26 15:46:58 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
* Aug 26 15:46:58 user.info kernel: /dev/ide/host0/bus0/target1/lun0: p1
* Aug 26 15:46:58 user.info kernel: SCSI subsystem driver Revision: 1.00
* Aug 26 15:46:58 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Jul 8 2006 04:48:23)
* Aug 26 15:46:58 user.warn kernel: scsi: Detection failed (no card)
* Aug 26 15:46:58 user.notice kernel: megaraid: v2.10.8.2 (Release Date: Mon Jul 26 12:15:51 EDT 2004)
* Aug 26 15:46:58 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Aug 26 15:46:58 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
* Aug 26 15:46:58 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
* Aug 26 15:46:58 user.warn kernel: 3w-xxxx: No cards found.
* Aug 26 15:46:58 user.debug kernel: libata version 1.10 loaded.
* Aug 26 15:46:58 user.info kernel: raw1394: /dev/raw1394 device initialized
* Aug 26 15:46:58 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
* Aug 26 15:46:58 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Aug 26 15:46:58 user.info kernel: usb.c: registered new driver usbdevfs
* Aug 26 15:46:58 user.info kernel: usb.c: registered new driver hub
* Aug 26 15:46:58 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Aug 26 15:46:58 user.info kernel: PCI: Found IRQ 11 for device 00:07.2
* Aug 26 15:46:58 user.info kernel: PCI: Sharing IRQ 11 with 00:0d.0
* Aug 26 15:46:58 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd400, IRQ 11
* Aug 26 15:46:58 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
* Aug 26 15:46:58 user.info kernel: hub.c: USB hub found
* Aug 26 15:46:58 user.info kernel: hub.c: 2 ports detected
* Aug 26 15:46:58 user.info kernel: Initializing USB Mass Storage driver.
* Aug 26 15:46:58 user.info kernel: usb.c: registered new driver usb-storage
* Aug 26 15:46:58 user.info kernel: USB Mass Storage support registered.
* Aug 26 15:46:58 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
* Aug 26 15:46:58 user.info kernel: IP Protocols: ICMP, UDP, TCP
* Aug 26 15:46:58 user.info kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
* Aug 26 15:46:58 user.info kernel: TCP: Hash tables configured (established 32768 bind 65536)
* Aug 26 15:46:58 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Aug 26 15:46:58 user.notice kernel: RAMDISK: NASLite file system found at block 0
* Aug 26 15:46:58 user.warn kernel: .<6>hub.c: new USB device 00:07.2-2, assigned address 2
* Aug 26 15:46:58 user.info kernel: eth0: link now 1000F mbps, full duplex and up.
* Aug 26 15:46:58 user.warn kernel: .<6>scsi1 : SCSI emulation for USB Mass Storage devices
* Aug 26 15:46:58 user.warn kernel: . Vendor: M-SysT5 Model: Dell Memory Key Rev: 5.04
* Aug 26 15:46:58 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Aug 26 15:46:58 user.warn kernel: .Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
* Aug 26 15:46:58 user.warn kernel: .SCSI device sda: 249599 512-byte hdwr sectors (128 MB)
* Aug 26 15:46:58 user.warn kernel: sda: Write Protect is off
* Aug 26 15:46:58 user.info kernel: /dev/scsi/host1/bus0/target0/lun0:. p1
* Aug 26 15:46:58 user.debug kernel: WARNING: USB Mass Storage data integrity not assured
* Aug 26 15:46:58 user.debug kernel: USB Mass Storage device found at 2
* Aug 26 15:46:58 user.warn kernel: <6>Freeing initrd memory: 1602k freed
* Aug 26 15:46:58 user.warn kernel: VFS: Mounted root (ext2 filesystem).
* Aug 26 15:46:58 user.info kernel: Mounted devfs on /dev
* Aug 26 15:46:58 user.info kernel: Freeing unused kernel memory: 536k freed
* Aug 26 15:46:58 user.warn kernel: Warning: unable to open an initial console.
* Aug 26 15:46:58 user.info kernel: kjournald starting. Commit interval 5 seconds
* Aug 26 15:46:58 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
* Aug 26 15:46:58 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Aug 26 15:46:58 user.info kernel: kjournald starting. Commit interval 5 seconds
* Aug 26 15:46:58 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
* Aug 26 15:46:58 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Aug 27 00:34:32 auth.info login[29510]: root login on `pts/0'

NASLite-2 shows SMART attributes for a given volume, provided the volume is a single storage drive. In a RAID, that is not the case.