plugout.net

Hi,

I just converted my HDD from ext3 to ext4 filesystem. The data content was backup before this.
After NAS reboot I had to re-define shares and users which worked fine with only one exeption:

A creation of user "gast" wasn't possible. Error message : can not add user, username already exists
A check of the existing user base via SSL does not show the user "gast".

What is wrong ?

P.S. User "guest" is possible but I want it in german ;)

There are several issues

After NAS reboot I had to re-define shares

This should not happen need to deepen it

sers which worked fine with only one exeption:

This is amazing

Can you read the nas data base file (/etc/nas_conf_db.xml) check if there is a node user for gast in the parent nodes <access><users>.

I assume it is not here but it may exist in

Code: Select all

cat /etc/passwd

In this case remove the related line.

And you should be able to recreate it

About convert issue:

There is a file /etc/install-firmware.log

So post it and also boot.log (if you did not yet reboot the nas since the nas rebooting after converting data partition)

Other idea,

This may happen, if the firmware failed to mount the data partition.

So post

Code: Select all

mount

Hi Jocko,

issue 1: No problem to me as data will be erased in any case. On more complex systems this could be complicated.

Issue 2: user "gast" is not in xml database, user "gast" is not in /etc/passwd (that was a surprise to me, but it was there before fs convert. I made a screenshot before doing it)

Another remark in the process ext3 => ext4
Twonky server is disabled (not installed). NFS server is disabled but IÄm not shure if it was enabled. I only use SMB access by Windows PCs
The cronjobs were erased.

So it feld a bit like a fresh installation.

<B>Firmware upgrade step 1 started:</B><br>
Search firmware version information for nwsp2 ...<br>
The latest version available from http://plugout.net is: fvdw-sl 17.0<br><br>
Get the bound upgrade files list<br>
Retrieve the firmware package<br>
Try to download part 1 on 3...<br>
Attempt 1: OK, got successful the firmware package part1 file<br>
Try to download part 2 on 3...<br>
Attempt 1: OK, got successful the firmware package part2 file<br>
Try to download part 3 on 3...<br>
Attempt 1: OK, got successful the firmware package part3 file<br>
Extract firmware package...<br>
OK, extract successful the firmware package<br>
Retrieve kernel image file for kirkwood...<br>
Attempt 1: OK, got successful the kernel image file<br>
<br>OK: Retrieve the latest firmware image file successful<br><br>
<br>=> <B>Firmware upgrade step 2 started:</B><br>
Firmware package uploaded via fvdw-sl server<br>
package type: new configuration (version > 16.1)<br>
Check Image file...
OK<br>
Update basic firmware image for nwsp2 platform, ...
OK<br>
Check kernel version...
new version must be installed<br>
Check DATABASE file...
OK<br>
Check active partition...
OK<br>
Write fs image on /dev/sda2...(please wait)
OK<br>
verify fs ...
OK<br>
Write new kernel image...
OK<br>
Update DATABASE...
OK<br>
switch boot part to upgraded partition...
OK<br>
<br>OK: Firmware upgrade successful<br><br>

start boot log
detect and set platform
nwsp2
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
nwsp2
mount dev/pts
update dev nodes
booting using sda2 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sat Jun 10 19:33:59 CEST 2017
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
create temporary group file
configure loopback network interface
setting reboot and standby
nwsp2
rebootd-nwsp2
nwsp2
standbyd-nwsp2
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Default: [ OK ]
* Finishing mount of volumes... [ OK ]
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... [ OK ]
* Initializing Timezone... [ OK ]
* Starting web server... [ OK ]
* Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ OK ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting DDNS Service... [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
* Starting dropbear... [ OK ]
* Kill temporary dropbear... [ OK ]
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting Disk Temperature Guard... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
* Starting FTP Service... [ OK ]
* Starting NTP client... [ OK ]
* Starting CRON Service... * Starting FTP Service... [ OK ]
[ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 17.0 patched
built on: May 28 2017

LAN IP address: 192.168.178.26 (DHCP)

Port configuration:

LAN -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished

userdel gast =>

root@Lacie-NS2:/ # userdel gast
-sh: userdel: not found

....strange ...

Ouups I made a mistake:
the log file is /etc/.setup.fs/setupjob.log

So about gast account, enable the debug mode

Code: Select all

debugon

try to create the user account
stop debug mode

Code: Select all

debugoff

And post the content of /var/log/messages

About twonky and nfs is logical at you have lost some share settings (technical shares)

So I need to find why you have this behaviour

ote: think to post also the output of the mount command

setupjob.log

<b>Setup task reset.sh is now running</b><br>
Found disk: sda(9XW04EAW) <br>
Format partition sda8 with file system ext4: <br>
=>mke2fs 1.42.11 (09-Jul-2014)
Creating filesystem with 487661099 4k blocks and 121921536 inodes
Filesystem UUID: d53a0390-0713-4a8e-9938-edd418cf2a7b
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Allocating group tables: 0/14883 8547/14883 done
Writing inode tables: 0/14883 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/14883 done

=>Formatting sda8 succeeded<br>
Update partition type on sda8:fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
OK<br>
Remove orphan shares: OK<br>
<b>Setup task reset.sh is ended</b><br>
<br><span style="color:red;">NAS restarting on user's request</span><br>
Restore the regular boot mode...<br>
OK<br></span>
NAS is restarting...OK<br>

!!! Remark: I changed from MBR to GPT