crash boom bang

[medoc]

Hi,

yesterday I noticed that the web interface of my box is unavailable. Transmission and minidlna seemed to work fine.

I couldn't log in via ssh and the button based restart not the shutdown didn't worked. So I plugged the plug. After restart the fsck started. After a while the process stopped and the box was gone again - ssh worked, so I logged in, rebooted from command line.

Fsck again, Stopped once again. I repeated this a few times. Now only one disk was checked (I have two disks), but it ended up in a crash again - probably during step 2.

Now again I'm not able to reach the box via ssh nor web. I'm not home, so I don't have physical access to the box until evening...

Any ideas what can cause this? And how to solve it?

thanks,

medoc

[Joao Cardoso]

On Tuesday, November 13, 2012 7:53:18 AM UTC, medoc wrote:

Hi,

yesterday I noticed that the web interface of my box is unavailable. Transmission and minidlna seemed to work fine.

I couldn't log in via ssh and the button based restart not the shutdown didn't worked. So I plugged the plug. After restart the fsck started. After a while the process stopped and the box was gone again - ssh worked, so I logged in, rebooted from command line.

Fsck again, Stopped once again. I repeated this a few times. Now only one disk was checked (I have two disks), but it ended up in a crash again - probably during step 2.

There are two reasons for fsck to fail:

-Not enough (virtual) memory

   -do you has/had swap active?

   -How was your disks partitioned?

      inherit DLink partition?

      Used Alt-F Disk Wizard?

      Partition manually?

 

-fsck found an error that it could not repair automatically, manual intervention is necessary; in this case partitions should automatically be mounted by Alt-F as read-only

  -what do the logs says? System Log, Boot log... (System->Utilities->View Logs, or use the command 'logread' from the command line

  -If the filesystem is mounted read-only and you have Alt-F packages installed on it, then some problems might arise; is this the case?

[Tomi Szabo]

Everything was default.

After one restart I killed all fsck and the started manually with -v for all 4 partitions (2 disks, 2 partitions each), one after another. Everything went fine, no errors shown.

Then I restarted, box unavailable, not even ping this time. Disk leds not blinking.

Again, I pulled the plug and restarted. Now it checks sda2, but there is a strange message above the status: awk: cmd. line:1: Division by zero.

Filesystem Maintenance

awk: cmd. line:1: Division by zero

Dev.	Label	Operation
sda2		checking...

system.log says:

[...]

Nov 13 19:48:03 malac user.warn kernel: ata1: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata1: SRST failed (errno=-16)
Nov 13 19:48:03 malac user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 19:48:03 malac user.info kernel: ata1.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
Nov 13 19:48:03 malac user.info kernel: ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Nov 13 19:48:03 malac user.info kernel: ata1.00: configured for UDMA/133
Nov 13 19:48:03 malac user.notice kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 13 19:48:03 malac user.debug kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 13 19:48:03 malac user.info kernel:  sda: sda1 sda2 sda4
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Nov 13 19:48:03 malac user.warn kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata2: SRST failed (errno=-16)
Nov 13 19:48:03 malac user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 19:48:03 malac user.info kernel: ata2.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
Nov 13 19:48:03 malac user.info kernel: ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Nov 13 19:48:03 malac user.info kernel: ata2.00: configured for UDMA/133
Nov 13 19:48:03 malac user.notice kernel: scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5
Nov 13 19:48:03 malac user.notice root: Starting urandom: OK.
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off
Nov 13 19:48:03 malac user.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 13 19:48:03 malac user.info kernel:  sdb: sdb1 sdb2 sdb4
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Nov 13 19:48:03 malac user.info kernel: Freeing init memory: 120K
Nov 13 19:48:03 malac user.warn kernel: aufs test_add:253:mount[53]: uid/gid/perm /tmproot/rootsq 0/0/0777, 0/0/0755
Nov 13 19:48:03 malac user.info kernel: Adding 530108k swap on /dev/sda1.  Priority:1 extents:1 across:530108k 
Nov 13 19:48:03 malac user.info kernel: Adding 530108k swap on /dev/sdb1.  Priority:1 extents:1 across:530108k 

[...]

Nov 13 19:48:59 malac user.notice hot: sda4 waiting to be fscked

[...]

boot.log says:

Nov 13 19:47:55 hot: Start fscking sda2
Nov 13 19:47:55 hot: sda4 waiting to be fscked
Nov 13 19:47:57 hot: Start fscking sdb2
Nov 13 19:47:58 hot: sdb4 waiting to be fscked
Nov 13 19:47:58 hot: Finish fscking sdb2: fsck 1.41.14 (22-Dec-2010) /dev/sdb2: clean, 97653/91512832 files, 334394646/366023462 blocks

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To post to this group, send email to al...@googlegroups.com.
To unsubscribe from this group, send email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f?hl=en.
To view this discussion on the web visit https://groups.google.com/d/msg/alt-f/-/yhJoo2uN3M0J.
 
 

[Joao Cardoso]

On Tuesday, November 13, 2012 7:00:57 PM UTC, medoc wrote:

Everything was default.

No. You should state what 'default' if for you, as it certainly is not the same for me.

After one restart I killed all fsck and the started manually with -v for all 4 partitions (2 disks, 2 partitions each), one after another. Everything went fine, no errors shown.

Have you tried to mount the filesystems?

 

Then I restarted, box unavailable, not even ping this time. Disk leds not blinking.

No clue about this... you have a "standard" disk layout, not RAID, right? Are you using a dynamic IP (your router DHCP server) or a static IP? 

 

Again, I pulled the plug and restarted. Now it checks sda2, but there is a strange message above the status: awk: cmd. line:1: Division by zero.

Filesystem Maintenance

awk: cmd. line:1: Division by zero

Dev.	Label	Operation
sda2		checking...

That is a harmless display error, Alt-F is trying to estimate the completion to early and a division by zero happens. Don't worry. You can go to the Status page and refresh it.

 

system.log says:

[...]

Nov 13 19:48:03 malac user.warn kernel: ata1: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata1: SRST failed (errno=-16)

You don't remember if this error happens before, do you?

How old are the drives?

 

Nov 13 19:48:03 malac user.info kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 19:48:03 malac user.info kernel: ata1.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
Nov 13 19:48:03 malac user.info kernel: ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Nov 13 19:48:03 malac user.info kernel: ata1.00: configured for UDMA/133
Nov 13 19:48:03 malac user.notice kernel: scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 13 19:48:03 malac user.debug kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 13 19:48:03 malac user.info kernel:  sda: sda1 sda2 sda4
Nov 13 19:48:03 malac user.notice kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Nov 13 19:48:03 malac user.warn kernel: ata2: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata2: SRST failed (errno=-16)

Again, for the other disk...

 

Nov 13 19:48:03 malac user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 13 19:48:03 malac user.info kernel: ata2.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
Nov 13 19:48:03 malac user.info kernel: ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Nov 13 19:48:03 malac user.info kernel: ata2.00: configured for UDMA/133
Nov 13 19:48:03 malac user.notice kernel: scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD154UI  1AG0 PQ: 0 ANSI: 5
Nov 13 19:48:03 malac user.notice root: Starting urandom: OK.
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off
Nov 13 19:48:03 malac user.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 13 19:48:03 malac user.info kernel:  sdb: sdb1 sdb2 sdb4
Nov 13 19:48:03 malac user.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Nov 13 19:48:03 malac user.info kernel: Freeing init memory: 120K
Nov 13 19:48:03 malac user.warn kernel: aufs test_add:253:mount[53]: uid/gid/perm /tmproot/rootsq 0/0/0777, 0/0/0755
Nov 13 19:48:03 malac user.info kernel: Adding 530108k swap on /dev/sda1.  Priority:1 extents:1 across:530108k 
Nov 13 19:48:03 malac user.info kernel: Adding 530108k swap on /dev/sdb1.  Priority:1 extents:1 across:530108k 

So you have swap active, fsck does not crash because of a lack of memory.

 

[...]

Nov 13 19:48:59 malac user.notice hot: sda4 waiting to be fscked

[...]

boot.log says:

Nov 13 19:47:55 hot: Start fscking sda2
Nov 13 19:47:55 hot: sda4 waiting to be fscked
Nov 13 19:47:57 hot: Start fscking sdb2
Nov 13 19:47:58 hot: sdb4 waiting to be fscked
Nov 13 19:47:58 hot: Finish fscking sdb2: fsck 1.41.14 (22-Dec-2010) /dev/sdb2: clean, 97653/91512832 files, 334394646/366023462 blocks

So sdb2 (probably your left disk) finish checking without problems.

Anything about sda2 fsck completion?

Do you have any Alt-F packages installed? On which disk sda or sdb?

[Tomi Szabo]

On Nov 13, 2012, at 8:35 PM, Joao Cardoso <whoami...@gmail.com> wrote:

No. You should state what 'default' if for you, as it certainly is not the same for me.

then let's stick with I'm not sure :)

I have two 1.5 TB disks installed with swap. If I remember correctly they are not in RAID.

After one restart I killed all fsck and the started manually with -v for all 4 partitions (2 disks, 2 partitions each), one after another. Everything went fine, no errors shown.

Have you tried to mount the filesystems? 

No. I just restarted

Then I restarted, box unavailable, not even ping this time. Disk leds not blinking.

No clue about this... you have a "standard" disk layout, not RAID, right? Are you using a dynamic IP (your router DHCP server) or a static IP? 

Not 100% sure about RAID, only 95%:)

The box has a static, DHCP server assigned (reserved) IP

 

Again, I pulled the plug and restarted. Now it checks sda2, but there is a strange message above the status: awk: cmd. line:1: Division by zero.

That is a harmless display error, Alt-F is trying to estimate the completion to early and a division by zero happens. Don't worry. You can go to the Status page and refresh it.

 

great news:)

system.log says:

[...]

Nov 13 19:48:03 malac user.warn kernel: ata1: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata1: SRST failed (errno=-16)

You don't remember if this error happens before, do you?

How old are the drives? 

Nope. True, I haven't checked it before as there were no problems. They are around 2-3 years old

What is this error? Can it be that the disks wear down?

Nov 13 19:47:55 hot: Start fscking sda2
Nov 13 19:47:55 hot: sda4 waiting to be fscked
Nov 13 19:47:57 hot: Start fscking sdb2
Nov 13 19:47:58 hot: sdb4 waiting to be fscked
Nov 13 19:47:58 hot: Finish fscking sdb2: fsck 1.41.14 (22-Dec-2010) /dev/sdb2: clean, 97653/91512832 files, 334394646/366023462 blocks

So sdb2 (probably your left disk) finish checking without problems.

Anything about sda2 fsck completion?

Do you have any Alt-F packages installed? On which disk sda or sdb?

yep, when I fsckd manually, it finished without a problem

I have a lot of Alt-F packages installed and they are on sda.

[Tomi Szabo]

A quick update:

fsck finished (this was auto fsck, so I don't know if there were errors)

After it finished, the web interface became unaccessible...

I'm still logged into the box via ssh, so have some access.

sda2 was mounted after the process ended, I manually mounted sda4.

There is however no /etc directory... This is also mentioned in the logs with some other interesting lines...

Nov 13 21:10:09 malac user.notice hot: Finish fscking sda2: fsck 1.41.14 (22-Dec-2010) /dev/sda2 was not cleanly unmounted, check forced. /dev/sda2: 

1000619/91512832 files (3.2% non-contiguous), 246733936/366023462 blocks

Nov 13 21:10:09 malac user.notice hot: Users directory found in sda2

Nov 13 21:10:09 malac user.notice hot: Alt-F directory found in sda2

Nov 13 20:10:11 malac daemon.crit sysctrl: sysctrl: open /etc/bay: No such file or directory

Nov 13 20:10:16 malac daemon.crit sysctrl: sysctrl: open /etc/bay: No such file or directory

Nov 13 20:10:18 malac user.notice hot: Start fscking sda4

Nov 13 20:10:18 malac user.notice hot: Finish fscking sda4: fsck 1.41.14 (22-Dec-2010) WARNING: couldn't open /etc/fstab: No such file or directory e

xt2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/sda4 

Nov 13 20:11:33 malac daemon.err inetd[876]: root: no such user

I guess root user is missing due to the fact that /etc is missing and the web interface is gone as inetd is crashed?

[Joao Cardoso]

On Tuesday, November 13, 2012 7:48:29 PM UTC, medoc wrote:

On Nov 13, 2012, at 8:35 PM, Joao Cardoso <whoami...@gmail.com> wrote:

No. You should state what 'default' if for you, as it certainly is not the same for me.

then let's stick with I'm not sure :)

I have two 1.5 TB disks installed with swap. If I remember correctly they are not in RAID.

After one restart I killed all fsck and the started manually with -v for all 4 partitions (2 disks, 2 partitions each), one after another. Everything went fine, no errors shown.

Have you tried to mount the filesystems? 

No. I just restarted

I can only recommend you to repeat the procedure, then try to mount the filesystems and see if the data is all there. Do you know how?

You can also try to boot the box with only one disk attached, at a time, to try to identify if the problem is with any of the disks

You can also try to boot without any disk (you have Alt-F flashed, right?), and then plug (if you dare, I do) one disk at a time

Do you have a linux computer where you can connect the drives?

Then I restarted, box unavailable, not even ping this time. Disk leds not blinking.

No clue about this... you have a "standard" disk layout, not RAID, right? Are you using a dynamic IP (your router DHCP server) or a static IP? 

Not 100% sure about RAID, only 95%:)

The box has a static, DHCP server assigned (reserved) IP

 

Again, I pulled the plug and restarted. Now it checks sda2, but there is a strange message above the status: awk: cmd. line:1: Division by zero.

That is a harmless display error, Alt-F is trying to estimate the completion to early and a division by zero happens. Don't worry. You can go to the Status page and refresh it.

 

great news:)

system.log says:

[...]

Nov 13 19:48:03 malac user.warn kernel: ata1: link is slow to respond, please be patient (ready=0)
Nov 13 19:48:03 malac user.err kernel: ata1: SRST failed (errno=-16)

You don't remember if this error happens before, do you?

How old are the drives? 

Nope. True, I haven't checked it before as there were no problems. They are around 2-3 years old

What is this error? Can it be that the disks wear down?

Don't know. You can try a SMART test, 'smartctl -t short /dev/sda' of even 'smartctl -t long /dev/sda', and when the test finish 'smctl -a /dev/sda' (test also sdb)

[Joao Cardoso]

On Tuesday, November 13, 2012 8:33:14 PM UTC, medoc wrote:

A quick update:

fsck finished (this was auto fsck, so I don't know if there were errors)

After it finished, the web interface became unaccessible...

I'm still logged into the box via ssh, so have some access.

sda2 was mounted after the process ended, I manually mounted sda4.

There is however no /etc directory... This is also mentioned in the logs with some other interesting lines...

Nov 13 21:10:09 malac user.notice hot: Finish fscking sda2: fsck 1.41.14 (22-Dec-2010) /dev/sda2 was not cleanly unmounted, check forced. /dev/sda2: 

1000619/91512832 files (3.2% non-contiguous), 246733936/366023462 blocks

Nov 13 21:10:09 malac user.notice hot: Users directory found in sda2

Nov 13 21:10:09 malac user.notice hot: Alt-F directory found in sda2

Nov 13 20:10:11 malac daemon.crit sysctrl: sysctrl: open /etc/bay: No such file or directory

Nov 13 20:10:16 malac daemon.crit sysctrl: sysctrl: open /etc/bay: No such file or directory

Nov 13 20:10:18 malac user.notice hot: Start fscking sda4

Nov 13 20:10:18 malac user.notice hot: Finish fscking sda4: fsck 1.41.14 (22-Dec-2010) WARNING: couldn't open /etc/fstab: No such file or directory e

xt2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/sda4 

Nov 13 20:11:33 malac daemon.err inetd[876]: root: no such user

I guess root user is missing due to the fact that /etc is missing and the web interface is gone as inetd is crashed?

I think that somehow the 'Alt-F' directory in sda2 (where you have Alt-F packages installed) become corrupted, this is why you don't see /etc.

As files in Alt-F override the ones from the base firmware, if any problem occurs there, then...

You have to remove/rename the 'Alt-F' (notice the case) directory on that filesystem (you will loose all packages files and configuration, so it's better to rename, so you can recover specific configuration files latter)

[Tomi Szabo]

On Nov 13, 2012, at 9:56 PM, Joao Cardoso <whoami...@gmail.com> wrote:

I can only recommend you to repeat the procedure, then try to mount the filesystems and see if the data is all there. Do you know how?

Some more... I was able to mount, it seemed that everything is there.

However. there are 3 partitons on each drive. 1 swap, 1 1.3TB in the size ext2, and another 500MB size ext2.

How can I make sure that there is no RAID?

Also when I mounted sda2 (it automounted actually), there was no /etc dir. It was there on the disk /rootmnt/root/etc, but not at /etc.

You can also try to boot the box with only one disk attached, at a time, to try to identify if the problem is with any of the disks

You can also try to boot without any disk (you have Alt-F flashed, right?), and then plug (if you dare, I do) one disk at a time

I rebooted the box, again, cannot access it. cannot even ping:(

the reboot/shutdown with front button works however.

yep it is flashed. I will try to do it one by one.

Do you have a linux computer where you can connect the drives?

nope. only a mac but it doesn't read it properly. it offers to initialise the disk, which I won't do...

What is this error? Can it be that the disks wear down?

Don't know. You can try a SMART test, 'smartctl -t short /dev/sda' of even 'smartctl -t long /dev/sda', and when the test finish 'smctl -a /dev/sda' (test also sdb)

I'll try that as well.

[Tomi Szabo]

Thanks, renaming worked...:)

Is there any way to recover settings of the packages somehow? README.txt says not to touch anything within the Alt-F dir :)

I guess I have to reinstall the packages with the web interface, right?

But is there any way to restore the configs, or they are gone with the /etc folder?

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To post to this group, send email to al...@googlegroups.com.
To unsubscribe from this group, send email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f?hl=en.

To view this discussion on the web visit https://groups.google.com/d/msg/alt-f/-/i1U32xjoGdUJ.
 
 

[Joao Cardoso]

On Tuesday, November 13, 2012 9:35:05 PM UTC, medoc wrote:

Thanks, renaming worked...:)

Is there any way to recover settings of the packages somehow? README.txt says not to touch anything within the Alt-F dir :)

Yes, but now, after renaming (and rebooting), it does not has special functions anymore, so you can use it.

But not the new Alt-F folder, which will appear after re-installing packages.

I guess I have to reinstall the packages with the web interface, right?

Yes

 

But is there any way to restore the configs, or they are gone with the /etc folder?

The configuration files are yet under '/mnt/sda2/Alt-F-renamed/etc'. (assuming you had packages installed in sda2 probably the right disk)

After re-installing the packages, examine each one of the old configuration files, just to be sure they aren't corrupted, and then

'cp /mnt/sda2/Alt-F-renamed/etc/<conf file> /etc/'.

Yes, to /etc, NOT to /Alt-F/etc or /mnt/sda2/Alt-F/etc.

Of course, if the file is /etc/foo/bar, you should copy from  /mnt/sda2/Alt-F-renamed/etc/foo/bar to /etc//foo/bar

Hope you get the ideia, read this twice :-)

You can check the new Alt-F folder by using the command 'aufs.sh -l', e.g. on my system

# aufs.sh -l

aufs on / type aufs (rw,relatime,si=406222f1)

/mnt/sda4/Alt-F=rw

...

means that Alt-F is using sda4 for packages, and that you should NOT MESS with /mnt/sda4/Alt-F folder (and files and subfolders) directly.

[Tomi Szabo]

On Nov 13, 2012, at 11:02 PM, Joao Cardoso <whoami...@gmail.com> wrote:

But is there any way to restore the configs, or they are gone with the /etc folder?

The configuration files are yet under '/mnt/sda2/Alt-F-renamed/etc'. (assuming you had packages installed in sda2 probably the right disk)

the etc is not a folder but a link to /rootmnt/root/etc which is the flashed version of the etc folder if I'm guessing right...

so I guess then the configs are gone?:(

[Joao Cardoso]

On Tuesday, November 13, 2012 10:13:32 PM UTC, medoc wrote:

On Nov 13, 2012, at 11:02 PM, Joao Cardoso <whoami...@gmail.com> wrote:

But is there any way to restore the configs, or they are gone with the /etc folder?

The configuration files are yet under '/mnt/sda2/Alt-F-renamed/etc'. (assuming you had packages installed in sda2 probably the right disk)

the etc is not a folder but a link to /rootmnt/root/etc

No, it should not be. On my system:

 # ls -l /mnt/sda4/Alt-F/
total 5
lrwxrwxrwx    1 root     root            15 Oct 31 22:41 Backup -> /mnt/md1/Backup
lrwxrwxrwx    1 root     root            15 Oct 25 18:00 Public -> /mnt/md0/Public
-rw-r--r--    1 root     root           115 Nov 13 19:38 README.txt
drwxr-xr-x    3 root     root          1024 Nov 13 19:38 etc
lrwxrwxrwx    1 root     root            13 Nov 13 19:38 ffp -> /mnt/sdb4/ffp
lrwxrwxrwx    1 root     root            14 Nov 13 19:38 home -> /mnt/md0/Users
-rw-r--r--    1 root     root           659 Nov  7 18:15 po
drwxr-xr-x    5 root     root          1024 Sep 14 17:55 usr
drwxr-xr-x    5 root     root          1024 Oct 31 22:41 var

If /mnt/.../Alt-F-renamed/etc is a link, it is wrong, and you lost all your settings. If this is the case, probably all issues started there.

which is the flashed version of the etc folder if I'm guessing right...

Yes,  /rootmnt/root is created from flash, 'df -h' should show it as a tmpfs filesystem (my system is different from a stock RC2, allow for small inaccuracies)

[Tomi Szabo]

On Nov 13, 2012, at 11:25 PM, Joao Cardoso <whoami...@gmail.com> wrote:

the etc is not a folder but a link to /rootmnt/root/etc

No, it should not be. On my system:

well, it is not a link in the newly installed Alt-F in my sys neither :)

If /mnt/.../Alt-F-renamed/etc is a link, it is wrong, and you lost all your settings. If this is the case, probably all issues started there.

but how...? don't remember messing with it.

anyway... thanks for the great support, Joao!

(sent my thanks via paypal too;))