Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array


dlandon

Recommended Posts

2 hours ago, mrbrowndk said:

Thanks for that thorough investigation!!! And here the noob q :)How to change when network is started before UD? 

 

Or somehow delay the auto mount e.g. 1 min?

The automount cannot be delayed.  People use UD devices for Dockers and VMs and they need the UD device to be ready.

 

I'm not an expert on the startup sequence of unRAID and the network, so I can't help there.

Edited by dlandon
  • Like 1
Link to comment
On 26 March 2018 at 8:29 AM, hawihoney said:

This is the output of wipefs. DOS? On a 3TB drive? Last time I used DOS was when using 1,44MB diskettes.

 

Really weird. 


Linux 4.14.26-unRAID.
root@Tower:~# wipefs /dev/sdg
DEVICE OFFSET TYPE UUID LABEL
sdg    0x1fe  dos
root@Tower:~#

 

 

Did you ever get this issue sorted out and your disk recognised?

 

I have a similar problem, having just completed a Parity Disk Upgrade (4 > 8Tb). When I plugged my old Parity Drive in it is not recognised as an Unassigned Device (from the unRAID Main Tab or when using the Unassigned Devices Plugin). It was seen as an output when I ran ls -l /dev/disk/by-id from the terminal and also showed up in the recently updated Preclear Disks Plugin screen (as device sdh), however, there is no drive/model info attached to the drive and when I attempted a Preclear it failed.

Link to comment

 

1 hour ago, blu3_v2 said:

 

Did you ever get this issue sorted out and your disk recognised?

 

I have a similar problem, having just completed a Parity Disk Upgrade (4 > 8Tb). When I plugged my old Parity Drive in it is not recognised as an Unassigned Device (from the unRAID Main Tab or when using the Unassigned Devices Plugin). It was seen as an output when I ran ls -l /dev/disk/by-id from the terminal and also showed up in the recently updated Preclear Disks Plugin screen (as device sdh), however, there is no drive/model info attached to the drive and when I attempted a Preclear it failed.

 

Yes, wipefs did the trick. Double check that this drive is not part of the array. Double check the correct device name. Issue "wipefs /dev/xxx" (replace xxx by correct device) without any additional parameters to check the current FS. This step is not necessary. It's just to check if it gives a non-unRAID-FS output. Finally "wipefs --all /dev/xxx" to wipe the disk. Lasts a second or so. After that I could attach the disk immediately to UD.

 

Edited by hawihoney
Link to comment
2 hours ago, hawihoney said:

 

 

Yes, wipefs did the trick. Double check that this drive is not part of the array. Double check the correct device name. Issue "wipefs /dev/xxx" (replace xxx by correct device) without any additional parameters to check the current FS. This step is not necessary. It's just to check if it gives a non-unRAID-FS output. Finally "wipefs --all /dev/xxx" to wipe the disk. Lasts a second or so. After that I could attach the disk immediately to UD.

 

Thanks for the tip.

 

I just shutdown my server to check that it was not a cabling issue, and now when I boot the drive is not recognised at all. Looks like I will have to shutdown and recheck cabling again or remove the drive and see if I can format it from another system before adding to the array. I find it strange that the drive had previously been functioning perfectly in unRAID as a Parity drive, then when installed back into the same system it is not recognised. Maybe it has to do with the fact the the Parity drive contains data without a file-system or partition structure as such.

Link to comment

I am new to this whole thing, but I can't get my external drive to mount on my Unraid server. It mounts on my Mac fine, it is exFat. I got it to mount once, but it only mounted the EFI partition. Here are the logs I am getting. 

