schreibman Posted January 14 Share Posted January 14 (edited) As indicated, after reboot no pool devices recognized. Causes Docker fail, img/apps on a pool device. Reboot/ Poweroff tried. no luck. The devices show unmounted in unassigned devices, but fail if I try to mount through the gui: Jan 14 12:36:12 Tower unassigned.devices: Error: Device '/dev/sdw1' mount point 'hd36pool' - name is reserved, used in the array or a pool, or by an unassigned device. Jan 14 12:36:12 Tower unassigned.devices: Disk with serial 'ST18000NE000-3G6101_ZVT0JX4D', mountpoint 'hd36pool' cannot be mounted. Jan 14 12:36:18 Tower unassigned.devices: Error: Device '/dev/sdac1' mount point 'hd36pool' - name is reserved, used in the array or a pool, or by an unassigned device. Jan 14 12:36:18 Tower unassigned.devices: Disk with serial 'ST18000NM000J-2TV103_ZR59ZJJV', mountpoint 'hd36pool' cannot be mounted. Jan 14 12:36:21 Tower unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme' - name is reserved, used in the array or a pool, or by an unassigned device. Jan 14 12:36:21 Tower unassigned.devices: Disk with serial 'Sabrent_SB-RKT4P-2TB_48790469800627', mountpoint 'nvme' cannot be mounted. Jan 14 12:36:26 Tower unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme' - name is reserved, used in the array or a pool, or by an unassigned device. Jan 14 12:36:26 Tower unassigned.devices: Disk with serial 'Sabrent_SB-R Also, can only access GUI 'terminal, SSH fails 'target machine refuses.' any help appreciated / diagnostics of course attached 🙂 tower-diagnostics-20240114-1349.zip Edited January 14 by schreibman add Quote Link to comment
JorgeB Posted January 15 Share Posted January 15 Stop the array, re-assign the pool devices to their original slots and post new diags after array start. Quote Link to comment
schreibman Posted January 15 Author Share Posted January 15 done. thanks tower-diagnostics-20240115-1354.zip Quote Link to comment
JorgeB Posted January 16 Share Posted January 16 Not sure why they became unassigned, but all 3 are mounting now, so should all be good. P.S. you are having macvlan call traces, these can hang the server, you should changer docker network to ipvlan. Quote Link to comment
Solution schreibman Posted January 21 Author Solution Share Posted January 21 On 1/16/2024 at 4:16 AM, JorgeB said: P.S. you are having macvlan call traces, these can hang the server, you should changer docker network to ipvlan. aGREED! done! all resolved. Quote Link to comment
Recommended Posts
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.