Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sat Nov 18, 2017 3:57 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 14 posts ] 
Author Message
PostPosted: Fri Apr 22, 2011 7:35 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
Hi Everyone,

I am running VDR 1.6.0 on my LS HG and I just wanted to update to version 1.7.9. While VDR 1.6.0 uses the DVB modules with API 3.x, the new VDR 1.7.9 needs DVB API 5.0 modules.

My 3.x DVB modules came with kernel 2.6.25.20/v117 which I installed some time ago via André's webinstaller. By checking the kernel headers for 2.6.30.1/v118 I saw that the new kernel version comes with DVB API 5.0 modules, but I have not been able to install the new kernel on my machine.

When running the webinstaller-kernelinst-dryrun.sh, it always downloads the legacy kernel 2.6.25.20 again. Since the output of the script says "Maintainer request (mandatory): legacy kernel package", I took a look into the script and it seems like it has been André's intention to always install the legacy kernel regardless of the user choice (probably for a good reason).

I read through the thread "Kernel 2.6.30.1 (PPC/v118) released", where some users reported problems, but I could not figure out what to do to get the kernel running or why the webinstaller doesn't install the latest kernel.
viewtopic.php?f=11&t=20661&hilit=v118

I tried to just take the DVB modules/headers from the new kernel without installing the kernel itself but that didn't work. I also tried to compile the modules from source myself but that also failed (probably because I don't have the kernel source on the LS).

If anybody knows how to run the webinstaller (without bricking the LS) or where I could obtain the DVB 5.0 modules for my system I would be very happy :).

greetings,
Daniel

ps: if that information has anything to do with it: I have uboot installed.


Top
   
PostPosted: Sat Apr 23, 2011 8:15 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Just go ahead and compile your own kernel on uboot. Personally, I prefer 2.6.32.* (longterm), it has proved very stable here. To get started, download the sources and patches from http://kernel.org/, unpack/apply them, and point a symlink to the sources directory. Now you're ready to compile the kernel with my helper script "kernel.sh", which will take several hours.

ln -s /usr/src/linux-2.6.32 /usr/src/linux
cd /usr/src/
wget http://hvkls.dyndns.org/downloads/tmp/config-2.6.32.39
wget http://hvkls.dyndns.org/downloads/tmp/kernel.sh
cp config-2.6.32.39 linux/.config
sh -x ./kernel.sh

Within the script, you will see a few commented lines. That's the place for the compilation of additional or modified DVB modules, such as the tda18218. You would need additional sources for that.


Top
   
PostPosted: Wed Apr 27, 2011 11:38 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
Hi André,

thank you for the quick answer.
I guess this means you do not recommend me to just edit the webinstaller script to install the latest version. But thanks for the detailed instructions. I will give it a try and let you know about my progress here.

greetings,
Daniel


Top
   
PostPosted: Thu May 12, 2011 11:45 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
Hi André,

I downloaded the kernel and ran the script from your website. The compilation went fine without any problems, unfortunately I didn't have luck when I restarted the LS, as it did not come up after reboot.

Now when the LS starts, I can see uboot counting down for about 10 seconds and afterwards the disk full LED blinks 7 times (1x short, 6x long). After that I can enter the U-boot minimal console by pressing power for one second and can switch between the boot modes as described here. However, I am not able to ping the LS on 192.168.11.150 nor connect using nc.

When choosing boot mode 1, the LS restarts (there is a short moment when windows says the network cable is not connected), the power LED is on for a while, then the LS restarts and returns to uboot + 7 blinks (as described above).
When choosing boot mode 2, the LS restarts, the power LED looks like in U-Boot (but the minimal console does not respond), after a while the LS restarts and returns to uboot + 7 blinks (as described above).
I haven't tried boot mode 3 yet, as I did not want to get into EM mode.

If I don't enter the minimal console after the disk full LED blinks 7 times, a few minutes later, the Diag LED blinks 6 times since avr_evtd has not been started.

Any idea whats going wrong or what those 7 blinks mean? I can put the HDD into a linux machine and check the contents of the disk, please let me know if I should post a particular file.

greetings,
Daniel


Top
   
