Le 3/13/25 à 17:36, Michael Stone a écrit> I guess I don't understand how you
expect smartctl to query a dead disk. It's dead, that means it's not going to
respond.
I wish there a was some kind of "death" that would render the drive useless for
storage
but still usable enough to retrieve diagn
Le 3/13/25 à 17:36, Michael Stone a écrit :
I guess I don't understand how you expect smartctl to query a dead disk. It's
dead, that means it's not going to respond.
I secretly wished there was some kind of blackbox in some specialized chip or
memory
that specialized software can use for fore
Le 3/13/25 à 14:33, Erwan David a écrit :
You can get the layout with lsblk, IIRC
I'm not an expert on the subject,
but from the few man pages and online help I've gathered,
I have come to understand that the system (and lsblk) only see logical disks.
Physical disks are hidden behind the RAID
On Thu, Mar 13, 2025 at 02:08:21PM CET, Yassine Chaouche
said:
> Le 3/12/25 à 23:11, Michael Stone a écrit :
> > Two of the drives are dead, you're not going to see anything from them
>
> So this means I can't rely on smartctl to list physical disks,
> which implies that,
> for servers I didn't
On Thu, 13 Mar 2025 12:36:46 -0400
Michael Stone wrote:
> I guess I don't understand how you expect smartctl to query a dead
> disk. It's dead, that means it's not going to respond.
Not quite. The electronics may respond even if the head-disk assembly
(HDA) is broken. It probably won't give a co
On Thu, Mar 13, 2025 at 11:35:08AM -0600, Charles Curley wrote:
On Thu, 13 Mar 2025 12:36:46 -0400
Michael Stone wrote:
I guess I don't understand how you expect smartctl to query a dead
disk. It's dead, that means it's not going to respond.
Not quite. The electronics may respond even if the
On Thu, Mar 13, 2025 at 02:08:21PM +0100, Yassine Chaouche wrote:
Le 3/12/25 à 23:11, Michael Stone a écrit :
Two of the drives are dead, you're not going to see anything from them
So this means I can't rely on smartctl to list physical disks,
I guess I don't understand how you expect smartc
Le 3/12/25 à 17:51, Greg a écrit> According to my (very old) scripts you should
use something like
/dev/cciss/c1d0 instead of /dev//sg?
It could be the old driver/kernel module interface.
The one I have is /dev/sgx.
I have no /dev/cciss* present.
Besides, for HP Smart Array,
the example found
Le 3/12/25 à 23:11, Michael Stone a écrit :
Two of the drives are dead, you're not going to see anything from them
So this means I can't rely on smartctl to list physical disks,
which implies that,
for servers I didn't install,
I need to know their RAID setup in advance,
or at least the total n
On Wed, Mar 12, 2025 at 04:41:06PM +0100, Yassine Chaouche wrote:
I have 5 disks on my server,
2x1 terabyte disks + 3x450 Gb disks,
but smartctl and cciss_vol_status only show 3 disks.
My controller is sg0 as shown in the output of lssci
Two of the drives are dead, you're not going to see anyth
On 3/12/25 16:41, Yassine Chaouche wrote:
Dear list,
I have 5 disks on my server,
2x1 terabyte disks + 3x450 Gb disks,
but smartctl and cciss_vol_status only show 3 disks.
My controller is sg0 as shown in the output of lssci
root@messagerie-recup[10.10.10.22] ~ # lsscsi -gs
[1:0:0:0]
Dear list,
I have 5 disks on my server,
2x1 terabyte disks + 3x450 Gb disks,
but smartctl and cciss_vol_status only show 3 disks.
My controller is sg0 as shown in the output of lssci
root@messagerie-recup[10.10.10.22] ~ # lsscsi -gs
[1:0:0:0]cd/dvd hp DVD A DS8A5LH 1HE3 /dev/
12 matches
Mail list logo
