Re: Strange case of vanishing disk
On 06/03/12 20:59, Kaya Saman wrote: this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. [...] ___ One thing I can think of is to disconnect the questionable disk from the RAID controller card and connect it directly to the motherboard. Then you'd know whether the fault is with the hard drive or the RAID controller. PSU = power supply unit? 180 watts seems very little, I didn't know any modern system could run on so little. I thought the minimum would be around 400 watts, and this would not allow for a powerful gaming graphics card. Maybe you need to replace the power supply with something having more watts, but make sure it will physically fit. Tom Thanks for the response! Here's some more info that I managed to dig up: Jun 4 02:39:19 Zeta-Ray root: ZFS: vdev I/O failure, zpool=ZFS_POOL_2 path=/dev/ad4 offset=270336 size=8192 error=6 Jun 4 02:39:19 Zeta-Ray kernel: ata2: port is not ready (timeout 15000ms) tfd = 00ff Jun 4 02:39:19 Zeta-Ray kernel: ata2: hardware reset timeout Jun 4 02:39:19 Zeta-Ray kernel: unknown: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269091394 Yeah, 180 Watts is what comes with the chassis as it's an external power supply. Additionally the system is a Mini-ITX so that would account for less power usage however, in this case I think it might be the PSU that's simply not providing enough power. I will definitely try sticking the downed disk into the motherboard controller directly as that will tell me if the disk is the issue or not. If the problem is actually insufficient power, this won't tell you a thing. You'll have to isolate the power supply as not being a problem before anything else will be relevant. If you swap the two new disks, and the one now on the card fails, it's probably not a disk problem. But you still can't tell if its the card or insufficient power. If you can sideline the two original disks and run, it's probably power. But I'd guess you're oversubscribed in that department. It should be relatively easy to estimate as mfg specs for cpu + mobo + disks is readily available. Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/04/2012 04:42 AM, Zane C. B-H. wrote: On Mon, 04 Jun 2012 02:06:57 +0100 Kaya Samankayasa...@gmail.com wrote: Hi, this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. The strange thing with this is that I recently installed the 4TB disks and they're brand new. One disk connected to the system board works fine and shows up as online and on one of the channels using atacontrol list. The other disk is connected to a Startech.com Jmicron based 2x SATA RAID controller card. The disk connected to the controller card is having issues. At first the drive wouldn't be seen by the system then after a while all of a sudden it was there. No reboots, no io scans nothing it just appeared. After blasting it with IO for a few days the disk has now vanished again. I had this error in dmesg for a while: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=113337535 I have tried to use pciconf -lbvv to show the connected interfaces and the JMICRON comes up fine: atapci0@pci0:2:0:0:class=0x010400 card=0x2366197b chip=0x2366197b rev=0x02 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'JMicron JMB366 AHCI/IDE Controller (JMB36X)' class = mass storage subclass = RAID bar [10] = type I/O Port, range 32, base 0xd040, size 8, enabled bar [14] = type I/O Port, range 32, base 0xd030, size 4, enabled bar [18] = type I/O Port, range 32, base 0xd020, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xd010, size 4, enabled bar [20] = type I/O Port, range 32, base 0xd000, size 16, enabled bar [24] = type Memory, range 32, base 0xd051, size 8192, enabled So why isn't the disk? I reckon as stated at the beginning that either the 180Watt PSU inside the system isn't enough or the controller is just really poor?? Could anyone suggest anything to look into, I'm sure I've covered all the bases but just incase there is something else I can do with this one?? Greetings, It looks like you are using the default ATA drive with that. I would suggest trying the AHCI driver and see if that works better. kldload ahci ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I've just tried this and lost my whole system. My boot disk is not labeled to work with ahci as it just has standard formatting on there. Need to remove the ahci_load=YES from /boot/loader.conf file now. Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/04/2012 08:34 AM, Gary Aitken wrote: On 06/03/12 20:59, Kaya Saman wrote: this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. [...] ___ One thing I can think of is to disconnect the questionable disk from the RAID controller card and connect it directly to the motherboard. Then you'd know whether the fault is with the hard drive or the RAID controller. PSU = power supply unit? 180 watts seems very little, I didn't know any modern system could run on so little. I thought the minimum would be around 400 watts, and this would not allow for a powerful gaming graphics card. Maybe you need to replace the power supply with something having more watts, but make sure it will physically fit. Tom Thanks for the response! Here's some more info that I managed to dig up: Jun 4 02:39:19 Zeta-Ray root: ZFS: vdev I/O failure, zpool=ZFS_POOL_2 path=/dev/ad4 offset=270336 size=8192 error=6 Jun 4 02:39:19 Zeta-Ray kernel: ata2: port is not ready (timeout 15000ms) tfd = 00ff Jun 4 02:39:19 Zeta-Ray kernel: ata2: hardware reset timeout Jun 4 02:39:19 Zeta-Ray kernel: unknown: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269091394 Yeah, 180 Watts is what comes with the chassis as it's an external power supply. Additionally the system is a Mini-ITX so that would account for less power usage however, in this case I think it might be the PSU that's simply not providing enough power. I will definitely try sticking the downed disk into the motherboard controller directly as that will tell me if the disk is the issue or not. If the problem is actually insufficient power, this won't tell you a thing. You'll have to isolate the power supply as not being a problem before anything else will be relevant. If you swap the two new disks, and the one now on the card fails, it's probably not a disk problem. But you still can't tell if its the card or insufficient power. If you can sideline the two original disks and run, it's probably power. But I'd guess you're oversubscribed in that department. It should be relatively easy to estimate as mfg specs for cpu + mobo + disks is readily available. Gary Yeah, this is really odd! I just offlined the system and took a look at the BIOS. The hard disk controller was set to ATA NATIVE, I attempted changing to AHCI and the system failed to boot thereafter. Booting into my rescue CD of FreeSBIE, with AHCI enabled only showed ad4 (the troubled disk) to be registering. Switching the setting back I managed to see all disk including ad4 from SBIE. I fixed the /boot/loader.conf file by commenting out ahci_load=YES and vuala done! The system booted and the ZPOOL jumped back into life: # zpool status pool: ZFS_POOL_1 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM ZFS_POOL_1 ONLINE 0 0 0 ad13 ONLINE 0 0 0 ad15 ONLINE 0 0 0 errors: No known data errors pool: ZFS_POOL_2 state: ONLINE scrub: scrub stopped after 307445734561825857h27m with 0 errors on Mon Jun 4 16:24:10 2012 config: NAMESTATE READ WRITE CKSUM ZFS_POOL_2 ONLINE 0 0 0 ad14 ONLINE 0 0 0 ad4 ONLINE 0 0 0 errors: No known data errors Here's the weird part now; I had to stop the SCRUB as the READ_DMA retrying errors came up again?? I have just swapped disks infact and ad4 seems to be playing up again :-( ad4 of course being assigned any disk that's on the controller. I am not sure of what to make of this? Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/04/2012 08:34 AM, Gary Aitken wrote: On 06/03/12 20:59, Kaya Saman wrote: this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. [...] ___ One thing I can think of is to disconnect the questionable disk from the RAID controller card and connect it directly to the motherboard. Then you'd know whether the fault is with the hard drive or the RAID controller. PSU = power supply unit? 180 watts seems very little, I didn't know any modern system could run on so little. I thought the minimum would be around 400 watts, and this would not allow for a powerful gaming graphics card. Maybe you need to replace the power supply with something having more watts, but make sure it will physically fit. Tom Thanks for the response! Here's some more info that I managed to dig up: Jun 4 02:39:19 Zeta-Ray root: ZFS: vdev I/O failure, zpool=ZFS_POOL_2 path=/dev/ad4 offset=270336 size=8192 error=6 Jun 4 02:39:19 Zeta-Ray kernel: ata2: port is not ready (timeout 15000ms) tfd = 00ff Jun 4 02:39:19 Zeta-Ray kernel: ata2: hardware reset timeout Jun 4 02:39:19 Zeta-Ray kernel: unknown: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269091394 Yeah, 180 Watts is what comes with the chassis as it's an external power supply. Additionally the system is a Mini-ITX so that would account for less power usage however, in this case I think it might be the PSU that's simply not providing enough power. I will definitely try sticking the downed disk into the motherboard controller directly as that will tell me if the disk is the issue or not. If the problem is actually insufficient power, this won't tell you a thing. You'll have to isolate the power supply as not being a problem before anything else will be relevant. If you swap the two new disks, and the one now on the card fails, it's probably not a disk problem. But you still can't tell if its the card or insufficient power. If you can sideline the two original disks and run, it's probably power. But I'd guess you're oversubscribed in that department. It should be relatively easy to estimate as mfg specs for cpu + mobo + disks is readily available. Gary More digging yields this: zpool iostat -v -- - - - - - - ZFS_POOL_2 527G 6.74T 0 0 3.18K 1.39K ad4431G 3.20T 0 0 1.55K678 ad14 95.6G 3.53T 0 0 1.63K740 -- - - - - - - There is not much bandwidth being used. the disk is fine! The bandwidth gets a little more and the disk starts timing out: -- - - - - - - ZFS_POOL_2 527G 6.74T 0 0 19.0K 12.8K ad4431G 3.20T 0 0 17.3K 5.97K ad14 95.6G 3.53T 0 0 1.72K 6.81K -- - - - - - - I'm pretty sure it's the Strartech.com controller in the system!! Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Strange case of vanishing disk
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Kaya Saman Sent: 04 June 2012 02:07 To: freebsd-questions@freebsd.org Subject: Strange case of vanishing disk Hi, this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. The strange thing with this is that I recently installed the 4TB disks and they're brand new. One disk connected to the system board works fine and shows up as online and on one of the channels using atacontrol list. The other disk is connected to a Startech.com Jmicron based 2x SATA RAID controller card. The disk connected to the controller card is having issues. At first the drive wouldn't be seen by the system then after a while all of a sudden it was there. No reboots, no io scans nothing it just appeared. After blasting it with IO for a few days the disk has now vanished again. I had this error in dmesg for a while: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=113337535 I have tried to use pciconf -lbvv to show the connected interfaces and the JMICRON comes up fine: atapci0@pci0:2:0:0:class=0x010400 card=0x2366197b chip=0x2366197b rev=0x02 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'JMicron JMB366 AHCI/IDE Controller (JMB36X)' class = mass storage subclass = RAID bar [10] = type I/O Port, range 32, base 0xd040, size 8, enabled bar [14] = type I/O Port, range 32, base 0xd030, size 4, enabled bar [18] = type I/O Port, range 32, base 0xd020, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xd010, size 4, enabled bar [20] = type I/O Port, range 32, base 0xd000, size 16, enabled bar [24] = type Memory, range 32, base 0xd051, size 8192, enabled So why isn't the disk? I reckon as stated at the beginning that either the 180Watt PSU inside the system isn't enough or the controller is just really poor?? Could anyone suggest anything to look into, I'm sure I've covered all the bases but just incase there is something else I can do with this one?? Thanks. Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I have had a similar issue on a 3 machines before and in each case the cause was slightly different, on one updating the motherboard BIOS updated the AHCI microcode and the problem went away, another it was the power supply that was a little under powered and in the third which was much more odd was a faulty ram socket on the motherboard, in that case I had initially thought it was the on board sata controller that was the issue so I tried a new 6 port sata controller but the behaviour was the same, so I know it sounds strange but run memtest and see if throws up an errors. Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Strange case of vanishing disk
I reckon as stated at the beginning that either the 180Watt PSU inside the system isn't enough or the controller is just really poor?? well i got through the same. changing PSU, forced a seller to replace my motherboard (got NEW, not the same - checked), checked all cables, even changing disks. used separate JMicron (as yours) based PCIe controllers, and builtin SATA ports on motherboard. things happened randomly. Checked if chipset isn't overheating on board - it wasn't. Then i just got worried and got some money to buy new (low end model) of Dell Poweredge. Things now works with onboard controller, with addon JMicron PCIe (yes the same cards), with any cables and all disks i tried before including those i considered faulty. What i think is that it is not controllers fault not disk faults or not even CPU/memory/chipset fault but bad motherboard electrical design of some motherboard. Possibly because of just different pattern of operation under windoze most clients don't have such a problem and motherboard are continued to be cheaply produced. As formerly failing JMicron controllers are working fine on Dell server proves that it isn't FreeBSD fault too. Could anyone suggest anything to look into, I'm sure I've covered all the bases but just incase there is something else I can do with this one?? Change the motherboard to DIFFERENT. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
I just offlined the system and took a look at the BIOS. The hard disk controller was set to ATA NATIVE, I attempted changing to AHCI and the system failed to boot thereafter. do you have ahci and ada drivers compiled in? Booting into my rescue CD of FreeSBIE, with AHCI enabled only showed ad4 (the troubled disk) to be registering. showing up some, but not all disks after rebooting is quite common to the problem i described. POWERING OFF (by disconnecting electricity, not by power button), waiting a minute, and powering on fixes the problem for some time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/04/2012 06:26 PM, Wojciech Puchar wrote: I just offlined the system and took a look at the BIOS. The hard disk controller was set to ATA NATIVE, I attempted changing to AHCI and the system failed to boot thereafter. do you have ahci and ada drivers compiled in? Booting into my rescue CD of FreeSBIE, with AHCI enabled only showed ad4 (the troubled disk) to be registering. showing up some, but not all disks after rebooting is quite common to the problem i described. POWERING OFF (by disconnecting electricity, not by power button), waiting a minute, and powering on fixes the problem for some time. Thanks Wojciech for the responses! It could be the motherboard; it's an Intel Core2Quad machine! I am looking at alternatives like Portwell: http://www.portwell.nl/products/WADE-8011.html http://www.portwell.nl/products/WADE-8012.html which are Xeon and i7 based system boards respectively and also industrial meaning that they are better designed then consumer desktop style boards. It will be interesting to test once my new rackmount chassis comes along with a 400Watt PSU where the system will then go and see what happens from there.. This system has been up for 3+ years before running 3x disks; one SSD and 2x 2TB drives in a ZFS pool. I only have 4GB RAM in here which may be an issue since I am also using round 5x Jails and 2x Apache Tomcat and 2x Postgresql databases inside to host separate instances of Xwiki - yep Java eats RAM for breakfast, lunch, and dinner :-) - will soon be migrating this stuff off the box but not for now as need some ca$h first ;-) Will wait for my new chassis then see what happens! Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On Mon, 04 Jun 2012 12:20:13 +0100 Kaya Saman kayasa...@gmail.com wrote: On 06/04/2012 04:42 AM, Zane C. B-H. wrote: On Mon, 04 Jun 2012 02:06:57 +0100 Kaya Samankayasa...@gmail.com wrote: snip I've just tried this and lost my whole system. My boot disk is not labeled to work with ahci as it just has standard formatting on there. Need to remove the ahci_load=YES from /boot/loader.conf file now. Ack, my apologies. Forgot about that. Yeah, you will need to do it from the loader prompt if you want to test it. Unless you are booting off of gmirror or have /etc/fstab configured with something else that will automatically be found, you will have a problem. But from the loader prompt it should be... load /boot/kernel/ahci.kp show rootdev If rootdev shows any thing other than shows boot device as ad, rewrite it as ada, using the set command. See loader(8). This will get it to boot, although it will error and drop to single user mode as /etc/fstab contains the old stuff. Just manually mount everything and continue. At this point it should be up and running and able to test it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/05/2012 12:50 AM, Zane C. B-H. wrote: On Mon, 04 Jun 2012 12:20:13 +0100 Kaya Samankayasa...@gmail.com wrote: On 06/04/2012 04:42 AM, Zane C. B-H. wrote: On Mon, 04 Jun 2012 02:06:57 +0100 Kaya Samankayasa...@gmail.com wrote: snip I've just tried this and lost my whole system. My boot disk is not labeled to work with ahci as it just has standard formatting on there. Need to remove the ahci_load=YES from /boot/loader.conf file now. Ack, my apologies. Forgot about that. Yeah, you will need to do it from the loader prompt if you want to test it. Unless you are booting off of gmirror or have /etc/fstab configured with something else that will automatically be found, you will have a problem. But from the loader prompt it should be... load /boot/kernel/ahci.kp show rootdev If rootdev shows any thing other than shows boot device as ad, rewrite it as ada, using the set command. See loader(8). This will get it to boot, although it will error and drop to single user mode as /etc/fstab contains the old stuff. Just manually mount everything and continue. At this point it should be up and running and able to test it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Thanks for the information! I had a small issue at the bootloader prompt, my USB keyboard didn't work as in it seems the kernel modules weren't loaded in order for the keys to function. Not sure how to get round that one :-) Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On Tue, 05 Jun 2012 01:03:59 +0100, Kaya Saman wrote: I had a small issue at the bootloader prompt, my USB keyboard didn't work as in it seems the kernel modules weren't loaded in order for the keys to function. Not sure how to get round that one :-) Check the BIOS settings: Sometimes you can enable USB keyboard legacy so it will also work at the lower levels of interactivity. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On 06/05/2012 01:09 AM, Polytropon wrote: On Tue, 05 Jun 2012 01:03:59 +0100, Kaya Saman wrote: I had a small issue at the bootloader prompt, my USB keyboard didn't work as in it seems the kernel modules weren't loaded in order for the keys to function. Not sure how to get round that one :-) Check the BIOS settings: Sometimes you can enable USB keyboard legacy so it will also work at the lower levels of interactivity. Did that! Enabled USB legacy support - didn't work. At the time was Google'ing the issue too however nobody really had an answer all that was suggested was the load the keyboard modules, but how can one do that with access to system. Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. The strange thing with this is that I recently installed the 4TB disks and they're brand new. One disk connected to the system board works fine and shows up as online and on one of the channels using atacontrol list. The other disk is connected to a Startech.com Jmicron based 2x SATA RAID controller card. The disk connected to the controller card is having issues. At first the drive wouldn't be seen by the system then after a while all of a sudden it was there. No reboots, no io scans nothing it just appeared. After blasting it with IO for a few days the disk has now vanished again. I had this error in dmesg for a while: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=113337535 I have tried to use pciconf -lbvv to show the connected interfaces and the JMICRON comes up fine: atapci0@pci0:2:0:0:class=0x010400 card=0x2366197b chip=0x2366197b rev=0x02 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'JMicron JMB366 AHCI/IDE Controller (JMB36X)' class = mass storage subclass = RAID bar [10] = type I/O Port, range 32, base 0xd040, size 8, enabled bar [14] = type I/O Port, range 32, base 0xd030, size 4, enabled bar [18] = type I/O Port, range 32, base 0xd020, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xd010, size 4, enabled bar [20] = type I/O Port, range 32, base 0xd000, size 16, enabled bar [24] = type Memory, range 32, base 0xd051, size 8192, enabled So why isn't the disk? I reckon as stated at the beginning that either the 180Watt PSU inside the system isn't enough or the controller is just really poor?? Could anyone suggest anything to look into, I'm sure I've covered all the bases but just incase there is something else I can do with this one?? Thanks. Kaya ___ One thing I can think of is to disconnect the questionable disk from the RAID controller card and connect it directly to the motherboard. Then you'd know whether the fault is with the hard drive or the RAID controller. PSU = power supply unit? 180 watts seems very little, I didn't know any modern system could run on so little. I thought the minimum would be around 400 watts, and this would not allow for a powerful gaming graphics card. Maybe you need to replace the power supply with something having more watts, but make sure it will physically fit. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. [...] ___ One thing I can think of is to disconnect the questionable disk from the RAID controller card and connect it directly to the motherboard. Then you'd know whether the fault is with the hard drive or the RAID controller. PSU = power supply unit? 180 watts seems very little, I didn't know any modern system could run on so little. I thought the minimum would be around 400 watts, and this would not allow for a powerful gaming graphics card. Maybe you need to replace the power supply with something having more watts, but make sure it will physically fit. Tom Thanks for the response! Here's some more info that I managed to dig up: Jun 4 02:39:19 Zeta-Ray root: ZFS: vdev I/O failure, zpool=ZFS_POOL_2 path=/dev/ad4 offset=270336 size=8192 error=6 Jun 4 02:39:19 Zeta-Ray kernel: ata2: port is not ready (timeout 15000ms) tfd = 00ff Jun 4 02:39:19 Zeta-Ray kernel: ata2: hardware reset timeout Jun 4 02:39:19 Zeta-Ray kernel: unknown: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269091394 Yeah, 180 Watts is what comes with the chassis as it's an external power supply. Additionally the system is a Mini-ITX so that would account for less power usage however, in this case I think it might be the PSU that's simply not providing enough power. I will definitely try sticking the downed disk into the motherboard controller directly as that will tell me if the disk is the issue or not. I'm also thinking to eliminate the issue of using external controller to just get a new system board that 6x SATA connectors on it instead of 4 as per my board. Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Strange case of vanishing disk
On Mon, 04 Jun 2012 02:06:57 +0100 Kaya Saman kayasa...@gmail.com wrote: Hi, this is a very strange issue but I guess will either be related to 2 things, PSU not being powerful enough or disk controller simply being crap. Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS server with 2x 2TB disks and 2x4TB disks as storage - all spread out over 2 ZFS storage pools. Additionally I am running the root file system on a 40GB SSD. The strange thing with this is that I recently installed the 4TB disks and they're brand new. One disk connected to the system board works fine and shows up as online and on one of the channels using atacontrol list. The other disk is connected to a Startech.com Jmicron based 2x SATA RAID controller card. The disk connected to the controller card is having issues. At first the drive wouldn't be seen by the system then after a while all of a sudden it was there. No reboots, no io scans nothing it just appeared. After blasting it with IO for a few days the disk has now vanished again. I had this error in dmesg for a while: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=113337535 I have tried to use pciconf -lbvv to show the connected interfaces and the JMICRON comes up fine: atapci0@pci0:2:0:0:class=0x010400 card=0x2366197b chip=0x2366197b rev=0x02 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'JMicron JMB366 AHCI/IDE Controller (JMB36X)' class = mass storage subclass = RAID bar [10] = type I/O Port, range 32, base 0xd040, size 8, enabled bar [14] = type I/O Port, range 32, base 0xd030, size 4, enabled bar [18] = type I/O Port, range 32, base 0xd020, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xd010, size 4, enabled bar [20] = type I/O Port, range 32, base 0xd000, size 16, enabled bar [24] = type Memory, range 32, base 0xd051, size 8192, enabled So why isn't the disk? I reckon as stated at the beginning that either the 180Watt PSU inside the system isn't enough or the controller is just really poor?? Could anyone suggest anything to look into, I'm sure I've covered all the bases but just incase there is something else I can do with this one?? Greetings, It looks like you are using the default ATA drive with that. I would suggest trying the AHCI driver and see if that works better. kldload ahci ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