PostPosted: Fri May 13, 2011 5:52 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
Here is some output I got from putting the disk into another machine, maybe it gives a hint:
Code:
bitserver:/linkstation/boot# ls -o
total 3800
lrwxrwxrwx 1 root      22 2011-05-12 23:03 config -> /boot/config-2.6.32.39
-rw-r--r-- 1 root   70666 2011-05-12 22:50 config-2.6.32.39
-rw-r--r-- 1 root   18011 2006-06-01 08:37 COPYING
-rwx------ 1 root  430080 2007-10-25 07:49 insmod.mipsel
-rwx------ 1 root  143004 2007-10-24 11:15 insmod.ppc
lrwxrwxrwx 1 root      13 2010-11-24 01:00 kurobox.dtb -> kuroboxHD.dtb
-rw-r--r-- 1 root    2371 2011-05-12 23:03 kuroboxHD.dtb
-rw-r--r-- 1 root    2371 2011-05-12 23:03 kuroboxHG.dtb
-rw-r--r-- 1 root    4862 2007-08-04 09:38 loaderHG.o
-rw-r--r-- 1 root    8164 2007-08-29 16:58 loaderII.o
-rw-r--r-- 1 root    4938 2007-08-04 09:38 loaderKB.o
-rw-r--r-- 1 root    5135 2007-08-04 09:38 loaderKG.o
-rw-r--r-- 1 root    5135 2007-08-04 09:38 loaderKO.o
-rw-r--r-- 1 root    5075 2007-08-04 09:38 loaderLS.o
-rw-r--r-- 1 root    4862 2007-06-29 09:24 loaderTS.o
lrwxrwxrwx 1 root      26 2011-05-12 23:03 System.map -> /boot/System.map-2.6.32.39
-rw-r--r-- 1 root  937857 2011-05-12 22:56 System.map-2.6.32.39
-rw-r--r-- 1 root      11 2010-11-24 01:01 try_new_kernel
lrwxrwxrwx 1 root      22 2011-05-12 23:03 uImage -> /boot/uImage-2.6.32.39
-rw-r--r-- 1 root 2218916 2011-05-12 22:56 uImage-2.6.32.39
-rw-r--r-- 1 root       0 2011-04-22 17:03 variant-legacy
-rw-r--r-- 1 root       0 2011-04-22 17:02 variant-uboot
-rw-r--r-- 1 root      16 2008-11-11 19:02 version
lrwxrwxrwx 1 root       6 2010-11-24 01:00 vmlinux.UBoot -> uImage
bitserver:/linkstation/boot# more version
r376-v117-uboot
bitserver:/linkstation/boot# more try_new_kernel
vmlinux.bin
bitserver:/linkstation/boot# ls -o /linkstation/lib/modules/
total 3
drwxr-xr-x 5 root 1024 2003-11-03 15:52 2.4.20_mvl31-ppc_linkstation
drwxr-xr-x 3 root 1024 2011-04-21 22:38 2.6.25.20-svn365-dirty493
drwxr-xr-x 3 root 1024 2011-05-12 23:03 2.6.32.39
bitserver:/linkstation/boot#


I found this thread about a uboot error message which looks somehow similiar:
viewtopic.php?f=41&t=22925
I'll see if I can get a connection with nc.

-Daniel


Top
   
PostPosted: Fri May 13, 2011 7:34 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
one more thing:
When I reassembled the LS and tried to start it again, I realized that the disk seems to boot something after the Disk LED flashes.

The HDD sounds like it is accessed and at a certain point I am able to ping the LS under 192.168.11.150. However, I could not connect via SSH and nmap could not find any open ports. At that time, the Disk LED is constantly flashing and when I hold the power button, the LS shuts down and turns off again after a few seconds.
(I am unsure if I mistook this as avr_evtd error yesterday or if something changed since back then)

So does this mean the boot process stucks at a certain point, before the SSH service is running? Maybe I can take a look into dmesg next time I connect the HDD to a PC. Or could it be possible that the disk simply became full when the new kernel had been installed? (Will check df next time).

-Daniel


Top
   
PostPosted: Fri May 13, 2011 9:34 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Hm, have you ever used fix_ext2_magic?


Top
   
PostPosted: Fri May 13, 2011 9:47 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
andre wrote:
Hm, have you ever used fix_ext2_magic?


Yes, I just used it when I put the drive into the other Linux machine today. Maybe it explains the different behaviour now ?!

-Daniel


Top
   
PostPosted: Sat May 14, 2011 11:44 am 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
This is the contents of /var/log/dmesg. Obviously it boots the new kernel, I can't see whats going wrong.

Code:
Using Buffalo Linkstation machine description
Linux version 2.6.32.39 (root@LinkStation) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #5 Thu May 12 22:55:38 CEST 2011
Found legacy serial port 0 for /soc10x/serial@80004500
  mem=80004500, taddr=80004500, irq=0, clk=130041000, speed=9600
Found legacy serial port 1 for /soc10x/serial@80004600
  mem=80004600, taddr=80004600, irq=0, clk=130041000, speed=57600
