User's Guide

Linux Setup and Operation 3-19
Notes on access to USB FDD
When you attempt an access by directly specifying an sd device name as described below while a
USB FDD is connected, the device name may be changed due to separation or integration of one of
the PCI modules, which can destroy partition information etc. of other disks unintentionally.
[Example]
If you execute a command for the USB FDD after you integrate one of the PCI modules with the
same sd device name that was specified before the system was separated, partition information etc.
of the disk A is destroyed.
Transition of sd device names
Disk A USB FDD Disk B
Before one of the PCI
modules is separated
sda sdb sdc
After one of the PCI
modules is separated
none sda sdc
After one of the PCI
modules is integrated
sdb sda sdc
1) Before one of the PCI modules is separated
# tar cf /dev/sdb files
→ Files are written in the USB FDD.
2) After one of the PCI modules is integrated
# tar cf /dev/sdb files
→ Files are written in the disk A unintentionally → partitions are destroyed
Note:
It is a feature of NEC Express5800/ft series that the device names of the device files change due
to integration or separation of one of the PCI modules.