Apr 3 23:30:36 Tower kernel: sd 11:0:0:0: [sdd] Spinning up disk...
Apr 3 23:30:46 Tower kernel: sd 11:0:0:0: [sdd] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 3 23:30:46 Tower kernel: sd 11:0:0:0: [sdd] Write Protect is off
Apr 3 23:30:46 Tower kernel: sd 11:0:0:0: [sdd] Mode Sense: 4f 00 00 00
Apr 3 23:30:46 Tower kernel: sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 3 23:30:46 Tower kernel: sdd: sdd1 sdd2
Apr 3 23:30:46 Tower kernel: sd 11:0:0:0: [sdd] Attached SCSI disk
Apr 3 23:43:39 Tower unassigned.devices: Adding disk '/dev/sdd1'...
Apr 3 23:43:39 Tower unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdd1' '/mnt/disks/EFI'
Apr 3 23:43:39 Tower unassigned.devices: Successfully mounted '/dev/sdd1' on '/mnt/disks/EFI'.
Apr 3 23:43:39 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'ADD' script not executed.
Apr 3 23:44:16 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'REMOVE' script not executed.
Apr 3 23:44:16 Tower unassigned.devices: Unmounting '/dev/sdd1'...
Apr 3 23:44:16 Tower unassigned.devices: Successfully unmounted '/dev/sdd1'
Apr 4 00:26:57 Tower kernel: sd 11:0:0:0: [sdd] Synchronizing SCSI cache
Apr 4 00:26:57 Tower kernel: sd 11:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Apr 4 00:38:25 Tower kernel: sd 11:0:0:0: [sdd] Spinning up disk...
Apr 4 00:38:35 Tower kernel: sd 11:0:0:0: [sdd] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 4 00:38:35 Tower kernel: sd 11:0:0:0: [sdd] Write Protect is off
Apr 4 00:38:35 Tower kernel: sd 11:0:0:0: [sdd] Mode Sense: 4f 00 00 00
Apr 4 00:38:35 Tower kernel: sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 4 00:38:35 Tower kernel: sdd: sdd1 sdd2
Apr 4 00:38:35 Tower kernel: sd 11:0:0:0: [sdd] Attached SCSI disk
Apr 4 00:39:18 Tower unassigned.devices: Adding disk '/dev/sdd1'...
Apr 4 00:39:18 Tower unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdd1' '/mnt/disks/EFI'
Apr 4 00:39:18 Tower unassigned.devices: Successfully mounted '/dev/sdd1' on '/mnt/disks/EFI'.
Apr 4 00:39:18 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'ADD' script not executed.
Apr 4 00:40:21 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'REMOVE' script not executed.
Apr 4 00:40:21 Tower unassigned.devices: Unmounting '/dev/sdd1'...
Apr 4 00:40:21 Tower unassigned.devices: Successfully unmounted '/dev/sdd1'
Apr 4 00:57:25 Tower kernel: sd 11:0:0:0: [sdd] Synchronizing SCSI cache
Apr 4 00:57:25 Tower kernel: sd 11:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Apr 4 00:57:48 Tower kernel: sd 11:0:0:0: [sdd] Spinning up disk...
Apr 4 00:57:58 Tower kernel: sd 11:0:0:0: [sdd] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 4 00:57:58 Tower kernel: sd 11:0:0:0: [sdd] Write Protect is off
Apr 4 00:57:58 Tower kernel: sd 11:0:0:0: [sdd] Mode Sense: 4f 00 00 00
Apr 4 00:57:58 Tower kernel: sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 4 00:57:58 Tower kernel: sdd: sdd1 sdd2
Apr 4 00:57:58 Tower kernel: sd 11:0:0:0: [sdd] Attached SCSI disk
Apr 4 00:58:11 Tower unassigned.devices: Adding disk '/dev/sdd1'...
Apr 4 00:58:11 Tower unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdd1' '/mnt/disks/EFI'
Apr 4 00:58:11 Tower unassigned.devices: Successfully mounted '/dev/sdd1' on '/mnt/disks/EFI'.
Apr 4 00:58:11 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'ADD' script not executed.
Apr 4 00:58:37 Tower unassigned.devices: Device '/dev/sdd1' script file not found. 'REMOVE' script not executed.
Apr 4 00:58:37 Tower unassigned.devices: Unmounting '/dev/sdd1'...
Apr 4 00:58:37 Tower unassigned.devices: Successfully unmounted '/dev/sdd1'
Apr 4 00:58:55 Tower kernel: sd 11:0:0:0: [sdd] Synchronizing SCSI cache
Apr 4 00:58:55 Tower kernel: sd 11:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Apr 4 00:58:58 Tower kernel: sd 11:0:0:0: [sdd] Spinning up disk...
Apr 4 00:59:04 Tower kernel: sd 11:0:0:0: [sdd] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 4 00:59:04 Tower kernel: sd 11:0:0:0: [sdd] Write Protect is off
Apr 4 00:59:04 Tower kernel: sd 11:0:0:0: [sdd] Mode Sense: 4f 00 00 00
Apr 4 00:59:04 Tower kernel: sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 4 00:59:04 Tower kernel: sdd: sdd1 sdd2
Apr 4 00:59:04 Tower kernel: sd 11:0:0:0: [sdd] Attached SCSI disk

