lost sdb1

Booting, installing, newbie
Message
Author
User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

lost sdb1

#1 Post by drspastic »

i am running puppeee 1.0 on eeepc 701.
i have removed other devices but sd card sdb1 is not seen.
it is seen if i boot without loading save file.

here is dmesg:


# dmesg
Initializing cgroup subsys cpuset
Linux version 2.6.33.2celeron (root@seashell) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #12 PREEMPT Tue Jun 29 22:00:27 EDT 2010
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f780000 (usable)
BIOS-e820: 000000001f780000 - 000000001f790000 (ACPI data)
BIOS-e820: 000000001f790000 - 000000001f7d0000 (ACPI NVS)
BIOS-e820: 000000001f7d0000 - 000000001f7de000 (reserved)
BIOS-e820: 000000001f7e0000 - 000000001f800000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
last_pfn = 0x1f780 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-DFFFF uncachable
E0000-EFFFF write-through
F0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask FE0000000 write-back
1 base 01F800000 mask FFF800000 uncachable
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
PAT not supported by CPU.
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 00000000000e4000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000001f780000 (usable)
modified: 000000001f780000 - 000000001f790000 (ACPI data)
modified: 000000001f790000 - 000000001f7d0000 (ACPI NVS)
modified: 000000001f7d0000 - 000000001f7de000 (reserved)
modified: 000000001f7e0000 - 000000001f800000 (reserved)
modified: 00000000fee00000 - 00000000fee01000 (reserved)
modified: 00000000fff80000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 01800000
init_memory_mapping: 0000000000000000-000000001f780000
0000000000 - 0000400000 page 4k
0000400000 - 001f400000 page 2M
001f400000 - 001f780000 page 4k
kernel direct mapping tables up to 1f780000 @ 14000-19000
RAMDISK: 1f68a000 - 1f77f694
ACPI: RSDP 000fbe60 00014 (v00 ACPIAM)
ACPI: RSDT 1f780000 00034 (v01 A M I OEMRSDT 01000804 MSFT 00000097)
ACPI: FACP 1f780200 00081 (v01 A M I OEMFACP 01000804 MSFT 00000097)
ACPI: DSDT 1f780400 05F2B (v01 A0797 A0797000 00000000 INTL 20051117)
ACPI: FACS 1f790000 00040
ACPI: APIC 1f780390 00068 (v01 A M I OEMAPIC 01000804 MSFT 00000097)
ACPI: OEMB 1f790040 00046 (v01 A M I AMI_OEM 01000804 MSFT 00000097)
ACPI: MCFG 1f786330 0003C (v01 A M I OEMMCFG 01000804 MSFT 00000097)
0MB HIGHMEM available.
503MB LOWMEM available.
mapped low ram: 0 - 1f780000
low ram: 0 - 1f780000
node 0 low ram: 00000000 - 1f780000
node 0 bootmap 00015000 - 00018ef0
(8 early reservations) ==> bootmem [0000000000 - 001f780000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00015ecc60] TEXT DATA BSS ==> [0001000000 - 00015ecc60]
#2 [001f68a000 - 001f77f694] RAMDISK ==> [001f68a000 - 001f77f694]
#3 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
#4 [00015ed000 - 00015f31f4] BRK ==> [00015ed000 - 00015f31f4]
#5 [0000010000 - 0000014000] ACPI WAKEUP ==> [0000010000 - 0000014000]
#6 [0000014000 - 0000015000] PGTABLE ==> [0000014000 - 0000015000]
#7 [0000015000 - 0000019000] BOOTMAP ==> [0000015000 - 0000019000]
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x0001f780
HighMem 0x0001f780 -> 0x0001f780
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0001f780
On node 0 totalpages: 128783
free_area_init_node: node 0, pgdat c15497c0, node_mem_map c15f5200
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3951 pages, LIFO batch:0
Normal zone: 975 pages used for memmap
Normal zone: 123825 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x808
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
Allocating PCI resources starting at 1f800000 (gap: 1f800000:df600000)
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 127776
Kernel command line: initrd=/initrd.gz BOOT_IMAGE=/vmlinuz
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
allocated 2577600 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Initializing HighMem for node 0 (00000000:00000000)
Memory: 501032k/515584k available (3670k kernel code, 14056k reserved, 1754k data, 308k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfffe5000 - 0xfffff000 ( 104 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xdff80000 - 0xff7fe000 ( 504 MB)
lowmem : 0xc0000000 - 0xdf780000 ( 503 MB)
.init : 0xc154d000 - 0xc159a000 ( 308 kB)
.data : 0xc1395877 - 0xc154c368 (1754 kB)
.text : 0xc1000000 - 0xc1395877 (3670 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:16
Console: colour VGA+ 80x25
console [tty0] enabled
Fast TSC calibration using PIT
Detected 630.107 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 1260.21 BogoMIPS (lpj=2520428)
Mount-cache hash table entries: 512
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
mce: CPU supports 5 MCE banks
Performance Events: p6 PMU driver.
... version: 0
... bit width: 32
... generic registers: 2
... value mask: 00000000ffffffff
... max period: 000000007fffffff
... fixed-purpose events: 0
... event mask: 0000000000000003
CPU: Intel(R) Celeron(R) M processor 900MHz stepping 08
Checking 'hlt' instruction... OK.
ACPI: Core revision 20091214
ACPI: setting ELCR to 0200 (from 0ca8)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using PIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
ACPI: EC: GPE = 0x18, I/O: command/status = 0x66, data = 0x62
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x1f810000-0xffffffff] (ignored)
pci 0000:00:02.0: reg 10: [mem 0xf7f00000-0xf7f7ffff]
pci 0000:00:02.0: reg 14: [io 0xec00-0xec07]
pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
pci 0000:00:02.0: reg 1c: [mem 0xf7ec0000-0xf7efffff]
pci 0000:00:02.1: reg 10: [mem 0xf7f80000-0xf7ffffff]
pci 0000:00:1b.0: reg 10: [mem 0xf7eb8000-0xf7ebbfff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20: [io 0xe400-0xe41f]
pci 0000:00:1d.1: reg 20: [io 0xe480-0xe49f]
pci 0000:00:1d.2: reg 20: [io 0xe800-0xe81f]
pci 0000:00:1d.3: reg 20: [io 0xe880-0xe89f]
pci 0000:00:1d.7: reg 10: [mem 0xf7eb7c00-0xf7eb7fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
pci 0000:00:1f.0: quirk: [io 0x0800-0x087f] claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
pci 0000:00:1f.0: LPC Generic IO decode 1 PIO at 0380-03ff
pci 0000:00:1f.2: reg 10: [io 0x0000-0x0007]
pci 0000:00:1f.2: reg 14: [io 0x0000-0x0003]
pci 0000:00:1f.2: reg 18: [io 0x0000-0x0007]
pci 0000:00:1f.2: reg 1c: [io 0x0000-0x0003]
pci 0000:00:1f.2: reg 20: [io 0xffa0-0xffaf]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
pci 0000:00:1c.0: PCI bridge to [bus 04-04]
pci 0000:03:00.0: reg 10: [mem 0xfbfc0000-0xfbffffff 64bit]
pci 0000:03:00.0: reg 30: [mem 0xfbfa0000-0xfbfbffff pref]
pci 0000:03:00.0: PME# supported from D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [mem 0xfbf00000-0xfbffffff]
pci 0000:01:00.0: reg 10: [mem 0xfbef0000-0xfbefffff 64bit]
pci 0000:00:1c.2: PCI bridge to [bus 01-02]
pci 0000:00:1c.2: bridge window [mem 0xf8000000-0xfbefffff]
pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf6ffffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P6._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12 14 15)
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
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
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
hpet clockevent registered
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [mem 0xfed13000-0xfed19fff] has been reserved
system 00:08: [io 0x0380-0x0383] has been reserved
system 00:08: [io 0x04d0-0x04d1] has been reserved
system 00:08: [io 0x0800-0x087f] has been reserved
system 00:08: [io 0x0480-0x04bf] has been reserved
system 00:08: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:08: [mem 0xfed20000-0xfed8ffff] has been reserved
system 00:08: [mem 0xfff00000-0xffffffff] could not be reserved
system 00:09: [mem 0xfec00000-0xfec00fff] has been reserved
system 00:09: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:0a: [mem 0xe0000000-0xefffffff] has been reserved
system 00:0b: [mem 0xe0000000-0xefffffff] has been reserved
system 00:0c: [mem 0x00000000-0x0009ffff] could not be reserved
system 00:0c: [mem 0x000c0000-0x000cffff] could not be reserved
system 00:0c: [mem 0x000e0000-0x000fffff] could not be reserved
system 00:0c: [mem 0x00100000-0x1f7fffff] could not be reserved
pci 0000:00:1c.0: BAR 8: assigned [mem 0x20000000-0x201fffff]
pci 0000:00:1c.0: BAR 9: assigned [mem 0x20200000-0x203fffff 64bit pref]
pci 0000:00:1c.1: BAR 9: assigned [mem 0x20400000-0x205fffff 64bit pref]
pci 0000:00:1c.0: BAR 7: assigned [io 0x1000-0x1fff]
pci 0000:00:1c.1: BAR 7: assigned [io 0x2000-0x2fff]
pci 0000:00:1c.2: BAR 7: assigned [io 0x3000-0x3fff]
pci 0000:00:1c.0: PCI bridge to [bus 04-04]
pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
pci 0000:00:1c.0: bridge window [mem 0x20000000-0x201fffff]
pci 0000:00:1c.0: bridge window [mem 0x20200000-0x203fffff 64bit pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0x2000-0x2fff]
pci 0000:00:1c.1: bridge window [mem 0xfbf00000-0xfbffffff]
pci 0000:00:1c.1: bridge window [mem 0x20400000-0x205fffff 64bit pref]
pci 0000:00:1c.2: PCI bridge to [bus 01-02]
pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff]
pci 0000:00:1c.2: bridge window [mem 0xf8000000-0xfbefffff]
pci 0000:00:1c.2: bridge window [mem 0xf0000000-0xf6ffffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 05-05]
pci 0000:00:1e.0: bridge window [io disabled]
pci 0000:00:1e.0: bridge window [mem disabled]
pci 0000:00:1e.0: bridge window [mem pref disabled]
pci 0000:00:1c.0: enabling device (0104 -> 0107)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
pci 0000:00:1c.0: PCI INT A -> Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: enabling device (0106 -> 0107)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
pci 0000:00:1c.1: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: enabling device (0106 -> 0107)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
pci 0000:00:1c.2: PCI INT C -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
pci_bus 0000:04: resource 0 [io 0x1000-0x1fff]
pci_bus 0000:04: resource 1 [mem 0x20000000-0x201fffff]
pci_bus 0000:04: resource 2 [mem 0x20200000-0x203fffff 64bit pref]
pci_bus 0000:03: resource 0 [io 0x2000-0x2fff]
pci_bus 0000:03: resource 1 [mem 0xfbf00000-0xfbffffff]
pci_bus 0000:03: resource 2 [mem 0x20400000-0x205fffff 64bit pref]
pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfbefffff]
pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf6ffffff 64bit pref]
pci_bus 0000:05: resource 3 [io 0x0000-0xffff]
pci_bus 0000:05: resource 4 [mem 0x00000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
PCI: CLS 16 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 981k freed
Scanning for low memory corruption every 60 seconds
HugeTLB registered 4 MB page size, pre-allocated 0 pages
squashfs: version 4.0 (2009/01/31) Phillip Lougher
NTFS driver 2.1.29 [Flags: R/O].
fuse init (API version 7.13)
aufs 2-standalone.tree-33-20100329
msgmni has been set to 980
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: AC Adapter [AC0] (off-line)
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
ACPI: Lid Switch [LID]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
ACPI: Sleep Button [SLPB]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button [PWRF]
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
Marking TSC unstable due to TSC halts in idle
Switching to clocksource hpet
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (52 C)
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 915GM Chipset
agpgart-intel 0000:00:00.0: detected 7932K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
pci 0000:00:02.0: setting latency timer to 64
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
brd: module loaded
loop: module loaded
ahci 0000:00:1f.2: version 3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ahci 0000:00:1f.2: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
ahci 0000:00:1f.2: PCI INT B disabled
ahci: probe of 0000:00:1f.2 failed with error -22
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ehci_hcd 0000:00:1d.7: PCI INT A -> Link[LNKH] -> GSI 3 (level, low) -> IRQ 3
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 16 is not supported
ehci_hcd 0000:00:1d.7: irq 3, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.33.2celeron ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKH] -> GSI 3 (level, low) -> IRQ 3
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 3, io base 0x0000e400
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.33.2celeron uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 7, io base 0x0000e480
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.33.2celeron uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 10, io base 0x0000e800
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.33.2celeron uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 5, io base 0x0000e880
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.33.2celeron uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
hub 5-0:1.0: USB hub found
hub 5-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 berry_charge
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input5
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f]
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
lib80211_crypt: registered algorithm 'TKIP'
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input6
ata2.00: CFA: SILICONMOTION SM223AC, , max UDMA/66
ata2.00: 7815024 sectors, multi 0: LBA
ata2.00: configured for UDMA/66
ACPI: Battery Slot [BAT0] (battery present)
scsi 1:0:0:0: Direct-Access ATA SILICONMOTION SM n/a PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 7815024 512-byte logical blocks: (4.00 GB/3.72 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Attached SCSI disk
Freeing unused kernel memory: 308k freed
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: New USB device found, idVendor=0951, idProduct=1606
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 1-5: Product: UB6225
usb 1-5: Manufacturer: ENE
usb 1-5: SerialNumber: 146030377350
scsi2 : usb-storage 1-5:1.0
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Synaptics Touchpad, model: 1, fw: 6.3, id: 0x180b1, caps: 0xa04753/0x200000
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7
usb-storage: device scan complete
scsi 2:0:0:0: Direct-Access USB2.0 CardReader SD0 0100 PQ: 0 ANSI: 0
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended

EXT4-fs (sda1): mounted filesystem with ordered data mode
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda1): mounted filesystem with ordered data mode
EXT4-fs (loop1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (loop1): mounted filesystem with ordered data mode
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro1 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro2 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_z 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro4 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro5 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro6 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro7 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro8 0/0/0755, 0/0/01777
aufs test_add:248:mount[1705]: uid/gid/perm /pup_ro9 0/0/0755, 0/0/01777
udevd version 124 started
Atheros(R) L2 Ethernet Driver - version 2.2.3
Copyright (c) 2007 Atheros Corporation.
atl2 0000:03:00.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
atl2 0000:03:00.0: setting latency timer to 64
cfg80211: Calling CRDA to update world regulatory domain
ath5k 0000:01:00.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
ath5k 0000:01:00.0: setting latency timer to 64
ath5k 0000:01:00.0: registered as 'phy0'
HDA Intel 0000:00:1b.0: PCI INT A -> Link[LNKA] -> GSI 5 (level, low) -> IRQ 5
HDA Intel 0000:00:1b.0: setting latency timer to 64
ath: EEPROM regdomain: 0x60
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x60
phy0: Selected rate control algorithm 'minstrel'
Registered led device: ath5k-phy0::rx
Registered led device: ath5k-phy0::tx
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
eeepc_laptop: Eee PC Hotkey Driver
eeepc_laptop: Hotkey init flags 0x41
eeepc_laptop: Get control methods supported: 0x101701
input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input8
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
wlan0: direct probe to AP 94:0c:6d:a2:46:b8 (try 1)
wlan0: direct probe to AP 94:0c:6d:a2:46:b8 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 94:0c:6d:a2:46:b8 (try 1)
wlan0: authenticated
wlan0: associate with AP 94:0c:6d:a2:46:b8 (try 1)
wlan0: RX AssocResp from 94:0c:6d:a2:46:b8 (capab=0x21 status=0 aid=2)
wlan0: associated
chrome[17865]: segfault at cef60354 ip cef60354 sp cef60354 error 5


i note the card and reader show here (8 gig sd)

how do i fix this? i want to keep my save file.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#2 Post by PaulBx1 »

I've never had a lot of luck with sd cards in Puppy. Sometimes it is visible on the desktop, other times not. I've never been able to mount it. After a while I gave up on the things.

Maybe you could compare your dmesg not using the pupsave, with the dmesg while using it. Might tell you something...

Bruce B

Re: lost sdb1

#3 Post by Bruce B »

drspastic wrote:i am running puppeee 1.0 on eeepc 701.
i have removed other devices but sd card sdb1 is not seen.
it is seen if i boot without loading save file.
The way it reads to me, it does see, recognize sdb and sdb1

You should try different APCI settings

pci=use_crs

Maybe later cgroup_disable=memory

Of course run e2fsck as needed

And, most important is: Where is the Puppy save file?

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

here is a more complete run down of howit happened

#4 Post by drspastic »

on the eeepc i keep puppeee 1.0 installed on sda1 the internal ssd and a clone of it on sdb1 (ok, i didnt update it as often as i should have, hence wanting to keep the sda1 save file!) this gives me a good level of redundancy in case of disaster: i can always boot and load save file from sdb1 instead.

the point at which it screwed up was when i removed the sd card and booted into lupu 511 from a usb flash drive and used the pc to install lupu to another external usb hard drive i later needed to wipe and replace xp on a friends machine (xp 0, lupu 1: spreadin tha word)

when i was in lupu, without my sd card in (to avoid loading save file) the usb flash became sdb1, sda1 was still sda1, and the usb hdd was sdc1.

all went ok and i shut down with the menu (didnt separately dismount sdb1 cos i was running from it)

when i rebooted into my usual config puppeee from the sda1 ssd and replaced the usual sd card in its slot, only sda1 came up in the desktop icon, pmount, and even gparted.

i dont fully understand the outputs from dmesg except that it tells what is in the computer regardless of the state of the os.... yeah?

its a major block to my learning that i need explaining to me the route by which the os finds, identifies and mounts a drive. i know it must be something to to with the /mnt or /dev directories.

as i am converting a lot of people to puppy from slow windoze it is important i know the process, reason, and correct cure to this common issue.

Bruce B

Re: here is a more complete run down of howit happened

#5 Post by Bruce B »

drspastic wrote: i dont fully understand the outputs from dmesg except that it tells what is
in the computer regardless of the state of the os.... yeah?
Few people fully understand everything, I sure don't. Be easy on yourself,
operating system 'mastery' is a huge task, one that can take years.

Worse it's an impossible task, because even if you understood everything, it
would change tomorrow.
drspastic wrote:its a major block to my learning that i need explaining
to me the route by which the os finds, identifies and mounts a drive. i know
it must be something to to with the /mnt or /dev directories.
Understandable. I leave a USB 500GB drive plugged in always. And it always
has the same Linux device letter/number assignment.

However, if I plug and unplug USB devices when Linux is running, it
changes device letter/number assignments.

First, let's figure out what is what and how it is recognized after the computer is booted.

We use the command line utility fdisk with the lowercase -L switch, like this:

fdisk -l

Here is my output:

Code: Select all

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        1216     9765625    c  W95 FAT32 (LBA)
/dev/hda2            1216        2432     9765625   83  Linux
/dev/hda3            2432        3648     9765625   83  Linux
/dev/hda4            3648        9729    48851286    f  W95 Ext'd (LBA)
/dev/hda5            3648        4864     9765625    c  W95 FAT32 (LBA)
/dev/hda6            4864        6079     9765624+   c  W95 FAT32 (LBA)
/dev/hda7            6079        7295     9765624+   c  W95 FAT32 (LBA)
/dev/hda8            7295        8511     9765624+   c  W95 FAT32 (LBA)
/dev/hda9            8511        9727     9765624+   7  HPFS/NTFS

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9726    78124063+   7  HPFS/NTFS
/dev/sda2            9727       24315   117186142+  83  Linux
/dev/sda3           24316       42558   146536897+   7  HPFS/NTFS
/dev/sda4           42559       60801   146536897+  83  Linux
This utility can tell you a lot. If you need specific help about mounting and
testing the supposed missing partition and device, then post what fdisk
shows
.

Maybe we can find it and test both the partition and the pup save file.

And of course mount it as needed.

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

fdisk

#6 Post by drspastic »

Disk /dev/sda: 4001 MB, 4001292288 bytes
255 heads, 63 sectors/track, 486 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 486 3903763+ 83 Linux

Bruce B

#7 Post by Bruce B »

drspastic,

The first thing we want to do is check the filesystem integrity.

We are not checking the drive, sda. We are checking the partition which is
sda1. We always check the partitions unmounted.

e2fsck -f /dev/sda1

After it is checked and cleaned you can mount it to use it and check the
pup_save file.

I'll presume names for sake of example, you will need to use actual names.

To mount sda1

mount -t ext3 /dev/sda1 /mnt/sda1

Where ext3 is the format type. It may be ext4 in your case?? Where
/mnt/sda1 is an actual directory. Where /dev/sda1 is the actual partition

Next to check the pup_save file

e2fsck -f /mnt/sda1/xyz/pup_save.2fs

You need to make /mnt/sda1/xyz/pup_save.2fs
correspond with the true name.

Then I suppose you'll have more questions, but I don't know what.

Good luck.

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

fdisk -l

#8 Post by drspastic »

# fdisk -l

Disk /dev/sda: 4001 MB, 4001292288 bytes
255 heads, 63 sectors/track, 486 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 486 3903763+ 83 Linux

Disk /dev/sdc: 300.0 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 36481 293033601 7 HPFS/NTFS
#




no mention of sdb but as you can see, i attached an external usb drive and it picked up as sdc....which is normal.

TBC

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

#9 Post by drspastic »

# e2fsck -f /mnt/sda1/eeesave-puppeee_1.3fs
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: No such file or directory while trying to open /mnt/sda1/eeesave-puppeee_1.3fs

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#10 Post by Béèm »

Try with fsck instead of e2fsck
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

getting nowhere fast

#11 Post by drspastic »

# e2fsck /dev/sda1
e2fsck 1.41.9 (22-Aug-2009)
Superblock last mount time (Tue Nov 9 22:36:37 2010,
now = Tue Nov 9 20:40:07 2010) is in the future.
Fix<y>? yes

Superblock last write time (Tue Nov 9 22:36:38 2010,
now = Tue Nov 9 20:40:07 2010) is in the future.
Fix<y>? yes

/dev/sda1: clean, 98/244320 files, 270315/975940 blocks
# fsck /dev/sda1
fsck 1.41.9 (22-Aug-2009)
e2fsck 1.41.9 (22-Aug-2009)
/dev/sda1: clean, 98/244320 files, 270315/975940 blocks
# fsck mnt/sda1/eeesave-puppeee_1.3fs
fsck 1.41.9 (22-Aug-2009)
#

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#12 Post by Béèm »

Are you sure there is a device still in the PC which could be eventually sdb1.
As per you initial post, you said that you removed devices.
Also your first fdisk -l only shows one device.
I am afraid you are chasing a phantom.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

#13 Post by drspastic »

ok, i just reanamed the sda1 save file cos puppy cant mount 2 save files with the same name. then i copied /dev from the working system on sdb to the mounted savefile on sda1.
now going to reboot and see if it has repaired the problem.

interested to know about checking filesystems on ext3 on disk and within shrunken filesystems.

thanks for all the help so far...fingers crossed

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#14 Post by Béèm »

Your explanations aren't very clear.
How can you copy from a device, which you claim doesn't exist.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

#15 Post by drspastic »

ok, i will recap:
i have the same os installed on sda1 and sdb1. this is how i always do it as backup.

i can choose at boot what savefile to load, if any.

loading from the savefile on sda1 results in the problem that i have been describing: ie sdb1 does not appear, other than in the output of dmesg several posts above.
as it was suggested to try checking the filesystem of sda1 and the shunken filesystem within the savefile on sda1 and they must be unmounted to do this, i booted loading the savefile i keep on sdb1.
this savefile works ok and gives me sda1 and sdb1 (of course then sdb1 cannot be unmounted)
i use this known good system as a reference and to copy that /dev across to sda1 savefile.
did i mention that both sda1 and sdb1 have frugal installs?

until this fault first occured there was no problems with my setup and it is very stable. time to time after i change my setup or install new software on sda1 savefile (the one i usually boot from) and i am confident the system has remained stable, i copy the savefile from sda1 to sdb1, thus i have a clone of a perfect system on sd card incase there arises a problem on the internal ssd due to ...well whatever.

the only way this setup can fail is if both the ssd and sd card screw up at the same time!

now i know it will take seconds to restore my system to a previous good state by booting and loading sdb1 savefile then copying it to sda1 to replace the defective savefile there, but the point is that i want to see this through to a logical conclusion as to why the system failed and to repair it.

as far as i can deduce the linux kernel can see all the drives fine but the filesystem is damaged after being confused with the external usb devices and order i plugged them in.

my purpose here on the forum is to learn from you guys with more experience.

rokytnji
Posts: 2262
Joined: Tue 20 Jan 2009, 15:54

#16 Post by rokytnji »

sdb1 have frugal installs?
I was not sure on how to reply till you mentioned that. What it sounds like is what happened to my AntiX 8.5 frugal persistent install on my 4 gig SD card one time when it was unmounted improperly.

What I did to fix it was. I had to insert the card into my Ubuntu 10.04 LTS IBM M57 Desktop with a USB to SD adapter. Then when it mounted. Looked in Gparted and card showed it was maxed out with written Data.

I umounted it in Gparted using right click menu and then again right clicked in Gparted and ran Check from the Menu. When done and Gparted rescanned the SD card. My partitions (Ext2), / and /data were shrunk from showing as being full of data. Card booted up properly again. Before it would not.
.

I now run AntiX 8.5 Full Iso on my EEEPC 701SD 8 gig SSD and Puppeee 4.X Beta frugal persistent runs on my 4 gig SD card now . Hope that explains what might have happened to you.


Edit: P.S. What I do now is I copy over my personal pupsave over to AntiX /home on internal SSD as a backup. Kinda reverse of what you do

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#17 Post by Béèm »

I still don't get it.
One boot from a partition, not a save file.
One selects a save file or the save file is chosen if it is the only one.

So do you boot from sda1 or sdb1?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

getting close

#18 Post by drspastic »

ok... i always BOOT from sda1....not that i have to, i can boot from sdb1 fine as well.

I select to load save file from sda1 or sdb1, in fact most of my external drives, usb stcks and sd cards have one save file or another, but for these purposes lets just consider sda1 and sdb1 because sda1 is built in ssd and sdb1 is the card that is not seen outside the dmesg output whilst using the savefile stored on sda1. in fact to narrow it down, it is the CARD READER not mountable; diferent sd cards in the slot also are not mounted while using the savefile on sda1.

if i boot without loading ANY save file, the card reader works fine.

the problem therefore lies with the save file on sda1.

I could post it or email it to any interested party with an eeepc 4g surf to try, but it is half a gig in size so not practical.

i can of course examine it live or i can boot pfix=ram and mount it.

as for the suggestion that the sd card was not unmounted clean, i know that problem well from my ubuntu days and usb ntfs drives that i had to mount on a mates xp machine to restore access sometimes after power failures.

i hope i am defining the situation in clearer terms.

i had a similar problem to the one i have now with puppeee rc7 that was resolved by removing an external usb card reader that hogged the designation sdc even when lacking a a card in the slot after many reboots.
i left it plugged into a usb hub and never thought of it as the problem as it had no card.
i just unplugged it and plugged it back in and all was fine.

in this case, the reader is internal, so unplugging IT is not an option.

so what shall i do to locate the fault in the offending save file as regards mounting cards in the internal reader?

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#19 Post by Béèm »

OK, you have a sda1 and a sdb1
You can boot from both.
If you boot from sdb1 with it's save file stored on it can you see sda1 then?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
drspastic
Posts: 90
Joined: Fri 29 Aug 2008, 09:03
Location: ruse, bulgaria

#20 Post by drspastic »

yes and i can boot from any device and load any save file EXCEPT the one that HAPPENS TO RESIDE on sda1 and see all devices and partitions.

as i say, i can boot on sda1 without loading that save file and see sdb1 fine.

booting from sdb1 and loading the save file on sda1, or that same save file copied to ANY device results in sdb1 not appearing anywhere except dmesg.

am i any clearer?

Post Reply