Singularity42 Posted May 31, 2022 Share Posted May 31, 2022 Server went AWOL overnight. CPU processes were maxed out at 99.99%. I resolved that, but the new issue is that I cannot mount my Unassigned disks, where my VM images live: May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write Protect is off May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Mode Sense: 46 00 10 08 May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA May 31 08:25:14 Singularity kernel: sdm: sdm1 May 31 08:25:14 Singularity kernel: sd 1:0:12:0: [sdm] Attached SCSI disk May 31 08:26:21 Singularity emhttpd: Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm) 512 3907029168 May 31 08:26:21 Singularity emhttpd: read SMART /dev/sdm May 31 08:26:32 Singularity unassigned.devices: Disk with ID 'Samsung_SSD_870_S6R4NJ0R607499P_33001438038737393 (sdm)' is not set to auto mount. May 31 09:07:40 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device. May 31 09:08:22 Singularity unassigned.devices: Error: Device '/dev/sdm1' mount point 'Samsung_SSD_' - name is reserved, used in the array or by an unassigned device. Any ideas on how to resolve this? Diagnostics attached, thanks. singularity-flash-backup-20210517-1342.zip Link to comment
JorgeB Posted May 31, 2022 Share Posted May 31, 2022 Please use the existing plugin support thread: Link to comment
Singularity42 Posted May 31, 2022 Author Share Posted May 31, 2022 Ah, was looking for what subforum to use. Is there a move option in Edit, or just delete and repost? Link to comment
Recommended Posts