Bug#590105: Same problem on LS-WSGL
Benjamin Cama
thanks
Hi,
Contrary to what the bug title says, Sébastien didn't really want
support for LS-CHL at first, but rather fix its disks not being
recognized. As Antonios says, this disk controller problem also happen
on LS-WTGL, and I confirm it on LS-WSGL too (with the latest installer
from
http://people.debian.org/~joeyh/d-i/armel/images/daily/orion5x/network-console/buffalo/lspro/ with 2.6.37-1), both of which are supported by current (2.6.32) kernel, at least. So I am reopening this bug. If someone think a new bug should be opened, please tell me.
The relevant logs are (same on both .32 and .37):
[ 29.544309] sata_mv sata_mv.0: version 1.28
[ 29.549592] sata_mv sata_mv.0: slots 32 ports 2
[ 29.560892] scsi0 : sata_mv
[ 29.566986] scsi1 : sata_mv
[ 29.571302] ata1: SATA max UDMA/133 irq 29
[ 29.575414] ata2: SATA max UDMA/133 irq 29
[ 29.926337] ata1: SATA link down (SStatus 0 SControl 300)
[ 30.436355] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.476402] ata2.00: ATA-8: SAMSUNG HM500LI, 2TF00_00, max UDMA7
[ 30.482417] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth
31/32)
[ 30.526422] ata2.00: configured for UDMA/133
[ 30.531398] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HM500LI
2TF0 PQ: 0 ANSI: 5
[ 30.690100] sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 30.702478] sd 1:0:0:0: [sda] Write Protect is off
[ 30.707342] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.707664] sd 1:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 31.218218] sda: sda1 sda2 sda4 < sda5 sda6 >
[ 31.229352] sd 1:0:0:0: [sda] Attached SCSI disk
[ 41.447884] ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action
0x6 frozen
[ 41.447925] ata2: edma_err_cause=00000020 pp_flags=00000003,
SError=00180000
[ 41.447971] ata2: SError: { 10B8B Dispar }
[ 41.448031] ata2: hard resetting link
[ 41.796329] ata2: SATA link down (SStatus 0 SControl 300)
[ 46.796286] ata2: hard resetting link
[ 47.146330] ata2: SATA link down (SStatus 0 SControl 300)
[ 47.146389] ata2: limiting SATA link speed to 1.5 Gbps
[ 52.145849] ata2: hard resetting link
[ 52.496081] ata2: SATA link down (SStatus 0 SControl 310)
[ 52.496139] ata2.00: disabled
[ 52.496208] ata2: EH complete
[ 52.496270] ata2.00: detaching (SCSI 1:0:0:0)
[ 52.501243] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 52.519709] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 52.519765] sd 1:0:0:0: [sda] Stopping disk
[ 52.519905] sd 1:0:0:0: [sda] START_STOP FAILED
[ 52.519934] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
I read here http://marc.info/?l=linux-ide&m=129113801605282&w=3 that it
may be a timing issue. This is only a workaround I think, and this bug
should be properly fixed, but I think it may help for now. But I don't
know how to test that fix…
Regards,
benjamin
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Benjamin Cama
> The relevant logs are (same on both .32 and .37):
And the result of hw-report for my NAS:
uname -a: Linux debian 2.6.37-1-orion5x #1 Thu Feb 17 07:03:57 UTC 2011
armv5tel GNU/Linux
lsmod: Module Size Used by
lsmod: sd_mod 30360 0
lsmod: crc_t10dif 1134 1 sd_mod
lsmod: sata_mv 23263 0
lsmod: libata 145360 1 sata_mv
lsmod: scsi_mod 145935 2 sd_mod,libata
lsmod: mv643xx_eth 22590 0
lsmod: inet_lro 4980 1 mv643xx_eth
df: Filesystem 1K-blocks Used Available Use% Mounted on
df: tmpfs 62912 4 62908 0% /dev
free: total used free shared
buffers
free: Mem: 125828 22956 102872 0
0
free: Swap: 0 0 0
free: Total: 125828 22956 102872
/proc/cmdline: console=ttyS0,115200 root=/dev/sda2=rw panic=5
BOOTVER=1.23 tftpboot=yes
/proc/cpuinfo: Processor : Feroceon rev 0 (v5l)
/proc/cpuinfo: BogoMIPS : 266.24
/proc/cpuinfo: Features : swp half thumb fastmult edsp
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 5TEJ
/proc/cpuinfo: CPU variant : 0x0
/proc/cpuinfo: CPU part : 0x926
/proc/cpuinfo: CPU revision : 0
/proc/cpuinfo:
/proc/cpuinfo: Hardware : Buffalo Linkstation Pro/Live
/proc/cpuinfo: Revision : 0000
/proc/cpuinfo: Serial : 0000000000000000
/proc/iomem: 00000000-07ffffff : System RAM
/proc/iomem: 00029000-00389c5f : Kernel text
/proc/iomem: 0038a000-0041ca07 : Kernel data
/proc/iomem: f1011000-f101101f : mv64xxx_i2c.0
/proc/iomem: f1011000-f101101f : mv64xxx_i2c adapter
/proc/iomem: f1012000-f10120ff : serial8250.0
/proc/iomem: f1012000-f101201f : serial
/proc/iomem: f1012100-f10121ff : serial8250.1
/proc/iomem: f1012100-f101211f : serial
/proc/iomem: f1050000-f1050fff : orion-ehci.0
/proc/iomem: f1060900-f10609ff : xor low
/proc/iomem: f1060b00-f1060bff : xor high
/proc/iomem: f1072000-f1073fff : mv643xx_eth.0
/proc/iomem: f1080000-f1084fff : sata base
/proc/iomem: f1090000-f109ffff : regs
/proc/iomem: f10a0000-f10a0fff : orion-ehci.1
/proc/iomem: f2200000-f2201fff : sram
/proc/iomem: f4000000-f403ffff : physmap-flash.0
/proc/iomem: f4000000-f403ffff : physmap-flash.0
/proc/interrupts: CPU0
/proc/interrupts: 0: 7853 orion_irq orion_tick
/proc/interrupts: 3: 280 orion_irq serial
/proc/interrupts: 4: 273 orion_irq serial
/proc/interrupts: 5: 57 orion_irq mv64xxx_i2c
/proc/interrupts: 21: 239 orion_irq eth0
/proc/interrupts: 22: 37 orion_irq mv643xx_eth
/proc/interrupts: 29: 46 orion_irq sata_mv
/proc/interrupts: 30: 2 orion_irq mv_xor.0
/proc/interrupts: 31: 2 orion_irq mv_xor.1
/proc/interrupts: Err: 0
/proc/meminfo: MemTotal: 125828 kB
/proc/meminfo: MemFree: 102872 kB
/proc/meminfo: Buffers: 0 kB
/proc/meminfo: Cached: 10536 kB
/proc/meminfo: SwapCached: 0 kB
/proc/meminfo: Active: 13872 kB
/proc/meminfo: Inactive: 4052 kB
/proc/meminfo: Active(anon): 7392 kB
/proc/meminfo: Inactive(anon): 0 kB
/proc/meminfo: Active(file): 6480 kB
/proc/meminfo: Inactive(file): 4052 kB
/proc/meminfo: Unevictable: 0 kB
/proc/meminfo: Mlocked: 0 kB
/proc/meminfo: SwapTotal: 0 kB
/proc/meminfo: SwapFree: 0 kB
/proc/meminfo: Dirty: 0 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 7412 kB
/proc/meminfo: Mapped: 2632 kB
/proc/meminfo: Shmem: 4 kB
/proc/meminfo: Slab: 2764 kB
/proc/meminfo: SReclaimable: 1076 kB
/proc/meminfo: SUnreclaim: 1688 kB
/proc/meminfo: KernelStack: 432 kB
/proc/meminfo: PageTables: 508 kB
/proc/meminfo: NFS_Unstable: 0 kB
/proc/meminfo: Bounce: 0 kB
/proc/meminfo: WritebackTmp: 0 kB
/proc/meminfo: CommitLimit: 62912 kB
/proc/meminfo: Committed_AS: 15216 kB
/proc/meminfo: VmallocTotal: 868352 kB
/proc/meminfo: VmallocUsed: 260 kB
/proc/meminfo: VmallocChunk: 867580 kB
Martin Michlmayr
> and I confirm it on LS-WSGL too (with the latest installer
LS-WSGL is the LS mini, right?
--
Martin Michlmayr
http://www.cyrius.com/
Benjamin Cama
> LS-WSGL is the LS mini, right?
Yes. I'm using the lspro image thinking it also supports the mini. Then
I'm wondering: does it really support it?
benjamin
Martin Michlmayr
finds your disk properly? (The installer itself won't work; I just
want to know if it boots).
Please send me the complete boot log.
http://merkel.debian.org/~tbm/tmp/kernel/ls-wsgl/
--
Martin Michlmayr
http://www.cyrius.com/
--
Benjamin Cama
> Can you boot the following installer image and see if it boots and
> finds your disk properly? (The installer itself won't work; I just
> want to know if it boots).
It boots and find my disks properly, thanks! I just tried to mount a
partition and ls from it, and it works. BTW, you did not preseed the
image with any parameters, but luckilly I have a serial console access
to the NAS.
> Please send me the complete boot log.
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-5-orion5x (Debian 2.6.32-29)
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sat Dec
11 09:47:14 UTC 2010
[ 0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ),
cr=a0053177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Buffalo Linkstation Mini
[ 0.000000] Clearing invalid memory bank 0KB@0xffffffff
[ 0.000000] Clearing invalid memory bank 0KB@0xffffffff
[ 0.000000] Clearing invalid memory bank 0KB@0xffffffff
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Ignoring unrecognised tag 0x41000403
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 32768
[ 0.000000] free_area_init_node: node 0, pgdat c038a228, node_mem_map
c03f3000
[ 0.000000] Normal zone: 256 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 32512 pages, LIFO batch:7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda2
panic=5 rw BOOTVER=1.23 tftpboot=yes
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536
bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768
bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 121768KB available (3224K code, 573K data, 128K
init, 0K highmem)
[ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:64
[ 0.000000] Console: colour dummy device 80x30
[ 25.770122] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[ 26.009972] Security Framework initialized
[ 26.010018] SELinux: Disabled at boot.
[ 26.010078] Mount-cache hash table entries: 512
[ 26.010801] Initializing cgroup subsys ns
[ 26.010835] Initializing cgroup subsys cpuacct
[ 26.010864] Initializing cgroup subsys devices
[ 26.010892] Initializing cgroup subsys freezer
[ 26.010920] Initializing cgroup subsys net_cls
[ 26.011043] CPU: Testing write buffer coherency: ok
[ 26.012717] devtmpfs: initialized
[ 26.016110] regulator: core version 0.5
[ 26.016592] NET: Registered protocol family 16
[ 26.017736] Orion ID: MV88F5182-A2. TCLK=166666667.
[ 26.019474] lsmini_init: finished
[ 26.023239] bio: create slab <bio-0> at 0
[ 26.024044] vgaarb: loaded
[ 26.025684] Switching to clocksource orion_clocksource
[ 26.037944] NET: Registered protocol family 2
[ 26.038584] IP route cache hash table entries: 1024 (order: 0, 4096
bytes)
[ 26.040712] TCP established hash table entries: 4096 (order: 3, 32768
bytes)
[ 26.041015] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 26.041179] TCP: Hash tables configured (established 4096 bind 4096)
[ 26.041210] TCP reno registered
[ 26.041647] NET: Registered protocol family 1
[ 26.042123] Unpacking initramfs...
[ 26.926166] Freeing initrd memory: 3972K
[ 26.926353] NetWinder Floating Point Emulator V0.97 (double
precision)
[ 26.927131] audit: initializing netlink socket (disabled)
[ 26.927219] type=2000 audit(1.150:1): initialized
[ 26.947341] VFS: Disk quotas dquot_6.5.2
[ 26.948120] Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
[ 26.948477] msgmni has been set to 245
[ 26.950344] alg: No test for stdrng (krng)
[ 26.950691] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 26.950732] io scheduler noop registered
[ 26.950757] io scheduler anticipatory registered
[ 26.950784] io scheduler deadline registered
[ 26.951390] io scheduler cfq registered (default)
[ 26.968170] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 26.969378] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a
16550A
[ 27.308977] console [ttyS0] enabled
[ 27.313477] physmap platform flash device: 00040000 at f4000000
[ 27.319669] Found: SST 39LF020
[ 27.322751] physmap-flash.0: Found 1 x8 devices at 0x0 in 8-bit bank
[ 27.329188] number of JEDEC chips: 1
[ 27.332769] cfi_cmdset_0002: Disabling erase-suspend-program due to
code brokenness.
[ 27.353177] RedBoot partition parsing not available
[ 27.360421] mice: PS/2 mouse device common for all mice
[ 27.366353] i2c /dev entries driver
[ 27.373600] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version
0.6
[ 27.380803] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as
rtc0
[ 27.388256] Registered led device: alarm:red
[ 27.392680] Registered led device: info:amber
[ 27.397254] Registered led device: func:blue:top
[ 27.402023] Registered led device: power:blue:bottom
[ 27.407197] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[ 27.445870] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 27.485877] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[ 27.494836] TCP cubic registered
[ 27.498131] NET: Registered protocol family 17
[ 27.502620] VFP support v0.3: not present
[ 27.507498] registered taskstats version 1
[ 27.513426] rtc-rs5c372 0-0032: setting system clock to 2153-07-18
18:36:18 UTC (1497182882)
[ 27.521901] Initalizing network drop monitor service
[ 27.527100] Freeing init memory: 128K
[ 28.199201] input: gpio-keys
as /devices/platform/gpio-keys/input/input0
[ 28.560532] MV-643xx 10/100/1000 ethernet driver version 1.4
[ 28.566969] mv643xx_eth smi: probed
[ 28.605925] SCSI subsystem initialized
[ 28.623946] net eth0: port 0 with MAC address 00:1d:73:4c:3b:c1
[ 28.937592] libata version 3.00 loaded.
[ 29.133440] sata_mv sata_mv.0: version 1.28
[ 29.156980] sata_mv sata_mv.0: slots 32 ports 2
[ 29.172342] scsi0 : sata_mv
[ 29.177251] scsi1 : sata_mv
[ 29.181528] ata1: SATA max UDMA/133 irq 29
[ 29.185640] ata2: SATA max UDMA/133 irq 29
[ 29.695815] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 29.735895] ata1.00: ATA-8: SAMSUNG HM500LI, 2TF00_00, max UDMA7
[ 29.741912] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth
31/32)
[ 29.786051] ata1.00: configured for UDMA/133
[ 29.791058] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM500LI
2TF0 PQ: 0 ANSI: 5
[ 30.305822] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.345902] ata2.00: ATA-8: SAMSUNG HM500LI, 2TF00_00, max UDMA7
[ 30.351921] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth
31/32)
[ 30.396049] ata2.00: configured for UDMA/133
[ 30.401056] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HM500LI
2TF0 PQ: 0 ANSI: 5
[ 30.525332] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 30.534169] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 30.545219] sd 0:0:0:0: [sda] Write Protect is off
[ 30.550094] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.550702] sd 1:0:0:0: [sdb] Write Protect is off
[ 30.555505] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 30.556145] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.577226] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.589885] sda:
[ 30.592234] sdb: sda1 sda2 sda4 < sda5 sda6 >
[ 31.074731] sdb1 sdb2 sdb4 < sdb5
[ 31.097353] sd 0:0:0:0: [sda] Attached SCSI disk
[ 31.106014] sdb6 >
[ 31.120522] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 48.006828] eth0: link up, 100 Mb/s, full duplex, flow control
disabled
Thanks for your work. BTW, what's the fix exactly?
Regards,
benjamin
Martin Michlmayr
> Thanks for your work. BTW, what's the fix exactly?
As you realized yourself in the meantime, you were booting the LS
Pro/Live kernel on the LS Mini, which doesn't work. Fortunately, LS
Mini support is in the kernel in Debian, so I just gave you a kernel
image that loads Mini support.
Anyway, in order to support the LS Mini in Debian and the installer,
we need to add support in flash-kernel, oldsys-preseed,
libdebian-installer and the installer build script. I'll look into
adding that.
> BTW, you did not preseed the image with any parameters, but luckilly
> I have a serial console access to the NAS.
Thanks for pointing this out.
--
Martin Michlmayr
http://www.cyrius.com/
--
Benjamin Cama
> Fortunately, LS
> Mini support is in the kernel in Debian, so I just gave you a kernel
> image that loads Mini support.
OK, thanks. I just checked out the mach-type setting for kernel images
here http://buffalo.nas-central.org/wiki/Buffalo_ARM9_Kernel_Port
It's sad it isn't autodetected. Still, I managed to install Debian via
the installer with your image, and these tweaks.
> Anyway, in order to support the LS Mini in Debian and the installer,
> we need to add support in flash-kernel, oldsys-preseed,
> libdebian-installer and the installer build script. I'll look into
> adding that.
I can help for that. I have serial console access and I'm ready to try
different builds. BTW, there's nothing to flash (appart from kernel boot
prameters) on the Mini as the kernel is loaded directly from the disk
(images must be present on both sda1 and sdb1, on an ext2/3 FS).
I'm still trying to figure out the correct uboot-envtools (fw_setenv)
parameters to change the bootargs from Debian.
Regards,
benjamin
Martin Michlmayr
> I can help for that. I have serial console access and I'm ready to try
> different builds. BTW, there's nothing to flash (appart from kernel boot
> prameters) on the Mini as the kernel is loaded directly from the disk
> (images must be present on both sda1 and sdb1, on an ext2/3 FS).
Can you please file a wishlist bug on oldsys-preseed to support this
device?
It would also be great if you could check out oldsys-preseed from git:
git://git.debian.org/git/d-i/oldsys-preseed
and send a patch.
Looks at the code that is there for the LS Pro already. Can this be
adapted for the Mini? Does the Mini use ext2/3 of XFS by default?
(The LS Pro uses XFS, which we cannot read in Debian.)
Anyway, please don't respond here (since this bug is really about a
different machine) but open a new bug on oldsys-preseed.
--
Martin Michlmayr
http://www.cyrius.com/
--
Benjamin Cama
Version: 3.11
Severity: wishlist
X-Debbugs-CC: Martin Michlmayr <t...@cyrius.com>
Here is a first try at supporting the Buffalo Linkstation Mini (aka
LS-WSGL) for d-i, in response to advices from Martin Michlmayr.
Le mardi 01 mars 2011 à 18:33 +0000, Martin Michlmayr a écrit :
> Can you please file a wishlist bug on oldsys-preseed to support this
> device?
Right here.
> It would also be great if you could check out oldsys-preseed from git:
> git://git.debian.org/git/d-i/oldsys-preseed
> and send a patch.
Here is a first try; I don't know what other file to modify. Is there
something to do in tests/arm/?
diff --git a/oldsys-preseed b/oldsys-preseed
index ac97cd3..9a64f50 100755
--- a/oldsys-preseed
+++ b/oldsys-preseed
@@ -153,14 +153,15 @@ case "`archdetect`" in
fi
umount $path/rootfs || true
rmdir $path/rootfs $path || true
- elif echo "$machine" | grep -q "^Buffalo Linkstation Pro/Live"; then
+ elif echo "$machine" | grep -q "^Buffalo Linkstation Pro/Live" ||
+ echo "$machine" | grep -q "^Buffalo Linkstation Mini"; then
# the default filesystem for the system partition is XFS, which isn't included
# in our startup environment. However, customized boxes might have ext3
# instead, so try to mount anyway.
- rootdev=/dev/sda2
path=/tmp/oldsys-preseed
mkdir -p $path/rootfs
- mount -o ro $rootdev $path/rootfs || true
+ mount -o ro /dev/sda2 $path/rootfs ||
+ mount -o ro /dev/md1 $path/rootfs || true
INTERFACE=eth0
parse_unix_tree $path/rootfs
info=$path/rootfs/etc/melco/info
Furthermore, I don't really see the point with what "unset_matching_var"
does, but the naming scheme for the Mini is indeed the same (i.e. MAC
appended to the hostname).
Please note that I didn't actually tested this code on the device; I
don't know how to test all this d-i stuff.
> Looks at the code that is there for the LS Pro already. Can this be
> adapted for the Mini? Does the Mini use ext2/3 of XFS by default?
> (The LS Pro uses XFS, which we cannot read in Debian.)
The Mini use XFS as rootfs too, but /boot is ext3 (which is not of
interest here for oldsys-preseed, but may help for further support of
the Mini). So, I don't really see a point in preseeding it too, as
people having enough skill customizing their box would rather use some
other parameters, IMHO (I didn't even use the original system on this
device, I directly installed Debian; which means that I may not be able
to test all that "backward checking" stuff)
BTW, the uboot command-line tell the kernel the root is on /dev/sda2,
but I'm quite sure the real root is /dev/md1 which is the software RAID1
device formed by /dev/sda2 and /dev/sdb2. All the informations found on
http://buffalo.nas-central.org/wiki/LS_Mini:_Serial_Port_Output_-_Boot-Log
made me realize that the root fs is /dev/root on the original firmware,
which doesn't help here, but I think the initrd may indeed use /dev/sda2
as a "single" FS (is it even possible if the device is used as a part of
a md array?) before pivot/switching root to the md1 array.
Hope this helps.
Regards,
benjamin
Martin Michlmayr
> Here is a first try at supporting the Buffalo Linkstation Mini (aka
> LS-WSGL) for d-i, in response to advices from Martin Michlmayr.
Thanks, I applied the patch. Sorry for the delay.
--
Martin Michlmayr
http://www.cyrius.com/
--