Installing firmware and getting root access

[razorpt69]

Hello everyone! As I mentioned in a previous post my NS2 stop appearing on network. I removed the hdd, formatted it, rebuild the partition table and installed what was needed. I can now get the NS2 to appear on the network and can see the first page of the initial setup but I have that problem of "the filesystem on /dev/sda2 is not accepted by the NAS"

I'm now having troubles getting root access (needed to fix that problem). Since I formatted the disk I guess the only options to get root access are:

- Through creating a custom capsule
- Enabling ssh with disassembling (Network space 2)

Since I dont have almost any Linux/programming knowledge I would prefer the disassembling option, because Im not finding it intuitive to create a custom capsule. It would be great if there were already made capsules that I could just download and update the ns2, but I was not able to find them. (My version is 1.2.93)

So I wanted to use the disassembling method. Despite not quite understanding if everything that needs to be done is clearly stated in the guide, I started doing it but when I try to mount the partition sda8 I get the following error:

Code: Select all

root@ubuntu:/home/ubuntu# mount -t ext3 /dev/sda8 /media/ns2 -o rw,data=orderedmount: wrong fs type, bad option, bad superblock on /dev/sda8,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

And I'm stuck. I don't know if it helps but I got the syslog:

Code: Select all

root@ubuntu:/home/ubuntu# dmesg | tail
[ 2610.289327] atkbd serio0: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
[ 2610.289335] atkbd serio0: Use 'setkeycodes e001 <keycode>' to make it known.
[ 2625.783602] EXT4-fs (sda8): mounting ext3 file system using the ext4 subsystem
[ 2625.783764] EXT4-fs (sda8): bad geometry: block count 212832 exceeds size of device (212605 blocks)
[ 2701.273378] EXT4-fs (sda8): mounting ext3 file system using the ext4 subsystem
[ 2701.273543] EXT4-fs (sda8): bad geometry: block count 212832 exceeds size of device (212605 blocks)
[ 3171.219163] atkbd serio0: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
[ 3171.219171] atkbd serio0: Use 'setkeycodes e001 <keycode>' to make it known.
[ 3175.760436] atkbd serio0: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
[ 3175.760444] atkbd serio0: Use 'setkeycodes e059 <keycode>' to make it known.



Also, in the guide its said that with older distros this problem doesnt occur, I wouldnt mind using an older distro and redo the whole thing just to avoid this problem, if someone knows which distro should I use not to have this problem it would also be really helpful

I'm really sorry to bother with this, thanks in advance ;)

[fvdw]

"the filesystem on /dev/sda2 is not accepted by the NAS"

what file system did you put on sda2 ? The lacie firmware needs xfs on sda2 if I remember well

post output of your partition table

Code: Select all

fdisk -l /dev/sda

(assuming sda is the disk of the nwsp2)

about mount issue, apparently you did something more not correct with the partition table or formatting them or putting a wrong files system on sda8
what happens if you just use this

Code: Select all

mount /dev/sda8 /media/ns2

...and on original firmware sda8 is not the partition were the data is stored, that is sda2. On sda8 a part of the firmware is installed.

[razorpt69]

Yes, sda is the disk of the ns2 because Im just running a live cd. The filesystem of sda2 is XFS because when I do the command:

Code: Select all

mkfs -t xfs /dev/sda2

I get:

Code: Select all

root@ubuntu:/home/ubuntu# mkfs -t xfs /dev/sda2
mkfs.xfs: /dev/sda2 appears to contain an existing filesystem (xfs).
mkfs.xfs: Use the -f option to force overwrite.

The partition table is as follows:

Code: Select all

Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63     4016249     2008093+   5  Extended
/dev/sda2         4016250  1953520064   974751907+  83  Linux
/dev/sda5            2111      514079      255984+  82  Linux swap / Solaris
/dev/sda6          516128      530144        7008+  83  Linux
/dev/sda7          532193      546209        7008+  83  Linux
/dev/sda8          548258     2249099      850421   83  Linux
/dev/sda9         2251148     4000184      874518+  83  Linux
/dev/sda10        4002233     4016249        7008+  83  Linux

Finally, tried to mount and created mountpoint first and still doesnt work

Code: Select all

root@ubuntu:/home/ubuntu# mount /dev/sda8 /media/ns2
mount: mount point /media/ns2 does not exist
root@ubuntu:/home/ubuntu# sudo mkdir /media/ns2
root@ubuntu:/home/ubuntu# mount /dev/sda8 /media/ns2
mount: wrong fs type, bad option, bad superblock on /dev/sda8,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[fvdw]

maybe this wiki is helpffull to you, it also mentions the problem with xfs file system not being recognized

http://lacie.nas-central.org/wiki/Insta ... space_2%29

[razorpt69]

maybe this wiki is helpffull to you, it also mentions the problem with xfs file system not being recognized

http://lacie.nas-central.org/wiki/Insta ... space_2%29

That is the guide that I have always followed. And their solution to this problem is first to get root access, which I can't because of the problems I mentioned in the first post.

I would either need:
-Find a solution for this problem I have with getting root with disassembling
-Download a custom capsule from somewhere
-Use an older distro that doesn't create this problem

[fvdw]

-Find a solution for this problem I have with getting root with disassembling

for this you could use our "standalone kernel" part of the the fvdw-sl console that runs under windows and let you upload a kernel that runs from RAM
When that kernel is running you can access the disk and partitions and do what you like. viewtopic.php?f=7&t=1271
This for example to enable root access or check the content of the partitions

However you can do the same thing by taking the disk out and connecting it vi usb-sata interface to a pc running linux.

For the rest I am not an expert in lacie firmware and restoring it, sorry for that