lacie 5 big network v.1 please support for fvdw

[taetae]

ko mmmm

[Jocko]

So now I understand why fdisk output is empty the kernel doesn't see your disk...

no such device...

Check if your disk is rightly plugged (maybe not !)

If the disk is rightly plugged then there is still an issue with the kernel. (so wait fvdw...)

Note : Indeed the trick to create an empty fstab removes the useless warning :-D and at each NAS reboot you should do it before using the fvdw-sl console features

[taetae]

the minimal kernel is loaded can this be the problem.....

[Jocko]

Yes I think that.

So you must wait fvdw...

But at least you can check if there is no issue with your disk.

So you must get the uboot console and then after rebooting the NAS do

Code: Select all

ide reset

and if there is no error

Code: Select all

ide part

. You must get the partition table of the disk.

So if it's ok then it is a kernel issue.

[fvdw]

to list partitions using fdisk on a disk the command to be used can be

Code: Select all

fdiks -l /dev/sda

(so not only fdisk -l, although this should list all disks found)

The reason why you get the "/etc/fstab" missing error when using mount command is because you did not use the right command, you did not specify the device to be mounted !

It must be like this
create a mountpoint

Code: Select all

mkdir /sda5

mount the partition

Code: Select all

mount /dev/sda5 /sda5

please post dmesg command output when running the standalone kernel

[Jocko]

to list partitions using fdisk the command can be

Code: Select all

fdiks -l /dev/sda

(so not only fdisk -l)

:disapprove it's right for gdisk but not with fdisk

Code: Select all

fdisk -l
Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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      243201  1951969792+  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      243201  1950644398+ 83 Linux

It must be like this
create a mountpoint

Code: Select all

mkdir /sda5

mount the partition

Code: Select all

mount /dev/sda5 /sda5

taetae did already that... See

mountsda5.jpg

and note the error "no such device". So it seems that the device sda is unknown by fdisk and at least sda5 by mount...

[fvdw]

:-D My comment was aiming at just checking sda device.
If you want to see which partitions there are on sda the fdisk -l /dev/sda is then the command to use.
I agree that fdisk -l should list them all.
The fact that this command doesn't give output indicates that are no disk in tatae's 5big1 or fdisk of the medium version of the standalone kernel has a problem.
But I don't think the standalone kernel is the problem
see this post of "toterweb" viewtopic.php?f=30&t=1557#p11498.
He used the fdisk -l command with the standalone kernel and it listed all 5 disks :tapfoot

[fvdw]

Hi tatae you must be doing something wrong

Totorweb tested mounting a partition with the standalone kernel, and it seems to work ok
see here viewtopic.php?f=30&t=1557&p=11594#p11591

:scratch

(did you run it without any disk ?)

[taetae]

there is only the installation disk in slot 1 of the system

standalone 30:

[fvdw]

the command must be

Code: Select all

fdisk -l /dev/sda

anyhow try as well

Code: Select all

fdisk -l /dev/sde

And post the output of

Code: Select all

dmesg

please note that Toterweb has no problems with the standalone kernel to detect the disks
see here viewtopic.php?f=30&t=1557&start=10#p11591