No Disk Volume [solved]

[uelpenich]

Hello,
I got a new NWSP2 with an 1TByte disk, and set it up as described (Version 11). It boots but unfortunetely it has no volume to share.
There were no error messages while setting up the disk. Also an update to Version 12 was possible.
Maybe an automount feature was a little bit boring and resposible for a mistake I didn't mention.:

This is the partition list.

Code: Select all

root@SPD8020-Base:/ # fdisk /dev/sda

The number of cylinders for this disk is set to 121601.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          64      514048+ 83 Linux
/dev/sda2              65         128      514080  83 Linux
/dev/sda3             129         192      514080  82 Linux swap
/dev/sda4             193      121601   975217792+  5 Extended
/dev/sda5             193         292      803218+ 83 Linux
/dev/sda6             293         293        8001  83 Linux
/dev/sda7             294         357      514048+ 83 Linux
/dev/sda8             358      121601   973892398+ 83 Linux


The partition SDA8 is not mounted, there is no /share/1000 directory.
The df command shows

Code: Select all

root@SPD8020-Base:/ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root               198368    137868     50260  73% /
/dev/sda2               198368    137868     50260  73% /
/dev/sda5               790556     17556    764968   2% /rw_fs
tmpfs                      200        60       140  30% /rw_fs/tmp/usr/var
/dev/root               198368    126024     62104  67% /lacie-boot
root@SPD8020-Base:/ #


There is a boot.log file but I am not able to type it (boot.log: not found).

Do you have any idea what to do?

Werner

[bozo29]

Try this:

- download "gparted" from this location: http://gparted.sourceforge.net/download.php
- burn the 'iso' on cd and boot with it.
- delete all partition that you are created before and partitioning the hdd in that mod:

Assume the disk is known as /dev/sda and create the following partition on it:

sda1 - primary - 512MB / ext3 >> (here write fvdw-sl firmware)
sda2 - primary - 512MB / ext3 >> (here write fvdw-sl firmware)
sda3 - primary - 512MB / swap
-----------------------------
sda4 - extended - rest of hdd
sda5 - 785MB / ext3 >> (here write the files in the tar ball sda5-lacie-nwsp.tar.gz)
sda6 - 7MB / unformated >> (here write UIMAGE-26xyz-NWSP2CL-n - compressed linux kernel image)
sda7 - 512MB / ext3 >> (here write fvdw-sl firmware)
sda8 - rest of hdd / ext3

Besides the partitioning proceed with the installation just as the tutorial says.

I'm not sure if this will solve your problem but you have nothing to lose.
I have done so and to me it worked.

[uelpenich]

Thank you for the hint to use GParted to partition the disc, now it works.
My only explanation is an unexpected automount of some of the partitions, that the following operations took place on a wrong place.
Regarding the "Advanced Format" discussion in the other forum I think it is a good idea to use the GParted "align to cylinder" option.

[fvdw]

the partitions are not auto mounted but by using explicit mount commands
But if it can not find the partition of course it will not be mounted. The partition table in your first post looks normal to me. The list the content of a file in Linux using the command line you must use the command "cat" (Not type)

Code: Select all

cat boot.log

ps You must be in the directory of the file if you only use the file name, if you are not then you must specify the path to it as well (cat /boot.log)

Why it did not work the first time is difficult to say maybe you made a mistake in writing the files to the different partitions. I think it must have been a problem with sda5. There the nas database is present. if it can not read that during boot then it will complete boot but with failures such as not mounting sda8 as the data partition to mount is specified in the database