JMB363 --> Failing to mount Drive

Status
Not open for further replies.

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
System spec: Dell Optiplex 755 (500GB SATA II HDD, E4400 CPU, 4GB 800Mhz DDR2 RAM, 0 IDE Slots, on-board NIC 1Gbit, JMB363 based IDE/SATA card)
Operating System: FreeNAS x64 9.2.1 (was FreeNAS x64 9.2.0 when testing originally)

Okay, so I started off with a PCI card using the VIA VT6410 chipset (cheap one off ebay). FreeNAS 9.2 found the card but no-matter which drive, IDE cable or PCI port I connected/tried, the drive never showed up. After lots of forum research I tried adding Tunables "ata_load=yes","atavia_load=yes","ataahci_load=yes" etc. and other techniques to no avail...

I SUGGEST AVOIDING THE "VT6410" CARDS ON EBAY... THEY DON'T WORK!!

As I don't have a lot of cash so I tried to find a cheap way around it and spent many hours trying to fix the problem but after a while I decided to get a new PCI card and decided to research the most compatible PCI/PCIe card with IDE support. I eventually found a card on Amazon which uses the JMB363 chipset (supported in FreeBSD)...

When I got it I plugged it in, I found the Dell (stupidly simple and incredibly restricted) BIOS detected the drive. (note: I am using an IDE cable which I know works and also the drive jumper is set to master and is connected to the correct part of the IDE cable). Freenas kernel detects the drive and the webGUI shows the drive in the drive list (I have tried multiple drives which all show up).

Okay... so the problem is that I cant mount the drive using auto import, import or the UFS or ZFS file systems but the drive does show up in the list of 'importable' drives. When importing via the webGUI I get... Error: Unable to GPT format the disk "ada0" at the top of the window and dmesg cycles through a series of "Read_DMA" errors (shown below) which don't stop (I have to hold the power button on the PC to hard reset the PC because I cant manually shut it down).


Code:
kernel: (ada0:ata1:0:1:0): Retrying command
kernel: (ada0:ata1:0:1:0): RES: 51 84 cc 0b 58 00 00 00 00 80 00
kernel: (ada0:ata1:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT )
kernel: (ada0:ata1:0:1:0): CAM status: ATA Status Error
kernel: (ada0:ata1:0:1:0): READ_DMA. ACB: c8 00 cc 0b 58 40 00 00 00 00 80 00
kernel: (ada0:ata1:0:1:0): Retrying command


I have tried to format the disk in windows using the inbuilt utility and NTFS "quick" format and then placing it in the system (I am not importing the NTFS volume so I don't have a problem with NTFS compatibility with freenas).
I have also used the "view disks" tab and then clicked on the drive and clicked "wipe" using quick format which didn't work either.

I have tried changing the BOIS settings from AHCI to Legacy which made my installation revert back to my previous 9.1.1 FreeNAS version and now I can't use the webGUI because I am getting tracebacks and various errors when clicking on anything. I have reverted back to the AHCI mode which didn't work (yet another problem for me to sort!)

Anayway.............

running "pciconf -lvcb" gives me this:
Code:
# pciconf -lvcb
hostb0@pci0:0:0:0:      class=0x060000 card=0x02111028 chip=0x29b08086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82Q35 Express DRAM Controller'
    class      = bridge
    subclass  = HOST-PCI
    cap 09[e0] = vendor (length 11) Intel cap 11 version 1
pcib1@pci0:0:1:0:      class=0x060400 card=0x02111028 chip=0x29b18086 rev=0x02                                    hdr=0x01
    vendor    = 'Intel Corporation'
    device    = '82Q35 Express PCI Express Root Port'
    class      = bridge
    subclass  = PCI-PCI
    cap 0d[88] = PCI Bridge card=0x02111028
    cap 01[80] = powerspec 3  supports D0 D3  current D0
    cap 05[90] = MSI supports 1 message
    cap 10[a0] = PCI-Express 1 root port slot max data 128(128) link x1(x16)
                speed 2.5(2.5) ASPM disabled(L0s)
ecap 0002[100] = VC 1 max VC0
ecap 0005[140] = Root Complex Link Declaration 1
vgapci0@pci0:0:2:0:    class=0x030000 card=0x02111028 chip=0x29b28086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82Q35 Express Integrated Graphics Controller'
    class      = display
    subclass  = VGA
    bar  [10] = type Memory, range 32, base 0xfea00000, size 524288, enabled
    bar  [14] = type I/O Port, range 32, base 0xec90, size  8, enabled
    bar  [18] = type Prefetchable Memory, range 32, base 0xd0000000, size 26843                                  5456, enabled
    bar  [1c] = type Memory, range 32, base 0xfeb00000, size 1048576, enabled
    cap 05[90] = MSI supports 1 message
    cap 01[d0] = powerspec 2  supports D0 D3  current D0
vgapci1@pci0:0:2:1:    class=0x038000 card=0x02111028 chip=0x29b38086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82Q35 Express Integrated Graphics Controller'
    class      = display
    bar  [10] = type Memory, range 32, base 0xfea80000, size 524288, enabled
    cap 01[d0] = powerspec 2  supports D0 D3  current D0
em0@pci0:0:25:0:        class=0x020000 card=0x02111028 chip=0x10bd8086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82566DM-2 Gigabit Network Connection'
    class      = network
    subclass  = ethernet
    bar  [10] = type Memory, range 32, base 0xfe9e0000, size 131072, enabled
    bar  [14] = type Memory, range 32, base 0xfe9db000, size 4096, enabled
    bar  [18] = type I/O Port, range 32, base 0xecc0, size 32, enabled
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 13[e0] = PCI Advanced Features: FLR TP
uhci0@pci0:0:26:0:      class=0x0c0300 card=0x02111028 chip=0x29378086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB UHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [20] = type I/O Port, range 32, base 0xff20, size 32, enabled
    cap 13[50] = PCI Advanced Features: FLR TP
uhci1@pci0:0:26:1:      class=0x0c0300 card=0x02111028 chip=0x29388086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB UHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [20] = type I/O Port, range 32, base 0xff00, size 32, enabled
    cap 13[50] = PCI Advanced Features: FLR TP
ehci0@pci0:0:26:7:      class=0x0c0320 card=0x02111028 chip=0x293c8086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB2 EHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [10] = type Memory, range 32, base 0xfe9d9c00, size 1024, enabled
    cap 01[50] = powerspec 2  supports D0 D3  current D0
    cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14
    cap 13[98] = PCI Advanced Features: FLR TP
none0@pci0:0:27:0:      class=0x040300 card=0x02111028 chip=0x293e8086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) HD Audio Controller'
    class      = multimedia
    subclass  = HDA
    bar  [10] = type Memory, range 64, base 0xfe9dc000, size 16384, enabled
    cap 01[50] = powerspec 2  supports D0 D3  current D0
    cap 05[60] = MSI supports 1 message, 64 bit
    cap 10[70] = PCI-Express 1 root endpoint max data 128(128) FLR link x0(x0)
ecap 0002[100] = VC 1 max VC1
ecap 0005[130] = Root Complex Link Declaration 1
pcib2@pci0:0:28:0:      class=0x060400 card=0x02111028 chip=0x29408086 rev=0x02                                    hdr=0x01
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) PCI Express Port 1'
    class      = bridge
    subclass  = PCI-PCI
    cap 10[40] = PCI-Express 1 root port slot max data 128(128) link x0(x1)
                speed 0.0(2.5) ASPM disabled(L0s)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x02111028
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
ecap 0002[100] = VC 1 max VC0
ecap 0005[180] = Root Complex Link Declaration 1
uhci2@pci0:0:29:0:      class=0x0c0300 card=0x02111028 chip=0x29348086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB UHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [20] = type I/O Port, range 32, base 0xff80, size 32, enabled
    cap 13[50] = PCI Advanced Features: FLR TP
uhci3@pci0:0:29:1:      class=0x0c0300 card=0x02111028 chip=0x29358086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB UHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [20] = type I/O Port, range 32, base 0xff60, size 32, enabled
    cap 13[50] = PCI Advanced Features: FLR TP
uhci4@pci0:0:29:2:      class=0x0c0300 card=0x02111028 chip=0x29368086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB UHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [20] = type I/O Port, range 32, base 0xff40, size 32, enabled
    cap 13[50] = PCI Advanced Features: FLR TP
ehci1@pci0:0:29:7:      class=0x0c0320 card=0x02111028 chip=0x293a8086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) USB2 EHCI Controller'
    class      = serial bus
    subclass  = USB
    bar  [10] = type Memory, range 32, base 0xff980800, size 1024, enabled
    cap 01[50] = powerspec 2  supports D0 D3  current D0
    cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14
    cap 13[98] = PCI Advanced Features: FLR TP
pcib3@pci0:0:30:0:      class=0x060401 card=0x02111028 chip=0x244e8086 rev=0x92                                    hdr=0x01
    vendor    = 'Intel Corporation'
    device    = '82801 PCI Bridge'
    class      = bridge
    subclass  = PCI-PCI
    cap 0d[50] = PCI Bridge card=0x02111028
isab0@pci0:0:31:0:      class=0x060100 card=0x00000000 chip=0x29148086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801IO (ICH9DO) LPC Interface Controller'
    class      = bridge
    subclass  = PCI-ISA
    cap 09[e0] = vendor (length 12) Intel cap 1 version 0
                features: SATA RAID-5, 4 PCI-e x1 slots
ahci1@pci0:0:31:2:      class=0x010601 card=0x02111028 chip=0x29228086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller'
    class      = mass storage
    subclass  = SATA
    bar  [10] = type I/O Port, range 32, base 0xfe00, size  8, enabled
    bar  [14] = type I/O Port, range 32, base 0xfe10, size  4, enabled
    bar  [18] = type I/O Port, range 32, base 0xfe20, size  8, enabled
    bar  [1c] = type I/O Port, range 32, base 0xfe30, size  4, enabled
    bar  [20] = type I/O Port, range 32, base 0xfec0, size 32, enabled
    bar  [24] = type Memory, range 32, base 0xff970000, size 2048, enabled
    cap 05[80] = MSI supports 16 messages enabled with 1 message
    cap 01[70] = powerspec 3  supports D0 D3  current D0
    cap 12[a8] = SATA Index-Data Pair
    cap 13[b0] = PCI Advanced Features: FLR TP
none1@pci0:0:31:3:      class=0x0c0500 card=0x02111028 chip=0x29308086 rev=0x02                                    hdr=0x00
    vendor    = 'Intel Corporation'
    device    = '82801I (ICH9 Family) SMBus Controller'
    class      = serial bus
    subclass  = SMBus
    bar  [10] = type Memory, range 64, base 0xfe9d9b00, size 256, enabled
    bar  [20] = type I/O Port, range 32, base 0xece0, size 32, enabled
atapci0@pci0:1:0:0:    class=0x010400 card=0x2363197b chip=0x2363197b rev=0x03                                    hdr=0x00
    vendor    = 'JMicron Technology Corp.'
    device    = 'JMB362/JMB363 Serial ATA Controller'
    class      = mass storage
    subclass  = RAID
    bar  [10] = type I/O Port, range 32, base 0xdce0, size  8, enabled
    bar  [14] = type I/O Port, range 32, base 0xdcd8, size  4, enabled
    bar  [18] = type I/O Port, range 32, base 0xdce8, size  8, enabled
    bar  [1c] = type I/O Port, range 32, base 0xdcdc, size  4, enabled
    bar  [20] = type I/O Port, range 32, base 0xdcf0, size 16, enabled
    bar  [24] = type Memory, range 32, base 0xfe7fe000, size 8192, enabled
    cap 01[68] = powerspec 2  supports D0 D3  current D0
    cap 10[50] = PCI-Express 1 legacy endpoint IRQ 1 max data 128(128) link x1(x                                  1)
                speed 2.5(2.5) ASPM disabled(L0s) 


I run # fsck_ufs -y /dev/ada0p1 and get:
sck_ufs: /dev/ada0p1: can't read disk label
Unmatched '.

What is quite interesting is that if I run # sysctl kern.geom.debugflags=0x10 I get:

kern.geom.debugflags: 0 -> 16
and I can then create a volume which can be written to via SSH but not via CIFS.. I then restart the NAS and the drive doesn't import (cycling through the Read_DMA error again).
All of the above commands were run before my freenas installation reverted itself back to 9.1.1 FreeNAS.
I am going to try updating the freenas installation to 9.2.1 (if I can get it back to 9.2.0) and also maybe try formatting with a long format on windows and not the "quick" format. I can't think of anything else because I have followed other forums and the things I have tried haven't worked.
I hope someone can help, I can't afford to buy another card!!
Thank you everyone! :)
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
UPDATE:
1. The NEW 9.2.0 freenas installation was bootable via F2 just after BIOS *NOT* F1 as I thought the first time I tried it!! So i think we are back in 9.2.0 now (time to upgrade it to 9.2.1!)
2. I am currently doing a format using windows formatting tool on the drive. I may leave it on an extended format overnight and then do a SMART test in the morning?? to be sure. No other SMART tests show a problem though. Also, I have now converted the disk from GPT to MBR which may help with initialising the disk once formatted?

Problem still isn't fixed as of yet though! Thanks guys! :)
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
2ND UPDATE:

1. I left the drive to do a full wipe in windows. That completed successfully.
2. I checked the SMART data and everything is okay.
3. I updated to FreeNAS 9.2.1 and everything is working great.
4. I tested the JMB363 IDE/SATA Controller in my Windows 7 machine, installed the drivers and then the computer froze-up, so i disconnected the drive and reset the PC.
5. The card seemed okay when no drives were attached.. so i updated the drvers to the latest version and shut the pc down.
4. I updated the JMB363 BIOS to the latest version using FreeDOS on a usb pen drive , tested it in windows 7 (with hdd attached agin) to see if the card would freeze my pc again... it didn't, yay!! copied a large file over.. worked fine.
5. placed it all back in the NAS again, booted up freenas 9.2.1 and made a ZFS volume... Uhh ohh!! "Write_DMA" and "ATA Stutus Error" appear again.
6. So the steps I took were useless and I'm back to square one with no ideas still!!!

It may be worth noting that I thought it was a "Read_DMA" error but actually it is a "Write_DMA" error which I have been encountering. along with "CAM Status: ATA Status Error" and "ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT )"
It gets to 5 retries and then the retries are exhausted and it starts the loop again.

I have seen a few posts on it but none of the fixes work for me so i need some fresh ideas. Please help guys :smile: Cheers
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
3rd UPDATE (still not working with IDE!!):

I JUST can't believe it!! So annoyed that I can't find any card that has even just one IDE slot which is compatible with FreeNAS (or windows 7 x64 bit for that matter!)

Okay, I know I am posting a lot but I just had a good idea... why not try to see if the SATA ports work instead?
So I tried it and guess what!!??
IT WORKED! i could boot an existing sata drive through the sata connector on the pcie card. it also functioned reasonably well (although there seemed the be some latency and some read errors when accessing data).

Now you may think this is good but it isn't for me! I need the IDE ports to work!! and not the SATA's!! grrr
This revelation may actually help in solving the problem as I guess it points more to a driver problem than hardware problems (I have tested multiple drives and cables with the IDE port). Is there anything I can do?
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Bump...
Does anyone know how to fix this?
I kinda forgot to send the card back and I don't think that I can send it back now so it is even more important now for me to fix this.
Please help guys :(
 

eraser

Contributor
Joined
Jan 4, 2013
Messages
147
May I ask why you need IDE ports?

Any IDE Hard Drives you have sitting around are going to be old and slow. Also I don't think IDE supports newer features like AHCI and hotplug.

I wouldn't trust old IDE drives myself. Best to spend the money to purchase some SATA drive replacements.

=-=-=

With that said though, since you are having trouble finding a supported IDE controller... What about converting your old IDE drives to SATA instead? Maybe using something similar to one of these below converters? (I have no idea how well they work myself though)

http://www.newegg.com/Product/Product.aspx?Item=N82E16812206002
http://www.newegg.com/Product/Product.aspx?Item=N82E16812232004
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Firstly, thank you eraser and Yatti420 for replying to my post, I really appreciate your time to respond...

eraser... basically I am trying to keep the costs down as I am a student with no money to spend so if a can use the spare IDE drives lying around it will save money. Also the server isnt mission critical so if they were to die i would just use another old IDE and replace the data (I would mostly use it for data backup). I am also not bothered about the features of AHCI or hot-plugging so that is fine too... I really just need to read the smart data so i can react to hdd failure before data loss.
There are other problems with having separate convertes such as having to power each separate controller and the corresponding hdd which involves the use of a power connector similar to the old floppy drive power (which means getting a SATA to floppy power converter for each hdd as i have a dell computer which has no Molex or floppy drive connectors available!). It also means using one of my SATA connectors on the MB which I would like to use for SATA drives.
The controller card expands my hdd capacity by 2 SATA's and 2 IDE's.

yatti 420... my IDE hdd's show up in the "disk" view but they won't 'initilaize' or imported/formatted and so they are not usable.. I have found that connecting a HDD to the SATA ports on the controller card seems to work perfectly and I can import and use them fine (although the read/write speeds seem to be a problem I think).
Yes there are drivers... FreeBSD supports the JMB36X controllers which is why (after buying a generic card off ebay which was useless) I decided to get this because I thought it would be straight forward. :-/

My diagnosis is that it is either a driver problem, a bug with freenas/freebsd or a conflict with another driver maybe?

Thanks again guys!
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
basically I am trying to keep the costs down as I am a student with no money to spend so if a can use the spare IDE drives lying around it will save money.

That statement alone makes FreeNAS a bad option. FreeNAS isn't designed to work on stuff that is cheap/free. It's meant to be a reliable file server for those willing to pay a reasonable price to do things right. It will hit your pocketbook.. hard. But it's far cheaper than calling Nexenta for a server.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
FreeNAS isn't designed to work on stuff that is cheap/free.

Actually that is exactly how FreeNAS started, it was designed for someone with spare computer parts laying around and to re-purpose them into a home built NAS. Now that was before iXSystems took the FreeNAS title and bent it to their will leaving FreeNAS .7 to re-brand it's name to NAS4Free. I still have no idea what happened there but I watched it happen. The new FreeNAS is more targeted towards people who want to build a good to high performance NAS and saving a lot of money. You can still use old parts but they cannot be too old. If they were state of the art 5 years ago then they should be fine now, but 10 years ago would be pushing it.

So if the OP wants to still use IDE then I'd recommend you try NAS4Free and see how that goes. You may run into the same situation where it will not work properly for your system.
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Hmm okay cyberjock and joeschmuck thank you for both your posts!

I understand that this is made to be a reliable NAS solution for people willing to spend the money... and trust me i am willing, i just cant right now which is kinda sad cus' i can see this is an awesome system when you start to get to grips with it. I initially got the system to achieve faster transfer speeds over the network without breaking the bank on crappy plug n' play NAS with no room for experimentation and expansion... I would love to explore it more and hopefully input ideas for making freenas better because I think it is fantastic, so keeping the system and trying to figure out a way to fix this would be the best option for me i think.

joeschmuck... my only concern with NAS4Free is the migration problems and (maybe) getting used to another system. I have most available PBI's being used i.e. transmission, plex, owncloud, couchpotato etc. along with custom stuff like an apache (LAN landing page) and minecraft server all running and I have no clue how to migrate this stuff especially on the basis that it may not work (although i would probably make a test system first)... sounds like a lot of work? would it be that hard you think?

again, thanks guys for this. :smile:
 

eraser

Contributor
Joined
Jan 4, 2013
Messages
147
Not sure if this is relevant to your situation: https://www.illumos.org/issues/1648 . (Actually most likely not since Illumos is based on OpenSolaris and not FreeBSD)

Hmm, found some FreeBSD bug reports that may or may not be relevant: http://www.freebsd.org/cgi/query-pr-summary.cgi?text=jmicron&closedtoo=on

Does the BIOS of your JMB363 card let you select from a list of different modes? (Something similar to here: http://www.evga.com/support/faq/afmviewfaq.aspx?faqid=58914). If so, suggest trying "AHCI + IDE Mode" or just "IDE Mode" (not RAID mode).

Can you attach the output of 'dmesg'? Wondering what model card is being reported.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
If you want to retain the low cost system I think you will still need to purchase a few SATA hard drives. You could purchase just two drives and set them up as a mirror. It's not free but it may allow you to retain your other hardware and keep your cost as low as possible.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I understand that this is made to be a reliable NAS solution for people willing to spend the money... and trust me i am willing, i just cant right now which is kinda sad cus' i can see this is an awesome system when you start to get to grips with it.

And that's okay.. so long as you recognize the limitations, potential risks, and potential consequences for your choices. For example, many people think they can create a 3 disk RAIDZ1 and later add more disks to the vdev. You can't. So generally speaking, you are better off building your FreeNAS box once, and building it exactly how you want it in the final configuration because many things can't be changed later if you are unhappy. For people that don't recognize the limitations of what they are doing right now, later when they decide to spend money for more disks or what-have-you they realize they really boned themselves by not just spending the money and doing it right the first time.
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Not sure if this is relevant to your situation: https://www.illumos.org/issues/1648 . (Actually most likely not since Illumos is based on OpenSolaris and not FreeBSD)
Actually, to me this bug report seems the most likely to be useful because if you look at the output of "pciconf" you can see it is listed as one device. It slipped my attention as I am relatively new to linux/freebsd and if they are supposed to appear as seperate devices it could be the reason for this problem!!
Code:
atapci0@pci0:1:0:0:    class=0x010400 card=0x2363197b chip=0x2363197b rev=0x03                                    hdr=0x00
vendor    = 'JMicron Technology Corp.'
device    = 'JMB362/JMB363 Serial ATA Controller'
class      = mass storage
subclass  = RAID
bar  [10] = type I/O Port, range 32, base 0xdce0, size  8, enabled
bar  [14] = type I/O Port, range 32, base 0xdcd8, size  4, enabled
bar  [18] = type I/O Port, range 32, base 0xdce8, size  8, enabled
bar  [1c] = type I/O Port, range 32, base 0xdcdc, size  4, enabled
bar  [20] = type I/O Port, range 32, base 0xdcf0, size 16, enabled
bar  [24] = type Memory, range 32, base 0xfe7fe000, size 8192, enabled
cap 01[68] = powerspec 2  supports D0 D3  current D0
cap 10[50] = PCI-Express 1 legacy endpoint IRQ 1 max data 128(128) link x1(x                                  1)
speed 2.5(2.5) ASPM disabled(L0s) 

The problem I have is that firstly the "main" NAS system has no "portsnap" or "pkg" installer installed and I don't kinda trust installing it because there must be a reason for it not being there right? So that means i cant install setpci to modify the pci registers
The second problem is that i have no clue how to convert this [[ setpci -v -s 04:00.0 40.b=b3 41.b=a1 42.b=c2 ]] from opensolaris to work with freenas!?

Hmm... okay, you know that BIOS screenshot link: http://www.evga.com/support/faq/afmviewfaq.aspx?faqid=58914
well I see exactly the same jmicron bios screens as seen in "step 2" of the guide but I have a VERY limited dell motherboard bios and so I guess I could change it to legacy IDE (but i think i may have tried this before and the drives weren't detected).
I also found reference to the ICH9 and the JMB363 card in this post: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/135497 but it also says about the device "not showing" and my disk is showing in freenas so i'm not sure how relevant it is...


also, i will attach the dmesg output later as I will have to shut the NAS down, find and reinstall the card (I thought it wouldn't be able to solve the problem)...

Thank you for your help eraser and also joeschmuck and cyberjock too :smile:
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Okay, I have attached all relevant "dmesg" output:
Code:
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: Length mismatch for 3 range: ec00001 vs ec00000
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xec90-0xec97 mem 0xfea00000-0xfea7ffff,0xd0000000-0xdfffffff,0xfeb00000-0xfebfffff irq 16 at device 2.0 on pci0
agp0: <Intel Q35 SVGA controller> on vgapci0
agp0: aperture size is 256M, detected 6140k stolen memory
vgapci1: <VGA-compatible display> mem 0xfea80000-0xfeafffff at device 2.1 on pci0
em0: <Intel(R) PRO/1000 Network Connection 7.3.8> port 0xecc0-0xecdf mem 0xfe9e0000-0xfe9fffff,0xfe9db000-0xfe9dbfff irq 21 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:00:00:00:00:ee
uhci0: <Intel 82801I (ICH9) USB controller> port 0xff20-0xff3f irq 16 at device 26.0 on pci0
uhci0: LegSup = 0x2f00
usbus0 on uhci0
uhci1: <Intel 82801I (ICH9) USB controller> port 0xff00-0xff1f irq 17 at device 26.1 on pci0
uhci1: LegSup = 0x2f00
usbus1 on uhci1
ehci0: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xfe9d9c00-0xfe9d9fff irq 22 at device 26.7 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
atapci0: <JMicron JMB363 UDMA133 controller> port 0xdce0-0xdce7,0xdcd8-0xdcdb,0xdce8-0xdcef,0xdcdc-0xdcdf,0xdcf0-0xdcff mem 0xfe6fe000-0xfe6fffff irq 16 at device 0.0 on pci2
ahci0: <JMicron JMB363 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x1<NOFORCE>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ata2: <ATA channel> at channel 0 on atapci0
uhci2: <Intel 82801I (ICH9) USB controller> port 0xff80-0xff9f irq 23 at device 29.0 on pci0
usbus3 on uhci2
uhci3: <Intel 82801I (ICH9) USB controller> port 0xff60-0xff7f irq 17 at device 29.1 on pci0
usbus4 on uhci3
uhci4: <Intel 82801I (ICH9) USB controller> port 0xff40-0xff5f irq 18 at device 29.2 on pci0
usbus5 on uhci4
ehci1: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xff980800-0xff980bff irq 23 at device 29.7 on pci0
usbus6: EHCI version 1.0
usbus6 on ehci1
pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib3
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci1: <Intel ICH9 AHCI SATA controller> port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem 0xff970000-0xff9707ff irq 18 at device 31.2 on pci0
ahci1: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported
ahcich2: <AHCI channel> at channel 0 on ahci1
ahcich3: <AHCI channel> at channel 1 on ahci1
ahcich4: <AHCI channel> at channel 2 on ahci1
ahcich5: <AHCI channel> at channel 3 on ahci1
ahcich7: <AHCI channel> at channel 5 on ahci1
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ichwd0 on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
ichwd0 at port 0x830-0x837,0x860-0x87f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcb7ff,0xcb800-0xcdfff,0xce000-0xcffff,0xd0000-0xd27ff,0xd2800-0xd3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
DUMMYNET 0xfffffe0002782000 with IPv6 initialized (100409)
load_dn_sched dn_sched RR loaded
load_dn_sched dn_sched WF2Q+ loaded
load_dn_sched dn_sched FIFO loaded
load_dn_sched dn_sched PRIO loaded
load_dn_sched dn_sched QFQ loaded
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen3.1: <Intel> at usbus3
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen4.1: <Intel> at usbus4
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
ugen5.1: <Intel> at usbus5
uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
ugen6.1: <Intel> at usbus6
uhub6: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
ada0 at ahcich2 bus 0 scbus3 target 0 lun 0
ada0: <ST3500312CS SC13> ATA-8 SATA 1.x device
ada0: Serial Number 5VV20QDY
ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad10
lapic1: Forcing LINT1 to edge trigger
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1995028260 Hz quality 1000
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
Root mount waiting for: usbus6 usbus2
Root mount waiting for: usbus6 usbus2
Root mount waiting for: usbus6 usbus2
uhub2: 6 ports with 6 removable, self powered
uhub6: 6 ports with 6 removable, self powered
Root mount waiting for: usbus6 usbus2
ugen2.2: <Cypress Semiconductor> at usbus2
umass0: <Cypress Semiconductor USB2.0 Storage Device, class 0/0, rev 2.00/0.01, addr 2> on usbus2
umass0:  SCSI over Bulk-Only; quirks = 0x4100
umass0:9:0:-1: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <ST325082 0A 0000> Fixed Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 238474MB (488395055 512 byte sectors: 255H 63S/T 30401C)
da0: quirks=0x2<NO_6_BYTE>
ugen5.2: <vendor 0x04d9> at usbus5
ukbd0: <vendor 0x04d9 USB Keyboard, class 0/0, rev 1.10/3.10, addr 2> on usbus5
kbd2 at ukbd0
uhid0: <vendor 0x04d9 USB Keyboard, class 0/0, rev 1.10/3.10, addr 2> on usbus5
Root mount waiting for: usbus6
ugen6.2: <vendor 0x0457> at usbus6
umass1: <vendor 0x0457 USB Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2> on usbus6
umass1:  SCSI over Bulk-Only; quirks = 0x0100
umass1:10:1:-1: Attached to scbus10
Trying to mount root from ufs:/dev/ufs/FreeNASs1a [ro]...
mountroot: waiting for device /dev/ufs/FreeNASs1a ...
da1 at umass-sim1 bus 1 scbus10 target 0 lun 0
da1: <PEAK III Flash Drive 0.00> Removable Direct Access SCSI-2 device
da1: Serial Number 5126b7b174f270
da1: 40.000MB/s transfers
da1: 1968MB (4030464 512 byte sectors: 255H 63S/T 250C)
da1: quirks=0x2<NO_6_BYTE>
GEOM_RAID5: Module loaded, version 1.1.20130907.44 (rev 5c6d2a159411)
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
GEOM_ELI: Device ada0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: software
GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: software

I don't know why but this line pci0: <multimedia, HDA> at device 27.0 (no driver attached) seems to be ringing alarm bells for me?
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
I would use Nas4Free aswell with older hardware..
 

eraser

Contributor
Joined
Jan 4, 2013
Messages
147
Your dmesg output does appear to indicate that both the SATA and the PATA(IDE) ports on your JMB363 controller are being recognized at boot. Looks like your IDE drive (if connected) should show up as 'ata2'. Did you have an IDE drive connected during this boot?

atapci0: <JMicron JMB363 UDMA133 controller> port 0xdce0-0xdce7,0xdcd8-0xdcdb,0xdce8-0xdcef,0xdcdc-0xdcdf,0xdcf0-0xdcff mem 0xfe6fe000-0xfe6fffff irq 16 at device 0.0 on pci2
ahci0: <JMicron JMB363 AHCI SATA controller> at channel -1 on atapci0
ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported
ahci0: quirks=0x1<NOFORCE>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ata2: <ATA channel> at channel 0 on atapci0

=-=-=

Hmm, did you already upgrade your option ROM to 1.07.24 ?

ftp://driver.jmicron.com.tw/SATA_Controller/Option_ROM/

=-=-=

I believe you can use 'pciconf' instead of 'setpci' to change PCI configuration registers and it is available in FreeNAS.

I found this page documenting what the 0x40, 0x41, 0x42, 0x43 configuration registers are for [ http://blog.stuffedcow.net/2012/08/jmicron-jmb36x-add-on-card-ahci-mode/ ], but I think all you really need to know is to set them to the values listed in https://www.illumos.org/issues/1648 .

I did find this output showing a JMB363 chipset (card=0x2363197b) showing up as a SATA and an IDE device instead of just a RAID device like yours, so maybe if you poke the correct registers on your card it will do the same. (not sure how to make it survive a power cycle though or how you can re-scan your PCI bus after making register changes).

http://forums.freebsd.org/viewtopic.php?f=32&t=35666&p=196554

=-=-=

Wow, it turns out that I have spent several hours researching this issue and have realized that I can't spare any more time. Sorry...

In an age where you can buy two used 250 GB SATA drives for $30 off ebay [1] and a used 750 GB SATA drive for $20 [2], I don't think trying to reuse two old IDE drives is worth spending more time troubleshooting. If it is too late to return the card, at the very least you can use the SATA connectors off the JMB363 adapter for additional SATA disks.

[1] http://www.ebay.com/itm/Lot-of-2-Ma...150-3-5-Desktop-HDD-Hard-Drives-/380852597033
[2] http://www.ebay.com/itm/SEAGATE-ST3750640NS-9BL148-269-SATA-750GB-DESKTOP-HARD-DRIVE-/201046966660

Best of luck on your FreeNAS journey!
 

Revilo

Dabbler
Joined
Oct 15, 2013
Messages
25
Thank you soo much for putting the time in to the problem eraser! I really appreciate it :smile:

No I didn't have a drive attached at boot but I know from previous boots it does detect properly and functions fine. It just doesn't format and mount the drive.
So the dmesg output shows 4 channels (2 SATA and 2 PATA)? It looks to me like there is only one ATA channel!? I'm not too good at reading dmesg output.
=-=-=
Yes I did update the rom to the latest but for some reason the version it displayed after was an earlier version than the original one but it didn't make a difference to the functioning of the device so I gave up trying to diagnose the problem.
=-=-=
I will give changing the registers a go I think. Bit worried about messing it up though so I will have to look at how it can be reversed if I do change it and it stops functioning.
=-=-=
You are completely right about buying new drives. When I can invest in some I definitely will, I just wish I hadn't invested in a controller which doesn't work with FreeNAS (despite spending countless hours finding a suitable solution).
I would like to try and sort this problem because I know from forums that other people have used these cards and have had problems with the IDE side of the card too. I just wish there was a PCIe card that could support a couple of PATA drives :-/

Again, thank you for your help!
 
Status
Not open for further replies.
Top