On Mon, 18 Jun 2012 00:46:55 +0200
Ramon Hofer wrote:
> I'm again having problems with the disks getting kicked out of the
> array :-o
I've already asked this before on the debian list and got an answer.
But I'm not sure if I should do this.
Here's a link to my old problem:
http://lists.debian.
I'm again having problems with the disks getting kicked out of the
array :-o
First of all the old WD green 2TB disk which was marked failed also
makes problems in the Netgear ReadyNas. I will see if I still have
warranty and try to get a new one.
But the other issue scares me a bit ;-)
Here's wh
On Fri, 15 Jun 2012 16:40:56 -0500
Stan Hoeppner wrote:
> Well lets look at this more closely. The disks may not be bad. How
> old are they? Send me your dmesg output:
Sorry I forgot to write the last time: The WD20EARS I have bough
between 14. Dec 2010 and 01. Oct 2011.
Maybe it was also ca
On Fri, 15 Jun 2012 16:40:56 -0500
Stan Hoeppner wrote:
> On 6/15/2012 8:36 AM, Ramon Hofer wrote:
>
> > First of all I tried to set the raid5 with the WD 20EARS and didn't
> > have much luck. They led to fail events when mdadm builds the array.
> > They "worked" in my Netgear NV+ with very low
On Thu, 14 Jun 2012 08:38:27 -0500
Stan Hoeppner wrote:
> On 6/14/2012 4:51 AM, Ramon Hofer wrote:
>
> >> These commands don't match the pastebin. The pastebin shows you
> >> creating a 4 disk RAID5 as /dev/md0.
> >
> > Really :-?
>
> That kind of (wrong) analysis is one of the many outcomes
On 6/14/2012 8:02 AM, Ramon Hofer wrote:
> AF drives are Advanced Format drives with more than 512 bytes per
> sector right?
Correct. Advanced Format is the industry wide name chosen for drives
that have 4096B physical sectors, but present 512B sectors at the
interface level, doing translation i
On 6/14/2012 9:45 AM, Ramon Hofer wrote:
> On Thu, 14 Jun 2012 08:38:27 -0500
> Stan Hoeppner wrote:
>
>> Couldn't hurt. And while you're at it, mount with "inode64" in your
>> fstab immediately after you create the XFS. You were running with
>> inode32, which sticks all the inodes at the front
On Thu, 14 Jun 2012 08:38:27 -0500
Stan Hoeppner wrote:
> Couldn't hurt. And while you're at it, mount with "inode64" in your
> fstab immediately after you create the XFS. You were running with
> inode32, which sticks all the inodes at the front of AG0 causing lots
> of seeks. Inode64 puts fil
On Thu, 14 Jun 2012 03:29:25 -0500
Stan Hoeppner wrote:
> On 6/13/2012 2:22 PM, Ramon Hofer wrote:
> > On Tue, 12 Jun 2012 17:30:43 -0500
> > Stan Hoeppner wrote:
>
> This chain is so long I'm going to liberally snip lots of stuff
> already covered. Hope that's ok.
Sure. Your mail still blew
On 6/13/2012 1:04 PM, Ramon Hofer wrote:
> On Tue, 12 Jun 2012 18:35:57 -0500
> Stan Hoeppner wrote:
>
>>> Hmm, probably I have to create a raid5 with the four empty 2 TB
>>> disks attached to the LSI. Then:
>>>
>>> ~$ mdadm -C /dev/md0 -n1 -l linear /dev/md1
>>
>> WTF?
>
> I also had to add --f
On 6/13/2012 2:22 PM, Ramon Hofer wrote:
> On Tue, 12 Jun 2012 17:30:43 -0500
> Stan Hoeppner wrote:
This chain is so long I'm going to liberally snip lots of stuff already
covered. Hope that's ok.
>> Note I stated "call". You're likely to get more/better
>> information/assistance speaking to
On Tue, 12 Jun 2012 17:30:43 -0500
Stan Hoeppner wrote:
> On 6/12/2012 8:40 AM, Ramon Hofer wrote:
> > On Sun, 10 Jun 2012 17:30:08 -0500
> > Stan Hoeppner wrote:
>
> >> Try the Wheezy installer. Try OpenSuSE. Try Fedora. If any of
> >> these work without lockup we know the problem is Debian
On Tue, 12 Jun 2012 18:35:57 -0500
Stan Hoeppner wrote:
> > Hmm, probably I have to create a raid5 with the four empty 2 TB
> > disks attached to the LSI. Then:
> >
> > ~$ mdadm -C /dev/md0 -n1 -l linear /dev/md1
>
> WTF?
I also had to add --force to create the array with one raid5.
> > Now
On 6/12/2012 12:05 PM, Ramon Hofer wrote:
> On Sun, 10 Jun 2012 17:30:08 -0500
> Stan Hoeppner wrote:
>
> (...)
>
>> You create two 4 drive md RAID5 arrays, one composed of the four
>> identical 1.5TB drives and the other composed of the four identical
>> 2TB drives. Then concatenate the two ar
On 6/12/2012 8:40 AM, Ramon Hofer wrote:
> On Sun, 10 Jun 2012 17:30:08 -0500
> Stan Hoeppner wrote:
>> Try the Wheezy installer. Try OpenSuSE. Try Fedora. If any of these
>> work without lockup we know the problem is Debian 6. However...
>
> I didn't do this because it the LSI worked with t
On Sun, 10 Jun 2012 17:30:08 -0500
Stan Hoeppner wrote:
(...)
> You create two 4 drive md RAID5 arrays, one composed of the four
> identical 1.5TB drives and the other composed of the four identical
> 2TB drives. Then concatenate the two arrays together into an md
> --linear array, similar to t
On 06/12/2012 09:40 AM, Ramon Hofer wrote:
> On Sun, 10 Jun 2012 17:30:08 -0500
> Stan Hoeppner wrote:
>
>> On 6/10/2012 9:00 AM, Ramon Hofer wrote:
>>> A situation update: Mounted the mobo with the CPU and RAM, attached
>>> the PSU, the OS SATA disk, the LSI and expander as well as the
>>> graph
On Sun, 10 Jun 2012 17:30:08 -0500
Stan Hoeppner wrote:
> On 6/10/2012 9:00 AM, Ramon Hofer wrote:
> > A situation update: Mounted the mobo with the CPU and RAM, attached
> > the PSU, the OS SATA disk, the LSI and expander as well as the
> > graphics card. There are no disks attached to the expan
A situation update: Mounted the mobo with the CPU and RAM, attached the
PSU, the OS SATA disk, the LSI and expander as well as the graphics
card. There are no disks attached to the expander because I put them
again into the old NAS and backing up the data from the 1.5 TB disks to
it.
Then I instal
On 6/6/2012 9:36 AM, Ramon Hofer wrote:
> It's me again.
>
> After several unsuccessful tries to update the BIOS I brought it back to
> my dealer to let him do it.
> He now says that the mainboard is broken and I get my money back.
Interesting...
> Now my question is should I go for the same mai
It's me again.
After several unsuccessful tries to update the BIOS I brought it back to
my dealer to let him do it.
He now says that the mainboard is broken and I get my money back.
Now my question is should I go for the same mainboard again or what do
you recommend?
I suppose the LSI problem was
On 5/30/2012 4:52 PM, Ramon Hofer wrote:
> On Tue, 29 May 2012 20:49:32 -0500
> Stan Hoeppner wrote:
>
>> On 5/29/2012 7:09 AM, Ramon Hofer wrote:
>>> On Sun, 20 May 2012 21:37:19 -0500
>>> Stan Hoeppner wrote:
>>>
>>> (...)
>>>
Does the mobo BIOS show the disk device? If not, does the 924
On Tue, 29 May 2012 20:49:32 -0500
Stan Hoeppner wrote:
> On 5/29/2012 7:09 AM, Ramon Hofer wrote:
> > On Sun, 20 May 2012 21:37:19 -0500
> > Stan Hoeppner wrote:
> >
> > (...)
> >
> >> Does the mobo BIOS show the disk device? If not, does the 9240
> >> BIOS show the disk device, RAID level,
On Tue, 29 May 2012 14:09:27 +0200, Ramon Hofer wrote:
>> Did you already flash the C7P67 BIOS to the latest version? I can't
>> recall.
>
> I have tried to do that but it was quite strange. I created a freedos
> usb stick with unetbootin and copied the files for the update from
> supermicro int
On 5/29/2012 7:09 AM, Ramon Hofer wrote:
> On Sun, 20 May 2012 21:37:19 -0500
> Stan Hoeppner wrote:
>
> (...)
>
>> Does the mobo BIOS show the disk device? If not, does the 9240 BIOS
>> show the disk device, RAID level, and its size?
>>
>> What we need to figure out is whether this is a BIOS p
On Sun, 20 May 2012 21:37:19 -0500
Stan Hoeppner wrote:
(...)
> Does the mobo BIOS show the disk device? If not, does the 9240 BIOS
> show the disk device, RAID level, and its size?
>
> What we need to figure out is whether this is a BIOS problem at this
> point or a Debian installer kernel dr
On 5/21/2012 2:00 PM, Ramon Hofer wrote:
> From my /var/log/installer/syslog I think it uses 2.6.32-5-amd64.
> I have attached the tree log files again (maybe you haven't seen them
> when I posted them to the list).
> There are two syslogs (the one from /var/log as well). And
> the /var/log/instal
On Mon, 21 May 2012, Ramon Hofer wrote:
> On Sun, 20 May 2012 23:35:58 -0300, Henrique de Moraes Holschuh wrote:
> >> Thanks for the suggestion, Henrique!
> >> The PSU is a 750 W so I think it should be enough for now.
> >
> > Yes, it is probably enough. You have to do a lot to overpower a *good*
On Sun, 20 May 2012 21:27:21 -0500
Stan Hoeppner wrote:
> On 5/20/2012 9:24 AM, Ramon Hofer wrote:
> > On Sat, 19 May 2012 11:31:51 -0500, Stan Hoeppner wrote:
> >
> >> On 5/19/2012 5:33 AM, Ramon Hofer wrote:
> >>
> >>> Yes, I'm really thankful for the recommendation. And somehow I
> >>> hoped
On Sun, 20 May 2012 21:37:19 -0500, Stan Hoeppner wrote:
> On 5/20/2012 1:13 PM, Ramon Hofer wrote:
>
>> There were no problems upgrading the fw :-)
>>
>> Unfortunately it didn't solve he problem.
>
> Grrr.
>
>>> 3. Go into the mobo BIOS and set and test these options:
>>>
>>> Quiet Boot:
On Sun, 20 May 2012 21:59:53 -0500, Stan Hoeppner wrote:
> On 5/20/2012 1:13 PM, Ramon Hofer wrote:
>
>> I was able to set a RAID1 in the WebBIOS and set the bootable option.
>> But I'm not sure if the setting was accepted. Even though when I set
>> the bootable option again the WebBIOS tells me
On Sun, 20 May 2012 23:35:58 -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 20 May 2012, Ramon Hofer wrote:
>> On Sat, 19 May 2012 13:06:40 -0300, Henrique de Moraes Holschuh wrote:
>> > On Sat, 19 May 2012, Ramon Hofer wrote:
>> >> On Sat, 19 May 2012 04:19:33 -0500, Stan Hoeppner wrote:
>>
On 5/20/2012 1:13 PM, Ramon Hofer wrote:
> I was able to set a RAID1 in the WebBIOS and set the bootable option. But
> I'm not sure if the setting was accepted. Even though when I set the
> bootable option again the WebBIOS tells me the option is already set - so
> it should be ok?
>
> Unfortu
On 5/20/2012 1:13 PM, Ramon Hofer wrote:
> There were no problems upgrading the fw :-)
>
> Unfortunately it didn't solve he problem.
Grrr.
>> 3. Go into the mobo BIOS and set and test these options:
>>
>> Quiet Boot: DISABLED
>> Interrupt 19 Capture:
On Sun, 20 May 2012, Ramon Hofer wrote:
> On Sat, 19 May 2012 13:06:40 -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 19 May 2012, Ramon Hofer wrote:
> >> On Sat, 19 May 2012 04:19:33 -0500, Stan Hoeppner wrote:
> >> > On 5/19/2012 2:52 AM, Ramon Hofer wrote:
> >> >> On Fri, 18 May 2012 17:5
On 5/20/2012 9:24 AM, Ramon Hofer wrote:
> On Sat, 19 May 2012 11:31:51 -0500, Stan Hoeppner wrote:
>
>> On 5/19/2012 5:33 AM, Ramon Hofer wrote:
>>
>>> Yes, I'm really thankful for the recommendation. And somehow I hoped
>>> you could jump in and help me :-)
>>
>> I'm actively working on it, have
On Sat, 19 May 2012 11:31:51 -0500, Stan Hoeppner wrote:
> On 5/19/2012 5:33 AM, Ramon Hofer wrote:
>
>> Yes, I'm really thankful for the recommendation. And somehow I hoped
>> you could jump in and help me :-)
>
> I'm actively working on it, have been for a couple of hours on and off.
> I'm re
On Sat, 19 May 2012 11:31:51 -0500, Stan Hoeppner wrote:
> On 5/19/2012 5:33 AM, Ramon Hofer wrote:
>
>> Yes, I'm really thankful for the recommendation. And somehow I hoped
>> you could jump in and help me :-)
>
> I'm actively working on it, have been for a couple of hours on and off.
> I'm re
On Sun, 20 May 2012 12:12:55 +, Ramon Hofer wrote:
> On Sat, 19 May 2012 13:41:33 +, Camaleón wrote:
>
>> Mmm, have you tried to set a RAID level instead using JBOD? It's just
>> for testing... although this can only be done in a very early stage
>> when the disks are completely empty wit
On Sat, 19 May 2012 13:06:40 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 19 May 2012, Ramon Hofer wrote:
>> On Sat, 19 May 2012 04:19:33 -0500, Stan Hoeppner wrote:
>> > On 5/19/2012 2:52 AM, Ramon Hofer wrote:
>> >> On Fri, 18 May 2012 17:57:56 -0500, Stan Hoeppner wrote:
>> >>
>> >>> On
On Sat, 19 May 2012 13:41:33 +, Camaleón wrote:
(...)
>> I have tried to check if I can see something in the mb BIOS to see if
>> it can tell me anything about the connected hardware. But I didn't find
>> anything in the PCI settings.
>
> Mmm, have you tried to set a RAID level instead using
On Sun, 20 May 2012, Stan Hoeppner wrote:
> On 5/19/2012 11:05 AM, Henrique de Moraes Holschuh wrote:
> > On Sat, 19 May 2012, Ramon Hofer wrote:
> And after a while there are more messages which I don't understand. I
> have taken a picture:
> http://666kb.com/i/c3wf606sc1qkcvgoc.jpg
On 5/19/2012 11:05 AM, Henrique de Moraes Holschuh wrote:
> On Sat, 19 May 2012, Ramon Hofer wrote:
And after a while there are more messages which I don't understand. I
have taken a picture:
http://666kb.com/i/c3wf606sc1qkcvgoc.jpg
>>>
>>> It shows that udev is having serious troubl
On 5/19/2012 5:33 AM, Ramon Hofer wrote:
> Yes, I'm really thankful for the recommendation.
> And somehow I hoped you could jump in and help me :-)
I'm actively working on it, have been for a couple of hours on and off.
I'm reading your responses as I go before responding so I hopefully
don't re
On Sat, 19 May 2012, Ramon Hofer wrote:
> On Sat, 19 May 2012 04:19:33 -0500, Stan Hoeppner wrote:
> > On 5/19/2012 2:52 AM, Ramon Hofer wrote:
> >> On Fri, 18 May 2012 17:57:56 -0500, Stan Hoeppner wrote:
> >>
> >>> On 5/18/2012 9:39 AM, Shane Johnson wrote:
> >>>
> After that I would look t
On Sat, 19 May 2012, Ramon Hofer wrote:
> >> And after a while there are more messages which I don't understand. I
> >> have taken a picture:
> >> http://666kb.com/i/c3wf606sc1qkcvgoc.jpg
> >
> > It shows that udev is having serious trouble handling one of the USB
> > devices.
>
> Yes but only wh
On Sat, 19 May 2012 11:26:09 +, Ramon Hofer wrote:
> On Sat, 19 May 2012 09:09:52 +, Camaleón wrote:
>> You installed the lsi card in one of the motherboard slots, configured
>> the BIOS to use a JBOD disk layout and then boot the installation CD
>> for Squeeze, right?
>
> Yes, but I did
On Sat, 19 May 2012 10:33:06 +, Ramon Hofer wrote:
> On Fri, 18 May 2012 17:47:54 -0500, Stan Hoeppner wrote:
>
>> Post your FW version here. It's likely pretty recent already.
>
> The FW version is 2.70.04-0862.
>
> I have a little confusion with the versioning from LSI. On their
> homepa
On Sat, 19 May 2012 09:09:52 +, Camaleón wrote:
> On Fri, 18 May 2012 21:55:36 +, Ramon Hofer wrote:
>
>> On Fri, 18 May 2012 20:18:46 +, Camaleón wrote:
>
>>> Are you running Squeeze?
>>
>> Yes, sorry forgot to mention.
>>
>> I installed squeeze amd64 yesterday on a raid1 (just t
On Sat, 19 May 2012 04:19:33 -0500, Stan Hoeppner wrote:
> On 5/19/2012 2:52 AM, Ramon Hofer wrote:
>> On Fri, 18 May 2012 17:57:56 -0500, Stan Hoeppner wrote:
>>
>>> On 5/18/2012 9:39 AM, Shane Johnson wrote:
>>>
After that I would look to see if
something isn't shorting out a USB port
On Fri, 18 May 2012 17:47:54 -0500, Stan Hoeppner wrote:
> On 5/18/2012 9:23 AM, Ramon Hofer wrote:
>> Hi all
>>
>> I finally got my LSI 9240-4i and the Intel SAS expander.
>>
>> Unfortunately it prevents the system from booting. I only got this
>> message on the screen:
>>
>> megasas: INIT ada
On Fri, 18 May 2012 18:28:05 -0500, Stan Hoeppner wrote:
> On 5/18/2012 4:55 PM, Ramon Hofer wrote:
>
>> I installed squeeze amd64 yesterday on a raid1 (just to try).
>
> You need to explain this in detail: "installed on raid1"
>
> Installed onto what raid1? Does this mean you created an mdad
On 5/19/2012 2:52 AM, Ramon Hofer wrote:
> On Fri, 18 May 2012 17:57:56 -0500, Stan Hoeppner wrote:
>
>> On 5/18/2012 9:39 AM, Shane Johnson wrote:
>>
>>> After that I would look to see if
>>> something isn't shorting out a USB port.
>>
>> Yes, USB is the cause of the over-current errors, which is
On Fri, 18 May 2012 21:55:36 +, Ramon Hofer wrote:
> On Fri, 18 May 2012 20:18:46 +, Camaleón wrote:
>> Are you running Squeeze?
>
> Yes, sorry forgot to mention.
>
> I installed squeeze amd64 yesterday on a raid1 (just to try). Today when
> the card was here I put it in and couldn't b
On Fri, 18 May 2012 17:57:56 -0500, Stan Hoeppner wrote:
> On 5/18/2012 9:39 AM, Shane Johnson wrote:
>
>> After that I would look to see if
>> something isn't shorting out a USB port.
>
> Yes, USB is the cause of the over-current errors, which is plainly
> evident in his screen shot. But we don
On 5/18/2012 4:55 PM, Ramon Hofer wrote:
> I installed squeeze amd64 yesterday on a raid1 (just to try).
You need to explain this in detail: "installed on raid1"
Installed onto what raid1? Does this mean you created an mdadm raid1
pair during the Squeeze installation process, and installed to
On 5/18/2012 9:39 AM, Shane Johnson wrote:
> Over current problems from what I have seen are hardware problems - I would
> make sure the intel expander doesn't need a external power source and if it
> does that it is functioning properly.
Ramon is well aware of the power configuration for the ex
On 5/18/2012 9:23 AM, Ramon Hofer wrote:
> Hi all
>
> I finally got my LSI 9240-4i and the Intel SAS expander.
>
> Unfortunately it prevents the system from booting. I only got this
> message on the screen:
>
> megasas: INIT adapter done
> hub 4-1:1.0 over-current condition on port 7
> hub 4-1:
On Fri, 18 May 2012 20:18:46 +, Camaleón wrote:
> On Fri, 18 May 2012 14:23:51 +, Ramon Hofer wrote:
>
>> I finally got my LSI 9240-4i and the Intel SAS expander.
>>
>> Unfortunately it prevents the system from booting. I only got this
>> message on the screen:
>>
>> megasas: INIT adapt
On Fri, 18 May 2012 14:23:51 +, Ramon Hofer wrote:
> I finally got my LSI 9240-4i and the Intel SAS expander.
>
> Unfortunately it prevents the system from booting. I only got this
> message on the screen:
>
> megasas: INIT adapter done
> hub 4-1:1.0 over-current condition on port 7
> hub 4
On Fri, 18 May 2012 08:39:57 -0600, Shane Johnson wrote:
> On Fri, May 18, 2012 at 8:23 AM, Ramon Hofer
> wrote:
>
>> Hi all
>>
>> I finally got my LSI 9240-4i and the Intel SAS expander.
>>
>> Unfortunately it prevents the system from booting. I only got this
>> message on the screen:
>>
>> meg
Over current problems from what I have seen are hardware problems - I would
make sure the intel expander doesn't need a external power source and if it
does that it is functioning properly. After that I would look to see if
something isn't shorting out a USB port.
Shane
On Fri, May 18, 2012 at
Hi all
I finally got my LSI 9240-4i and the Intel SAS expander.
Unfortunately it prevents the system from booting. I only got this
message on the screen:
megasas: INIT adapter done
hub 4-1:1.0 over-current condition on port 7
hub 4-1:1.0 over-current condition on port 8
I also got the over-cur
63 matches
Mail list logo
