Am 07.10.20 um 10:40 schrieb Stefan G. Weichinger:
> Am 06.10.20 um 15:08 schrieb k...@aspodata.se:
>> Stefan G. Weichinger:
>>> I know the model: ICP5165BR
>>
>> https://ask.adaptec.com/app/answers/detail/a_id/17414/~/support-for-sata-and-sas-disk-drives-with-a-size-of-2tb-or-greater
>>
>> says
Am 06.10.20 um 15:08 schrieb k...@aspodata.se:
> Stefan G. Weichinger:
>> I know the model: ICP5165BR
>
> https://ask.adaptec.com/app/answers/detail/a_id/17414/~/support-for-sata-and-sas-disk-drives-with-a-size-of-2tb-or-greater
>
> says it is supported up to 8TB drives using firmware v5.2.0
Stefan G. Weichinger:
> Am 06.10.20 um 11:52 schrieb k...@aspodata.se:
> > Stefan G. Weichinger:
> >> Am 05.10.20 um 21:32 schrieb k...@aspodata.se:
> > ...
> >> What do you think, is 2 TB maybe too big for the controller?
> >
> 0a:0e.0 RAID bus controller: Adaptec AAC-RAID
> >
> > This
On 05/10/2020 17:01, Stefan G. Weichinger wrote:
Am 05.10.20 um 17:19 schrieb Stefan G. Weichinger:
So my issue seems to be: non-working arcconf doesn't let me "enable"
that one drive.
Some kind of progress.
Searched for more and older releases of arcconf, found Version 1.2 that
doesn't
Am 06.10.20 um 11:52 schrieb k...@aspodata.se:
> Some guesses:
>
> https://wiki.debian.org/LinuxRaidForAdmins#aacraid
> says that it requires libstd++5
>
> arcconf might fork and exec, one could try with strace and try to
> see what happens
>
> one could, if the old suse dist. is
Am 06.10.20 um 11:52 schrieb k...@aspodata.se:
> Stefan G. Weichinger:
>> Am 05.10.20 um 21:32 schrieb k...@aspodata.se:
> ...
>> What do you think, is 2 TB maybe too big for the controller?
>
0a:0e.0 RAID bus controller: Adaptec AAC-RAID
>
> This doesn't really tells us which controller it
Stefan G. Weichinger:
> Am 05.10.20 um 16:38 schrieb k...@aspodata.se:
...
> But no luck with any version of arcconf so far. Unpacked several zips,
> tried 2 releases, 32 and 64 bits .. all crash.
>
> > Just a poke in the dark, does ldd report all libs found, as in:
> > $ ldd /bin/ls
> >
Stefan G. Weichinger:
> Am 05.10.20 um 21:32 schrieb k...@aspodata.se:
...
> What do you think, is 2 TB maybe too big for the controller?
>>> 0a:0e.0 RAID bus controller: Adaptec AAC-RAID
This doesn't really tells us which controller it is, try with
lspci -s 0a:0e.0 -nn
In the kernel source
Am 05.10.20 um 21:32 schrieb k...@aspodata.se:
> What if you put it on the 53c1030 card, can you do that, at least to
> verify the disk ?
I am 600kms away from that server and the people I could send to the
basement there aren't very competent in these things. I am afraid that
won't work out
Stefan G. Weichinger:
...
> Searched for more and older releases of arcconf, found Version 1.2 that
> doesn't crash here.
>
> This lets me view the physical device(s), but the new disk is marked as
> "Failed".
...
What if you put it on the 53c1030 card, can you do that, at least to
verify the
Am 05.10.20 um 17:19 schrieb Stefan G. Weichinger:
> So my issue seems to be: non-working arcconf doesn't let me "enable"
> that one drive.
Some kind of progress.
Searched for more and older releases of arcconf, found Version 1.2 that
doesn't crash here.
This lets me view the physical
Am 05.10.20 um 16:57 schrieb Rich Freeman:
> If you're doing software RAID or just individual disks, then you're
> probably going to go into the controller and basically configure that
> disk as standalone, or as a 1-disk "RAID". That will make it appear
> to the OS, and then you can do whatever
Am 05.10.20 um 16:38 schrieb k...@aspodata.se:
> And theese on the aac, since they have the same scsi host, and I guess
> that scsi ch.0 is for the configured drives and ch.1 for the raw drives:
>> [1:0:1:0]diskICP SAS2 V1.0 /dev/sda
>> [1:0:2:0]diskICP
On Mon, Oct 5, 2020 at 10:38 AM wrote:
>
> Stefan G. Weichinger:
> > On an older server the customer replaced a SAS drive.
> >
> > I see it as /dev/sg11, but not yes as /dev/sdX, it is not visible in "lsblk"
>
> Perhaps theese links will help:
>
>
Stefan G. Weichinger:
> On an older server the customer replaced a SAS drive.
>
> I see it as /dev/sg11, but not yes as /dev/sdX, it is not visible in "lsblk"
...
Not that I think it will help you much, but there is sys-apps/sg3_utils:
# lsscsi
[0:0:0:0]diskATA TOSHIBA MG03ACA3
On an older server the customer replaced a SAS drive.
I see it as /dev/sg11, but not yes as /dev/sdX, it is not visible in "lsblk"
Back then with an installed Suse Linux, I had some GUI tool to create a
VD on top of the physical drive and "enable" it ...
I am searching how to achieve that in
16 matches
Mail list logo
