First, I discourage strongly to use a linear device or a raid0 for storing backup as soon as you will get an issue with one disk, you lose all your backup !
So you should use a raid1.
Currently, you have an issue if you have sdb plugged in an usb port (id issue but I think understand why) and in the other case (esata port) you have at least two issues 1/the firmware think the partition is currently mounted as an USB share (which is wrong) 2/nas database is not updated and there is no setup for your esata disk
Point 1/ is a cosmetic bug (I forgot to remove an always true test I added to check the menu). It is just an informative message
Point 2/
aled72 wrote:Note: the disk is formatted ext4 but the system don't see it.
No, the system sees it, disk and its partitions are listed in /proc/partitions. So no issue on the esata port but only a nas database issue.
So do
- Code: Select all
/etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"
unplug your disk and do
- Code: Select all
echo > /var/log/messages
debugon
plug again your disk, wait around 30'' and do
- Code: Select all
debugoff
cat /var/log/messages
Now for usb case, plug your disk in the usb port and post
- Code: Select all
/etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"
usb_id -x /block/sdb|tr "\n" " "|awk -F '[ =]' '{print $10"-"$14"_"$2"_"$4}'
(I assume its kernel name is still sdb)