NASLite Network Attached Storage

I definitively changed my NAS Hardware (M/B & CPU) trying to give a solution to my problems : I chamged from my NVidia/AMD platform to an Asus LGA775 Intel based Motherboard and cheap Celeron 430 CPU ... obviously my Boot Flash and my SATA HDDs remained the same ones (I only had to change my Unlock Code, of course).
Everything seems to work well now but I took a look at NASLite Log and I found some Warnings :

# May 28 18:45:41 [4] Driver 'sd' needs updating - please use bus_type methods
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Write Protect is off
# May 28 18:45:41 [1] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
# May 28 18:45:41 [2] sda:
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Write Protect is off
# May 28 18:45:41 [1] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
# May 28 18:45:41 [4] sda1
# May 28 18:45:41 [2] sdb:
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 28 18:45:41 [4] sdb1
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Attached SCSI disk
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:07 [2] ATL1E 0000:01:00.0: ATL1E: eth0 NIC Link is Up<1000 Mbps Full Duplex>
# May 28 18:46:18 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:18 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:18 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:22 [2] kjournald starting. Commit interval 5 seconds
# May 28 18:46:22 [2] EXT3 FS on sda1, internal journal
# May 28 18:46:22 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 28 18:46:24 [2] kjournald starting. Commit interval 5 seconds
# May 28 18:46:24 [2] EXT3 FS on sdb1, internal journal
# May 28 18:46:24 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 28 18:46:47 [2] Adding 1048568k swap on /export/Disk-1/_NL_SWAP/VRAM. Priority:-1 extents:266 across:1068316k

Can anyone or can you explain me those messages ??

Michele.

Is the drive mounted and accessible? If so I would not worry about it. The log is simply telling you that there are issues with the drivers for the drive interface controller. At least that is my guess. YMMV.

Mike

Thank you Mike !!
The two disk are mounted & accessible so I basically have no problems : I only noticed that one of my previous configs, the one with an Intel Mini-ITX Board, seemed to work better but it could had been an impression of mine.
YMMV .. what is this ?? Could it literally mean "Your mileage may vary" but it is often used in forum talk meaning that "your results will vary" ??
Michele.

Did you benchmark with tests the performance of the old machine on the Intel Mini-ITX machine? Do the same with your present configuration and compare the numbers. You will need to run a large number of frames to get a real indication of the actual performance.

"Your mileage may vary" is correct.

Mike