Any ideas? 

Thanks

Link to comment
On 2 April 2018 at 7:27 PM, hawihoney said:

I'm not sure if my failing drive was a parity drive before. But as it's SMART values are ok I bet it was.

 

I don't swap data drives if SMART values are ok. But I swap parity drives with perfect SMART values if I need a bigger one.

 

My old Parity Drive was perfectly healthy, and I can now report that it was correctly recognised as an Unassigned Device once I shutdown the server and triple-checked all cabling (turns out it must have a loose/intermittent connection to my PCIe SATA card). It is now undergoing a Preclear just to be safe before being added as an Array Disk.

Link to comment
47 minutes ago, blu3_v2 said:

My old Parity Drive was perfectly healthy, and I can now report that it was correctly recognised as an Unassigned Device once I shutdown the server and triple-checked all cabling (turns out it must have a loose/intermittent connection to my PCIe SATA card). It is now undergoing a Preclear just to be safe before being added as an Array Disk.

Looks like I spoke too soon. Shortly after starting the Clearing process I received Read errors and the Process Aborted. Have posted in General Support section as unrelated to this plugin.

Edited by blu3_v2
Reposted to General Support
Link to comment
23 minutes ago, blu3_v2 said:

Looks like I spoke too soon. Shortly after starting the Clearing process I received Read errors and the Process Aborted.

 

I tried to run a SMART test on the newly added old Parity Drive but this too fails. I have attached a link to my Diagnosics file (as am writing this from my iPad). Could someone please let me know how to proceed as I now have a disk with a Blue Square beside it in my Array. How do I remove this/fix it without messing up parity.

 

Diagnostics link http://users.on.net/~jilbo/watchtower-diagnostics-20180404-1845.zip

 

Disk dropped offline, it's on a Marvell controller and these are know to drop disks in some cases, disk4 is on the same controller, has it been there for long and without issues?

Link to comment
54 minutes ago, johnnie.black said:

 

Disk dropped offline, it's on a Marvell controller and these are know to drop disks in some cases, disk4 is on the same controller, has it been there for long and without issues?

Disk 4 has been on the same controller for a few weeks and has undergone a change from ReiserFS to XFS, as well as a complete Parity Check without issues. I set Disk 5 as No Device rather than attempt to add the old Parity back to the Array for now as it was giving errors while trying to Spin Down, and even now when Unassigned. I will unplug it until I can source a new SATA card and/or cabling.

Link to comment
3 hours ago, mrbrowndk said:

Hi Dlandon, Thanks for the help until now. Is there a way to restart UD via a command e.g. restarting UD via a user script?

I don't understand what you want to do by "restarting" UD.  There is nothing to restart.  You can refresh the devices by clicking on the refresh icon in the upper right side of the UI.

Link to comment
33 minutes ago, dlandon said:

I don't understand what you want to do by "restarting" UD.  There is nothing to restart.  You can refresh the devices by clicking on the refresh icon in the upper right side of the UI.

He's trying to get around his slow network startup, but apparently doesn't want to wait until the network is up and start the array manually.

 

Turning off array autostart would solve the issue.

 

Link to comment
4 hours ago, mrbrowndk said:

Hi Dlandon, Thanks for the help until now. Is there a way to restart UD via a command e.g. restarting UD via a user script?

Install User Scripts and set up a script to run on array start:

sleep 60
usr/local/sbin/rc.unassigned mount auto

This will mount any UD automount devices that haven't already been mounted.  Any devices already mounted, will not be affected.

Link to comment
13 minutes ago, JackBauer said:

Is there a way to view / monitor active connections?

 

Sorry - hard to read through 86 pages to find this answer :)

3 plugins which might be useful to you. Active Streams, File Activity, and Open Files. You can get them from Community Applications of course.

Link to comment

Thank you - but Active Streams doesn't seem to pick up on shares that are outside the array?  I have a UD "share" that is actually an SMB share from another server.  Just wanting to monitor that "stream" if possible.

 

Any ideas?  Not super-urgent...

 

edit:  Never mind - I used a plugin to monitor my Ethernet traffic - and that's a proxy for what I wanted...

Edited by JackBauer
Link to comment

I presume this is simple, but search for drive not appearing in unassigned devices doesn't give me anything I can work with.

Installed 8 x 2tb SAS drives on an M1015, run the preclear script from the tools tab.  Let that finish, all good and we're back to here:

image.thumb.png.06c606717ac0fa720a1f407a4c5b2909.png

But they are not available in unassigned devices:
image.thumb.png.8c4e7197feabe76bcc36485c3fa43bcc.png


Is this because they are SAS drives on a SAS controller?  I wouldn't have thought so mind...

image.png.0aeb062d859a455267328008f7ea73d0.png


Main tabs shows the drives?

  

Diagnostics attached:
alexserver-diagnostics-20180408-2252.zip

 

 

Link to comment
2 minutes ago, dlandon said:

Give me the output of this command:


ls -l /dev/disk/by-id/

 

 

 

lrwxrwxrwx 1 root root  9 Apr  8 12:00 ata-SAMSUNG_HD103SJ_S246J9GZB06056 -> ../../sdj
lrwxrwxrwx 1 root root 10 Apr  8 12:00 ata-SAMSUNG_HD103SJ_S246J9GZB06056-part1 -> ../../sdj1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 ata-ST1000DM003-1CH162_Z1D8Y3Z7 -> ../../sdl
lrwxrwxrwx 1 root root 10 Apr  8 12:00 ata-ST1000DM003-1CH162_Z1D8Y3Z7-part1 -> ../../sdl1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 ata-ST500DM002-1BD142_Z6ELEWZY -> ../../sdm
lrwxrwxrwx 1 root root 10 Apr  8 12:00 ata-ST500DM002-1BD142_Z6ELEWZY-part1 -> ../../sdm1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 ata-WDC_WD20EURX-63T0FY0_WD-WCC4M7XA0RXL -> ../../sdf
lrwxrwxrwx 1 root root 10 Apr  8 12:00 ata-WDC_WD20EURX-63T0FY0_WD-WCC4M7XA0RXL-part1 -> ../../sdf1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM3ZVZY0000C130DG42 -> ../../sdd
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM3ZVZY0000C130DG42-part1 -> ../../sdd1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM4C6CD00009133T7SW -> ../../sdi
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM4C6CD00009133T7SW-part1 -> ../../sdi1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM4EPZT00009134CTD1 -> ../../sdc
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM4EPZT00009134CTD1-part1 -> ../../sdc1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM4FMPL0000C1347DNU -> ../../sdb
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM4FMPL0000C1347DNU-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM4HELV00009134WA9B -> ../../sdg
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM4HELV00009134WA9B-part1 -> ../../sdg1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM4LHLS0000C1347ADN -> ../../sdh
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM4LHLS0000C1347ADN-part1 -> ../../sdh1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM5ZE6E0000C1435EES -> ../../sde
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM5ZE6E0000C1435EES-part1 -> ../../sde1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 scsi-ST32000444SS_9WM6036J0000C1432M65 -> ../../sdk
lrwxrwxrwx 1 root root 10 Apr  8 12:00 scsi-ST32000444SS_9WM6036J0000C1432M65-part1 -> ../../sdk1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 usb-Kingston_DataTraveler_U3_0E61E860C1632924-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  8 12:00 usb-Kingston_DataTraveler_U3_0E61E860C1632924-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c5002622b38f -> ../../sdd
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c5002622b38f-part1 -> ../../sdd1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50033d0d8b7 -> ../../sdi
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50033d0d8b7-part1 -> ../../sdi1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50033d97543 -> ../../sdc
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50033d97543-part1 -> ../../sdc1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50033d9fefb -> ../../sdb
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50033d9fefb-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50033e0f60b -> ../../sdg
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50033e0f60b-part1 -> ../../sdg1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50033e3703f -> ../../sdh
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50033e3703f-part1 -> ../../sdh1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50034417483 -> ../../sde
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50034417483-part1 -> ../../sde1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c500344457cf -> ../../sdk
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c500344457cf-part1 -> ../../sdk1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c50065bd6fd8 -> ../../sdl
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c50065bd6fd8-part1 -> ../../sdl1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x5000c5007b86b61a -> ../../sdm
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x5000c5007b86b61a-part1 -> ../../sdm1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x50014ee20b9309e8 -> ../../sdf
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x50014ee20b9309e8-part1 -> ../../sdf1
lrwxrwxrwx 1 root root  9 Apr  8 12:00 wwn-0x50024e9203e6b8dd -> ../../sdj
lrwxrwxrwx 1 root root 10 Apr  8 12:00 wwn-0x50024e9203e6b8dd-part1 -> ../../sdj1

Link to comment
Linux 4.14.26-unRAID.
Last login: Sun Apr  8 23:22:40 +0100 2018 on /dev/pts/0.
root@alexserver:~# ls /dev/
aer_inject       input/        md3                 ptyp2   sde   sdm1     stdout@  tty22  tty38  tty53  ttyp1    vcsa2
block/           kmem          mem                 ptyp3   sde1  sg0      tty      tty23  tty39  tty54  ttyp2    vcsa3
bsg/             kmsg          memory_bandwidth    ptyp4   sdf   sg1      tty0     tty24  tty4   tty55  ttyp3    vcsa4
btrfs-control    kvm           mouse@              ptyp5   sdf1  sg10     tty1     tty25  tty40  tty56  ttyp4    vcsa5
bus/             log=          mpt2ctl             ptyp6   sdg   sg11     tty10    tty26  tty41  tty57  ttyp5    vcsa6
char/            loop-control  mpt3ctl             ptyp7   sdg1  sg12     tty11    tty27  tty42  tty58  ttyp6    vfio/
console          loop0         net/                random  sdh   sg2      tty12    tty28  tty43  tty59  ttyp7    vga_arbiter
core@            loop1         network_latency     rtc@    sdh1  sg3      tty13    tty29  tty44  tty6   urandom  vhost-net
cpu/             loop2         network_throughput  rtc0    sdi   sg4      tty14    tty3   tty45  tty60  vcs      xconsole|
cpu_dma_latency  loop3         null                sda     sdi1  sg5      tty15    tty30  tty46  tty61  vcs1     zero
disk/            loop4         port                sda1    sdj   sg6      tty16    tty31  tty47  tty62  vcs2
fd@              loop5         ppp                 sdb     sdj1  sg7      tty17    tty32  tty48  tty63  vcs3
full             loop6         ptmx                sdb1    sdk   sg8      tty18    tty33  tty49  tty7   vcs4
fuse             loop7         ptp0                sdc     sdk1  sg9      tty19    tty34  tty5   tty8   vcs5
hpet             mapper/       pts/                sdc1    sdl   shm/     tty2     tty35  tty50  tty9   vcs6
hwrng            md1           ptyp0               sdd     sdl1  stderr@  tty20    tty36  tty51  ttyS0  vcsa
initctl|         md2           ptyp1               sdd1    sdm   stdin@   tty21    tty37  tty52  ttyp0  vcsa1

 

Link to comment
  • trurl pinned this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.