bootconsole [udbg0] enabled
Adding PCI host bridge /soc10x/pci@fec00000
PCI host bridge /soc10x/pci@fec00000 (primary) ranges:
  IO 0x00000000fe000000..0x00000000febfffff -> 0x0000000000000000
 MEM 0x0000000080000000..0x00000000efffffff -> 0x0000000080000000
BUFFALO Network Attached Storage Series
(C) 2002-2005 BUFFALO INC.
Top of RAM: 0x8000000, Total RAM: 0x8000000
Memory hole size: 0MB
Zone PFN ranges:
  DMA      0x00000000 -> 0x00008000
  Normal   0x00008000 -> 0x00008000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00008000
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c047dcc8, node_mem_map c04c3000
  DMA zone: 256 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 32512 pages, LIFO batch:7
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 124912k/131072k available (4388k kernel code, 6012k reserved, 248k data, 220k bss, 172k init)
Kernel virtual memory layout:
  * 0xffffe000..0xfffff000  : fixmap
  * 0xfd3fc000..0xfe000000  : early ioremap
  * 0xc9000000..0xfd3fc000  : vmalloc & ioremap
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:512
mpic: Setting up MPIC " EPIC     " version 1.2 at 80040000, max 1 CPUs
mpic: ISU size: 4, shift: 2, mask: 3
mpic: Initializing for 12 sources
time_init: decrementer frequency = 32.522240 MHz
time_init: processor frequency   = 262.144000 MHz
clocksource: timebase mult[7afe256] shift[22] registered
clockevent: decrementer mult[85360a5] shift[32] cpu[0]
Console: colour dummy device 80x25
console [tty0] enabled, bootconsole disabled
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
pci 0000:00:00.0: reg 14 32bit mmio: [0x000000-0x000fff]
pci 0000:00:0b.0: reg 10 io port: [0xbfff00-0xbfffff]
pci 0000:00:0b.0: reg 14 32bit mmio: [0xbffffc00-0xbffffcff]
pci 0000:00:0c.0: reg 10 io port: [0xbffed0-0xbffed7]
pci 0000:00:0c.0: reg 14 io port: [0xbffed8-0xbffedb]
pci 0000:00:0c.0: reg 18 io port: [0xbffee0-0xbffee7]
pci 0000:00:0c.0: reg 1c io port: [0xbffee8-0xbffeeb]
pci 0000:00:0c.0: reg 20 io port: [0xbffef0-0xbffeff]
pci 0000:00:0c.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
pci 0000:00:0e.0: reg 10 32bit mmio: [0xbfffe000-0xbfffefff]
pci 0000:00:0e.0: supports D1 D2
pci 0000:00:0e.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:0e.0: PME# disabled
pci 0000:00:0e.1: reg 10 32bit mmio: [0xbfffd000-0xbfffdfff]
pci 0000:00:0e.1: supports D1 D2
pci 0000:00:0e.1: PME# supported from D0 D1 D2 D3hot
pci 0000:00:0e.1: PME# disabled
pci 0000:00:0e.2: reg 10 32bit mmio: [0xbfffcf00-0xbfffcfff]
pci 0000:00:0e.2: supports D1 D2
pci 0000:00:0e.2: PME# supported from D0 D1 D2 D3hot
pci 0000:00:0e.2: PME# disabled
irq: irq 0 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 16
irq: irq 1 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 17
irq: irq 3 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 18
pci_bus 0000:00: resource 0 io:  [0x00-0xbfffff]
pci_bus 0000:00: resource 1 mem: [0x80000000-0xefffffff]
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource timebase
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
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)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
irq: irq 9 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 19
irq: irq 10 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 20
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 244
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x80004500 (irq = 19) is a 16550A
serial8250.0: ttyS1 at MMIO 0x80004600 (irq = 20) is a 16550A
brd: module loaded
loop: module loaded
pata_it821x: controller in pass through mode.
scsi0 : pata_it821x
scsi1 : pata_it821x
ata1: PATA max UDMA/133 cmd 0xbffed0 ctl 0xbffed8 bmdma 0xbffef0 irq 17
ata2: PATA max UDMA/133 cmd 0xbffee0 ctl 0xbffee8 bmdma 0xbffef8 irq 17
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:00:0b.0: no PCI Express capability
eth0: RTL8110s at 0xc902cc00, 00:0d:0b:99:42:0f, XID 04000000 IRQ 16
netconsole: local port 6666
netconsole: local IP 192.168.11.150
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.11.149
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: device eth0 not up yet, forcing it
r8169: eth0: link down
ata1.00: ATA-8: WDC WD5000AAKB-00H8A0, 05.04E05, max UDMA/133
ata1.00: 976773168 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD5000AAKB-0 05.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: Attached scsi generic sg0 type 0
 sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
