DSM-G600, DNS-3xx and NSA-220 Hack Forum

fonz · 2007-06-12 01:38:48

My file systems suffered a bit under my experiments and it became necessary to run a file system check. Since it's not safe to run e2fsck on mounted volumes, I created a ramdisk that can run e2fsck:

http://www.inreto.de/dns323/fsck/

RAID support is missing (though, mdadm is included). I assume that one should setup RAID before running e2fsck to prevent inconsistencies. If anyone knows how to configure RAID, please let me know.

da_blitz · 2007-06-13 18:35:22

if its RAID 1 you can get away with it but it would be a good idea to not rely on that, emergencies only

the reason is if the 2 contain slightly diffrent data, ie hard drive crash during write or bit rot then there is the chance that you will have 2 diffrent copies, you wont notice it till its too late and only running a raid check will find it

Code:

echo check >> /sys/block/mdX/md/sync_action

for more info look at http://gentoo-wiki.com/HOWTO_Gentoo_Ins … ware_RAID, mainly the stuff at the bottom

fonz · 2007-06-13 21:49:55

thanks for the pointer, I had been reading on the gentoo site before. it's pretty good - i must have missed that.
i"m not running raid, though, so can't test.

Tester · 2007-06-23 10:47:17

to whom it may concern:

I tried it while connected to the the serial interface:

After booting you are not in the correct directory and the path to e2fsck is not set.

go to /opt/sbin and run ./e2fsck /dev/sda2 ...

mmh got always a out of memory error...

Last edited by Tester (2007-06-23 10:59:47)

fonz · 2007-06-23 18:50:05

Then sth is wrong. PATH should be set correctly. The out of memory error is most likely because of missing swap space. If you have a serial console, can you post the boot messages?

Edit: To verify that it's working, I've downloaded my files and ran the commands from the readme file. Works as expected. Is there anything unusual about your setup (like only one disk and such)?

Last edited by fonz (2007-06-23 19:25:39)

Tester · 2007-06-23 20:20:31

Hi Fonz,

thanks for your help:

Got these tail of the reboot log messages, is it enough ?
I have two separate disks installed.

I logged in as root.

scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
Vendor: SAMSUNG Model: SP2504C Rev: VT10
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SAMSUNG Model: HD501LJ Rev: CR10
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
physmap flash device: 800000 at ff800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition definition
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00010000 : "MTD1"
0x00010000-0x00020000 : "MTD2"
0x00020000-0x001a0000 : "Linux Kernel"
0x001a0000-0x007d0000 : "File System"
0x007d0000-0x00800000 : "u-boot"
ehci_platform ehci_platform.20865: EHCI Host Controller
ehci_platform ehci_platform.20865: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.20865: irq 17, io mem 0x00000000
ehci_platform ehci_platform.20865: park 0
ehci_platform ehci_platform.20865: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 5
egiga0: link down
IP-Config: Incomplete network configuration information.
Freeing init memory: 104K
init started: BusyBox v1.6.0 (2007-06-11 19:12:43 CEST) multi-call binary
starting pid 233, tty '': '/etc/rc.d/rc.sysinit'
/etc/rc.d/rc.sysinit:
version 0 swap is no longer supported. Use mkswap -v1 /dev/sda1
swapon: /dev/sda1: Invversion 0 swap is no longer supported. Use mkswap -v1 /dev/sdb1
alid argument
swapon: /dev/sdb1: Invalid argument
Starting /sbin/fanctl.sh...
Starting /usr/sbin/telnetd -l /bin/sh...
OK
Linux 2.6.12.6-arm1_huge
starting pid 257, tty '': '/sbin/getty'
starting pid 258, tty '': '/sbin/getty'

DNS-323 login: root
root
Jun 23 19:10:15 login[257]: root login on 'ttyS0'
~ # free
total used free shared buffers
Mem: 61376 13988 47388 0 0
Swap: 0 0 0
Total: 61376 13988 47388
~ # uname -a
Linux DNS-323 2.6.12.6-arm1_huge #28 Mon Jun 11 21:59:15 CEST 2007 armv5tejl unknown
~ # e2fsck /dev/sda2
-ash: e2fsck: not found

fonz · 2007-06-23 20:43:50

This one is real strange. What firmware did you use when formatting the drives? Did you use these drives with in another Linux computer?

Code:

version 0 swap is no longer supported. Use mkswap -v1 /dev/sda1

This one should look different, too:

Code:

IP-Config: Incomplete network configuration information.

