System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

ls: cannot access /sys/bus/scsi/devices/1:0:1:0/: No such file or directory

hpuxmagic
Advisor

ls: cannot access /sys/bus/scsi/devices/1:0:1:0/: No such file or directory

running redhat linux 6 on HP ProLian and with Smart Array P410 contorller.

 

 

I am running the controller utility hpacucli, but got the following error at beginning.
# hpacucli ctrl all show config
ls: cannot access /sys/bus/scsi/devices/1:0:1:0/: No such file or directory
ls: cannot access /sys/bus/scsi/devices/1:0:3:0/: No such file or directory
ls: cannot access /sys/bus/scsi/devices/1:0:1:0/: No such file or directory
ls: cannot access /sys/bus/scsi/devices/1:0:3:0/: No such file or directory

 

Smart Array P410i in Slot 0 (Embedded) (sn: 5001438007C179D0)

array A (SAS, Unused Space: 0 MB)

logicaldrive 1 (136.7 GB, RAID 1, OK)

physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK)
physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 146 GB, OK)

array B (SAS, Unused Space: 0 MB)

logicaldrive 3 (558.7 GB, RAID 1+0, Recovering, 5% complete)

physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 300 GB, Rebuilding)
physicaldrive 1I:1:4 (port 1I:box 1:bay 4, SAS, 300 GB, OK)
physicaldrive 2I:1:5 (port 2I:box 1:bay 5, SAS, 300 GB, OK)
physicaldrive 2I:1:6 (port 2I:box 1:bay 6, SAS, 300 GB, OK)


Any idea why all these files got lost?

Thanks!

1 REPLY
Matti_Kurkela
Honored Contributor

Re: ls: cannot access /sys/bus/scsi/devices/1:0:1:0/: No such file or directory

All the files in /sys are virtual constructs, based on the kernel data structures.

You may have some storage devices that used to be accessible through the /sys/class/scsi_host/host1 storage controller, but have been yanked away. If /sys/class/scsi_host/host1 is a SAN HBA, it might be that the storage admin has un-presented some LUNs.

 

Use "lsscsi" or the files in /sys/class/scsi_host/host1 to identify what the second storage controller actually is.

It probably isn't the Smart Array controller: the first storage controller is #0, the second is #1.

 

If the disks are some un-presented SAN LUNs you no longer need, first find out which /dev/sd* device(s) correspond to them, then use a command like "echo 1 >/sys/block/sdX/device/delete" to tell the system that those devices have been removed on purpose and aren't coming back. Or just reboot.

MK