r8169: eth0: link up
console [netcon0] enabled
netconsole: network logging started
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:0e.2: EHCI Host Controller
ehci_hcd 0000:00:0e.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0e.2: Enabling legacy PCI PM
ehci_hcd 0000:00:0e.2: irq 18, io mem 0xbfffcf00
ehci_hcd 0000:00:0e.2: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:0e.0: OHCI Host Controller
ohci_hcd 0000:00:0e.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0e.0: irq 18, io mem 0xbfffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:0e.1: OHCI Host Controller
ohci_hcd 0000:00:0e.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:0e.1: irq 18, io mem 0xbfffd000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
usbcore: registered new interface driver ums-alauda
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-isd200
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-karma
usbcore: registered new interface driver ums-onetouch
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
irq: irq 5 on host /soc10x/interrupt-controller@80040000 mapped to virtual irq 21
rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
EDAC MC: Ver: 2.1.0 May 11 2011
TCP cubic registered
NET: Registered protocol family 17
NET4: DECnet for Linux: V.2.5.68s (C) 1995-2003 Linux DECnet Project Team
DECnet: Routing cache hash table of 1024 buckets, 4Kbytes
NET: Registered protocol family 12
registered taskstats version 1
rtc-rs5c372 0-0032: setting system clock to 2011-05-13 21:08:46 UTC (1305320926)
linkstation: disarming the AVR watchdog:
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
Freeing unused kernel memory: 172k init
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
usbcore: registered new interface driver dvb_usb_vp7045


btw. Is it required to use the IP address 192.168.11.149 when trying to connect to the netconsole? (Instead of any other in 192.168.11.*)


Top
   
PostPosted: Sat May 14, 2011 12:04 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Other addresses should be OK.

Your /etc/fstab and /etc/network/interfaces?


Top
   
PostPosted: Sat May 14, 2011 7:38 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
/etc/fstab:
Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>               <dump>  <pass>
/dev/hda1       /               ext3    defaults,noatime,nodiratime,errors=remount-ro      0 0
proc            /proc           proc    defaults                        0 0
none            /dev/pts        devpts  gid=5,mode=20                   0 0
/dev/hda2       swap            swap    defaults                        0 0
/dev/hda3       /mnt            ext3    defaults,noatime,nodiratime     0 0
/mnt/usr        /usr            none    bind                            0 0

/etc/network/interfaces:
Code:
# we always want the loopback interface
#
auto lo
iface lo inet loopback

# default dynamic setup (no adjustment necessary)
#
#auto eth0
#iface eth0 inet dhcp
      hostname `hostname`

# frontalot's static setup (adjust to your network settings)
#
auto eth0
iface eth0 inet static
     address 192.168.11.150
     network 192.168.11.0
     netmask 255.255.255.0
     broadcast 192.168.11.255
     gateway 192.168.11.150

I switched from DHCP to the fixed address yesterday, in order to make sure the LS is pingable at 192.168.11.150 - regardless in which state the LS is. I realized that I just did it halfway (specified a wrong gateway address and did not comment out the hostname line) - wonder if that could cause a problem.


Top
   
PostPosted: Sat May 14, 2011 9:25 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
Hi André,

since you asked me for the fstab I figured out that at some point most users switched from /dev/hd* to /dev/sd*, so I gave that a try. Well, and now the LS boots again and I can ssh into it :up:. However, I still wonder why the disk LED is blinking all the time.

Next I will check if I can get the new VDR running.

thanks for your help!
-Daniel


Top
   
PostPosted: Sun May 15, 2011 10:54 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Here's my /etc/default/avr_evtd, for reference. Check $DISKNAG and $DISKCHECK.

LOG=/var/log
DEBUG=OFF
EMMODE=NO
TIMER=OFF
DEVICE=/dev/ttyS1
SUN-SAT=OFF=01:15,ON=06:20
SHUTDOWN=
POWERON=
DISKCHECK=90
ROOT=sda1
WORK=sda3
REFRESH=40
HOLD=3
DISKNAG=ON
FANSTOP=15


Top
   
PostPosted: Sun May 15, 2011 11:52 pm 
Offline
Newbie

Joined: Tue Aug 15, 2006 6:47 pm
Posts: 14
Location: Germany
I think the problem was that ROOT and WORK were still pointing to /dev/hda. Now it's working again.

-Daniel


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 14 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 9 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited