Mageia forum

Perhaps someone can offer an explanation for the following. I've recently had to do a rebuild on this machine. Attached to the machine is a second generation Drobo, USB, storage device. This goes back a bit, to the time when there was a 2TB limit to disk partitions (there still is!). Consequently the drobo has two partitions, labelled "drobo1a" and "drobo1b". The first of nomilnally 2TB and the second, the remainder. These appear in the notifications tray in the usual way, labelled drobo1a and drobo1b. In the long past, they have been mounted on /run/media/rod/drobo..etc. I have both bookmarked in the File Manager, for ease of access. . After the rebuild, however, the two are still in the notification tray, as before, labelled as before, but whilst the bookmark for drobo1a opens up the file system, the that for drobo1b, reports that no file system exists. Eventually, opening them up from the notifications tray, I found that drobo1a is still mounted on /run/media/rod, whilst drobo1b is mounted on /media/windows. For the moment, I've deleted the incorrect bookmark, and established a new on in the current mount point. If anyone has a rational explanation, for this apparently irrational event, I for one, would be pleased to hear it

Was the drobo plugged in during installation of Mageia?
Is drobo1b NTFS?
Did you select an automatic partitioning option during installation?

Automatic partitioning sometimes assumes that an NTFS partition is a Windows partition.

To avoid this either unplug the drobo during installation or use custom partitioning and don't set mount points for the partitions on the drobo.

If you want to keep the mount point for drobo1b as is, then add the nofail option to the fstab line for this partition, otherwise the system may fail to boot if the drobo is not present.

Jim

The drobo lives semi-permanently plugged in, so, most probably it was there on install. Both partitions are formatted NTFS-3G, and in all respects are identical, except for size. Custom partitioning was the option on install. If the installl considered this as a fixed drive, then why did it not mount both? fstab has an entry for the one partition. Presumably, if I delete the entry for that drive, then both will be mounted as removable drives, as they were before