Hi Quentin,This would be an ideal solution however the hardware configuration, in terms of the number of internal drives, is not standard on our units. If the fstab file is fixed then we would encounter a problem if there are fewer than 5 drives in a unit. It is also not feasible to customise the fstab file for each type of configuration as the configuration can change as and when the users desire i.e. a system could have 1 to 4 drives when first setup but then a user may install an additional 4 drives using the Promise card and hence the problem would manifest.
The ideal solution, when taking all the different configurations into consideration, is to facilitate the mapping of the on-board drives first.
Regards, Selvan Quentin Garnier wrote:
On Thu, Mar 27, 2008 at 01:09:41PM +0200, Selvan wrote:Hi Quentin,At startup, the system would boot-off the drive connected to the on-board SATA 0 port, as expected, but during the kernel execution this drive is mapped as wd4 (drives on the Promise card mapped as wd0, wd1, wd2 and wd3). The kernel execution stops at the point where the system is expecting to mount /dev/wd0a and /dev/wd0e, as set in the fstab file, but these partitions don't exist on wd0 but /dev/wd4a and /dev/wd4e exist on wd4.fstab is what needs fixing, then.Quentin Garnier wrote:On Thu, Mar 27, 2008 at 08:49:05AM +0200, Selvan wrote:Hi all,I'm faced with a problem that's proving quite difficult to solve. MyWhy is it a problem?