Please look for the kernel command line (in the serial console or in /proc/cmdline when it's running).

You're right about the PATH - but only when you log in on the serial console. I'm always connecting via telnet, the PATH is correct then. But telnet won't work in your case, since the IP autoconfig didn't seem to work.

Anyway. You can still make it work. Set PATH correctly to

Code:

export PATH=/sbin:/usr/sbin:/bin:/usr/bin:/opt/sbin:/opt/bin

And recreate that swap partition. That "version 0" thing is pretty mysterious, though.

Tester · 2007-06-23 21:10:11

Yes, indeed.

I formatted the drives under debian.

Will try to fix the version 0 with recreating.

Perhaps I have to make a clean startup and formatting session.

Thought so, the serial config won't get the new config and exports.

fonz · 2007-06-23 21:15:01

What debian version is it? And what kernel version does it run?

Tester · 2007-06-24 15:22:54

Debian 4 with 2.6.18 I think.

Strange thing with the swap space.
While booting the DNS wants to setup Version 0.
And gives an error to mkswap version 1:

##############
The number of cylinders for this disk is set to 30401.
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)
partitions = 4, sys_ind = 0x82
exit status 0
success
Setting up swapspace version 0, size = 49311744 bytes
version 0 swap is no longer supported. Use mkswap -v1 /dev/sda1
swapon: /dev/sda1: Invalid argument

The number of cylinders for this disk is set to 60801.
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)
partitions = 4, sys_ind = 0x82
exit status 0
success
Setting up swapspace version 0, size = 49311744 bytes
version 0 swap is no longer supported. Use mkswap -v1 /dev/sdb1
swapon: /dev/sdb1: Invalid argument

#################

After defining the swapspace manually: It runs again:
Running filesystem check, check is running okay.

##################
Setting up swapspace version 1, size = 49311744 bytes
# swapon /dev/sda1
Adding 48152k swap on /dev/sda1. Priority:-1 extents:1
# swapon /dev/sdb1
Adding 48152k swap on /dev/sdb1. Priority:-2 extents:1
##################

After typing rebooting with command reboot, it starts again:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

Swapspace gives error again.

fonz · 2007-06-24 15:38:48

"EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended"

I get the same message. Don't know why it still thinks that it's unchecked (maybe it's related to system time).

D-Link firmware sets up swap version 1 here, as expected. Did you mean, you did mkswap -v1, and after reboot it still complains about version 0 swap?

Tester · 2007-06-24 15:49:39

I do not really know.
After a clean DNS firmware boot I got this message:
Especially the message:

Code:

Setting up swapspace version 0, size = 49311744 bytes
version 0 swap is no longer supported. Use mkswap -v1 /dev/sda1

After boot is done, I made deleted the sda1 and sdb1 partitions and made new ones (imho not necessary.)
I made mkswap -v1 /dev/sda1 and swapon.

All works, made a filesystem check with reloading.

Afterwards I made a reboot and again the boot log shows swapspace error.

Code:

The number of cylinders for this disk is set to 30401.
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)
partitions = 4, sys_ind = 0x82
exit status 0
success
Setting up swapspace version 0, size = 49311744 bytes
version 0 swap is no longer supported. Use mkswap -v1 /dev/sda1
swapon: /dev/sda1: Invalid argument

Last edited by Tester (2007-06-24 15:52:37)

fonz · 2007-06-24 15:59:23

If you made new partitions, have you made sure that they have the correct parition type? (83, I think for swap).

btw, 49311744 is only 47MB (as opposed to about 500MB per disk set up by D-Link's firmware).

Tester · 2007-06-24 16:25:00

83 is linux... 82 is linux swap.

yes, i know that is the reason why I formatted the drives manually.

I can't imagine, why this box needed 2 * 500 MB as swap space...
Imho 100 MB should work....

Correct me, if I am totally wrong.

Tester · 2007-06-24 21:51:50

I hate this, copying all away, formatting, copying back....

I recognized that there are 4 partitiions on the new formatted disk.
Perhaps the system copies the swap partition version on sda4 or something.

Now the swap space was added sucessfully.

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2007-06-12 01:38:48

File system checks

#2 2007-06-13 18:35:22

Re: File system checks

Code:

#3 2007-06-13 21:49:55

Re: File system checks

#4 2007-06-23 10:47:17

Re: File system checks

#5 2007-06-23 18:50:05

Re: File system checks

#6 2007-06-23 20:20:31

Re: File system checks

#7 2007-06-23 20:43:50

Re: File system checks

Code:

Code:

Code:

#8 2007-06-23 21:10:11

Re: File system checks

#9 2007-06-23 21:15:01

Re: File system checks

#10 2007-06-24 15:22:54

Re: File system checks

#11 2007-06-24 15:38:48

Re: File system checks

#12 2007-06-24 15:49:39

Re: File system checks

Code:

Code:

#13 2007-06-24 15:59:23

Re: File system checks

#14 2007-06-24 16:25:00

Re: File system checks

#15 2007-06-24 21:51:50

Re: File system checks

Board footer