[SOLVED] Drive labels mixed after new hard drive install

[MrEd]

I recently installed NAS4 Free 9.1.0.1 - Sandstorm (revision 273)
I had gotten everything setup and working (aside from fuppes being goofy)

I installed a 4 port sata card, looks just like this.
http://www.amazon.com/Port-SATA-Serial- ... s+J+Parker

The sata card has a silicon image 3114 chip.

I formatted a brand new drive Western Digital WD10EURX 1TB sata
I had to format it on a windows machine, the only place the drive would show up....
I then reformatted it on the nas to the ufs system like my other drives, but in order to do this
I had to unmount AND unplug a couple of drives to do this because this particular drive seemed to swap places
with a couple others. The new drive is not raided, it's just an extra drive.

In the end after remounting the old drives and connecting the WD10EURX to the sata card,
everything boots up and can connect to all the shares and the have the right descriptions,
but the Device models are swapped on some of the drives. See pic

If I remember correctly they swapped without using the raid card as well, but I was
trying different things quickly to get it to work so I could be mistaken.

I guess my question is, is this a weird bug with this drive model and is there a way to fix it?

If anymore information is needed, just let me know.
I'm still a beginner, be gentle.

[raulfg3]

please check if is the same problem described here: viewtopic.php?f=78&t=1055&start=10

[alexey123]

MrEd
I has some, see viewtopic.php?p=4915#p4915
Pls attach /var/run/dmesg.boot file.

You have problem after install SATA pci -controller?
System priority is ISA --> PCI (and pci-express) --> IDE (and onboard sata.), this is not NAS4free, this is ALL systems.
May be you need reconfigure your drives. AS viewtopic.php?p=4879#p4879

[daoyama]

Currently, raw disk is not supported, but SoftwareRAID and encrypted disks can be reload with "Clear and import" from r306's Disk Management.

[MrEd]

@ alexey123
Here is the dmesg.boot file. in case it's helpfull.

I've also noticed in this version I've gone to, the log
has a section in it that says "Buggy and fixed firmware report same version number!"

Code: Select all

Sep 23 19:31:27 	aim 	nmbd[2600]: [2012/09/23 19:31:27.446462, 0] nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Sep 23 19:31:20 	aim 	smartd[2649]: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks
Sep 23 19:31:20 	aim 	smartd[2649]: http://knowledge.seagate.com/articles/en_US/FAQ/223571en
Sep 23 19:31:20 	aim 	smartd[2649]: See the following web pages for details:
Sep 23 19:31:20 	aim 	smartd[2649]: Buggy and fixed firmware report same version number!
Sep 23 19:31:20 	aim 	smartd[2649]: ****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Sep 23 19:31:20 	aim 	smartd[2649]: drive may result in data loss due to a firmware bug.
Sep 23 19:31:20 	aim 	smartd[2649]: Device: /dev/ada2, WARNING: Using smartmontools or hdparm with this
Sep 23 19:31:19 	aim 	nmbd[2600]: become_domain_master_browser_bcast: querying subnet 192.168.1.144 for domain master browser on workgroup AIM
Sep 23 19:31:19 	aim 	nmbd[2600]: [2012/09/23 19:31:19.369919, 0] nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Sep 23 19:31:19 	aim 	nmbd[2600]: Attempting to become domain master browser on workgroup AIM on subnet 192.168.1.144
Sep 23 19:31:19 	aim 	nmbd[2600]: become_domain_master_browser_bcast:
Sep 23 19:31:19 	aim 	nmbd[2600]: [2012/09/23 19:31:19.369467, 0] nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Sep 23 19:31:18 	aim 	proftpd[2398]: 192.168.1.144 - ProFTPD 1.3.4b (maint) (built Sun Sep 9 2012 02:13:08 JST) standalone mode STARTUP
Sep 23 19:31:16 	aim 	root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub0

Just in case it's relevant, I didn't do anything to the sata card other than stick it
in the pci slot in the machine.
I'll update to 306 as soon as I can.

[raulfg3]

Sorry my answer is not related exactly about your problem.

I only want to notice that in old FreeNAS Forums SIL 3114 is mark as "problematic" card, is a cheap controller, but is SATA 150 and limit your actuall disk that are SATA 300 .

Perhaps, if you try other SATA 300, you can benefit of a great trhoughput.

Code: Select all

ada0: <WDC WD10EURX-73FH1Y0 01.01A01> ATA-8 SATA 3.x device
ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad8
ada1 at ata0 bus 0 scbus4 target 1 lun 0
ada1: <Maxtor 6Y120P0 YAR41BW0> ATA-7 device
ada1: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
ada1: 117246MB (240121728 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad1
ada2 at ata6 bus 0 scbus5 target 0 lun 0
ada2: <SAMSUNG HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada2: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad12
ada3 at ata6 bus 0 scbus5 target 1 lun 0
ada3: <Hitachi HDS721010CLA332 JP4OA3EA> ATA-8 SATA 2.x device
ada3: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad13

[alexey123]

MrEd, your log have lines with links

ada0: Previously was known as ad8
ada1: Previously was known as ad1
ada2: Previously was known as ad12
ada3: Previously was known as ad13

This links says about any changes in system, any reconnects disks after install.
But! May be webgui have any code, which use adaN and adN names. Or have problem into regular extensions.
I have no other explanation - my server behaves exactly like yours, but I have a plug and play PCI raid controller and I do not see solutions

[MrEd]

Ok I finally got a chance to upgrade to 9.1.0.1 - Sandstorm (revision 323)

It may have been Revision 320 that fixed it but I could be wrong.

NAS4Free Changelog
http://nas4free.svn.sourceforge.net/vie ... /?view=log

after the upgrade I got this




Everyone is now where they should be after reimporting...All fixed