Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

cannot write to user share

Featured Replies

I'm using unRAID server pro using version 4.2.3

 

This problem started happening after I disabled user level security.

 

Problem description:

I can read from the user share with no problems until i do one of the following:

try to write to the share

try to rename a user share

try to stop the array

 

When i try to write to the share, i get an error saying the share is not accessible, you might not have permission to use this network resource. After this happens or any of the above, I can no longer access the web interface and end up having to hard reboot the server. the server is pingable and i can telnet in and perform functions from the command line.

 

I have tried saving my disk config file and reformatting the flash drive and reinstalling unraid with the same results. I also had one drive that was getting errors, so i removed that drive from the array and left that slot unassigned to see if that was causing the issues, but no luck.

 

Any ideas?

 

Almost always, the first step is to capture and attach your syslog.

To obtain a copy of your current syslog, at the unRAID console or in a Telnet session, type the command:

 

  cp  /var/log/syslog  /boot

 

This will make a copy of the system log in the root directory of your flash drive, which you can either copy directly from the flash share of your server, or plug the flash drive into your PC and access the syslog there.  Any file manager such as Windows Explorer can access the file across the network.  For example, if your unRAID server name is Tower, then you can access your newly created syslog as \\Tower\flash\syslog.  I recommend renaming it with the date and time and the .txt extension, for example syslog2007-08-28-1630.txt.

 

Try to capture the syslog after attempting operations that fail, so we can see any logged messages related to the failures.  It may also help to provide some detail about your hardware setup.

 

  • Author

ASUS P4P800S mainboard

P4 3.0E cpu

1.5GB Kingston ram

Promise Ultra 133TX2

6 western digital 250GB PATA

1 maxtor 250GB PATA

 

After having problems, i have reset everything back to the default configuration.

 

DHCP is enabled (my gateway is 192.168.1.1. i also tried adding the nameserver to resolv.conf and hosts since i read about similar problems on here, but no change. now the everything is back to default)

I currently have 2 usershares

- Media 2, high-water, split-level 2, no restrictions or exclusions

- Storage, high-water, split-level 999, no restriction or exclusions

 

These shares worked in the beginning when i first created them with only 3 drives. After i got my pro key, i added the other drives to the array and started copying large amounts of data to the share. things were going good for a while, then the next morning the copy had almost completed and i had the not accessible error. since then i haven't had much luck writing to the share. at first it was just flaky and worked sometimes, now it hasn't been working at all other than reading.

 

 

Thanks!

  • Author

I copied this log after trying to create a new user share named "Media1". After clicking Add Share, the web interface became non-responsive. Accessing the system via console was fine. i'm not familiar enough to know what services to try and kill and restart to get it operational again.

 

 

Mar 12 09:43:34 Tower syslogd 1.4.1: restart.
Mar 12 09:43:35 Tower kernel: klogd 1.4.1, log source = /proc/kmsg started.
Mar 12 09:43:35 Tower kernel: [    0.000000] Linux version 2.6.22.5 (root@Develop) (gcc version 3.4.6) #9 Fri Sep 14 00:14:18 PDT 2007
Mar 12 09:43:35 Tower kernel: [    0.000000] BIOS-provided physical RAM map:
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 0000000000100000 - 000000004ffb0000 (usable)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 000000004ffb0000 - 000000004ffc0000 (ACPI data)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 000000004ffc0000 - 000000004fff0000 (ACPI NVS)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 000000004fff0000 - 0000000050000000 (reserved)
Mar 12 09:43:35 Tower kernel: [    0.000000]  BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
Mar 12 09:43:35 Tower kernel: [    0.000000] Warning only 896MB will be used.
Mar 12 09:43:35 Tower kernel: [    0.000000] Use a HIGHMEM enabled kernel.
Mar 12 09:43:35 Tower kernel: [    0.000000] 896MB LOWMEM available.
Mar 12 09:43:35 Tower kernel: [    0.000000] Entering add_active_range(0, 0, 229376) 0 entries of 256 used
Mar 12 09:43:35 Tower kernel: [    0.000000] Zone PFN ranges:
Mar 12 09:43:35 Tower kernel: [    0.000000]   DMA             0 ->     4096
Mar 12 09:43:35 Tower kernel: [    0.000000]   Normal       4096 ->   229376
Mar 12 09:43:35 Tower kernel: [    0.000000] early_node_map[1] active PFN ranges
Mar 12 09:43:35 Tower kernel: [    0.000000]     0:        0 ->   229376
Mar 12 09:43:35 Tower kernel: [    0.000000] On node 0 totalpages: 229376
Mar 12 09:43:35 Tower kernel: [    0.000000]   DMA zone: 32 pages used for memmap
Mar 12 09:43:35 Tower kernel: [    0.000000]   DMA zone: 0 pages reserved
Mar 12 09:43:35 Tower kernel: [    0.000000]   DMA zone: 4064 pages, LIFO batch:0
Mar 12 09:43:35 Tower kernel: [    0.000000]   Normal zone: 1760 pages used for memmap
Mar 12 09:43:35 Tower kernel: [    0.000000]   Normal zone: 223520 pages, LIFO batch:31
Mar 12 09:43:35 Tower kernel: [    0.000000] DMI 2.3 present.
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: RSDP 000FAD60, 0014 (r0 ACPIAM)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: RSDT 4FFB0000, 0030 (r1 A M I  OEMRSDT  10000401 MSFT       97)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: FACP 4FFB0200, 0081 (r2 A M I  OEMFACP  10000401 MSFT       97)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: DSDT 4FFB03F0, 3763 (r1  A0049 A0049000        0 INTL  2002026)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: FACS 4FFC0000, 0040
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: APIC 4FFB0390, 005C (r1 A M I  OEMAPIC  10000401 MSFT       97)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: OEMB 4FFC0040, 003F (r1 A M I  OEMBIOS  10000401 MSFT       97)
Mar 12 09:43:35 Tower kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x808
Mar 12 09:43:35 Tower kernel: [    0.000000] Allocating PCI resources starting at 60000000 (gap: 50000000:afb80000)
Mar 12 09:43:35 Tower kernel: [    0.000000] Built 1 zonelists.  Total pages: 227584
Mar 12 09:43:35 Tower kernel: [    0.000000] Kernel command line: initrd=bzroot rootdelay=10 BOOT_IMAGE=bzimage 
Mar 12 09:43:35 Tower kernel: [    0.000000] Enabling fast FPU save and restore... done.
Mar 12 09:43:35 Tower kernel: [    0.000000] Enabling unmasked SIMD FPU exception support... done.
Mar 12 09:43:35 Tower kernel: [    0.000000] Initializing CPU#0
Mar 12 09:43:35 Tower kernel: [    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
Mar 12 09:43:35 Tower kernel: [    0.000000] Detected 3007.088 MHz processor.
Mar 12 09:43:35 Tower kernel: [   54.784804] Console: colour VGA+ 80x25
Mar 12 09:43:35 Tower kernel: [   54.788748] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Mar 12 09:43:35 Tower kernel: [   54.789371] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mar 12 09:43:35 Tower kernel: [   54.803853] Memory: 877216k/917504k available (1752k kernel code, 39800k reserved, 681k data, 156k init, 0k highmem)
Mar 12 09:43:35 Tower kernel: [   54.804001] virtual kernel memory layout:
Mar 12 09:43:35 Tower kernel: [   54.804003]     fixmap  : 0xffff8000 - 0xfffff000   (  28 kB)
Mar 12 09:43:35 Tower kernel: [   54.804004]     vmalloc : 0xf8800000 - 0xffff6000   ( 119 MB)
Mar 12 09:43:35 Tower kernel: [   54.804005]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
Mar 12 09:43:35 Tower kernel: [   54.804006]       .init : 0xc0364000 - 0xc038b000   ( 156 kB)
Mar 12 09:43:35 Tower kernel: [   54.804008]       .data : 0xc02b6282 - 0xc0360780   ( 681 kB)
Mar 12 09:43:35 Tower kernel: [   54.804009]       .text : 0xc0100000 - 0xc02b6282   (1752 kB)
Mar 12 09:43:35 Tower kernel: [   54.804597] Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mar 12 09:43:35 Tower kernel: [   54.954628] Calibrating delay using timer specific routine.. 6016.91 BogoMIPS (lpj=30084592)
Mar 12 09:43:35 Tower kernel: [   54.954828] Mount-cache hash table entries: 512
Mar 12 09:43:35 Tower kernel: [   54.954990] CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000441d 00000000 00000000
Mar 12 09:43:35 Tower kernel: [   54.954997] monitor/mwait feature present.
Mar 12 09:43:35 Tower kernel: [   54.955081] using mwait in idle threads.
Mar 12 09:43:35 Tower kernel: [   54.955170] CPU: Trace cache: 12K uops, L1 D cache: 16K
Mar 12 09:43:35 Tower kernel: [   54.955287] CPU: L2 cache: 1024K
Mar 12 09:43:35 Tower kernel: [   54.955371] CPU: After all inits, caps: bfebfbff 00000000 00000000 0000b180 0000441d 00000000 00000000
Mar 12 09:43:35 Tower kernel: [   54.955377] Intel machine check architecture supported.
Mar 12 09:43:35 Tower kernel: [   54.955466] Intel machine check reporting enabled on CPU#0.
Mar 12 09:43:35 Tower kernel: [   54.955552] CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
Mar 12 09:43:35 Tower kernel: [   54.955641] Compat vDSO mapped to ffffe000.
Mar 12 09:43:35 Tower kernel: [   54.955735] CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 04
Mar 12 09:43:35 Tower kernel: [   54.955889] Checking 'hlt' instruction... OK.
Mar 12 09:43:35 Tower kernel: [   54.994693] ACPI: Core revision 20070126
Mar 12 09:43:35 Tower kernel: [   54.998944] Parsing all Control Methods:
Mar 12 09:43:35 Tower kernel: [   54.999070] Table [DSDT](id 0001) - 510 Objects with 48 Devices 149 Methods 14 Regions
Mar 12 09:43:35 Tower kernel: [   54.999287]  tbxface-0587 [02] tb_load_namespace     : ACPI Tables successfully acquired
Mar 12 09:43:35 Tower kernel: [   54.999489] ACPI: setting ELCR to 0200 (from 0c20)
Mar 12 09:43:35 Tower kernel: [   54.999733] evxfevnt-0091 [02] enable                : Transition to ACPI mode successful
Mar 12 09:43:35 Tower kernel: [   55.000052] NET: Registered protocol family 16
Mar 12 09:43:35 Tower kernel: [   55.000216] ACPI: bus type pci registered
Mar 12 09:43:35 Tower kernel: [   55.000369] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
Mar 12 09:43:35 Tower kernel: [   55.000456] PCI: Using configuration type 1
Mar 12 09:43:35 Tower kernel: [   55.000540] Setting up standard PCI resources
Mar 12 09:43:35 Tower kernel: [   55.010514] evgpeblk-0956 [04] ev_create_gpe_block   : GPE 00 to 1F [_GPE] 4 regs on int 0x9
Mar 12 09:43:35 Tower kernel: [   55.013624] evgpeblk-1052 [03] ev_initialize_gpe_bloc: Found 9 Wake, Enabled 0 Runtime GPEs in this block
Mar 12 09:43:35 Tower kernel: [   55.014215] Completing Region/Field/Buffer/Package initialization:...
Mar 12 09:43:35 Tower kernel: [   55.021838] Initialized 13/14 Regions 42/42 Fields 41/41 Buffers 16/16 Packages (519 nodes)
Mar 12 09:43:35 Tower kernel: [   55.022056] Initializing Device/Processor/Thermal objects by executing _INI methods:.
Mar 12 09:43:35 Tower kernel: [   55.022537] Executed 1 _INI methods requiring 0 _STA executions (examined 52 objects)
Mar 12 09:43:35 Tower kernel: [   55.022760] ACPI: Interpreter enabled
Mar 12 09:43:35 Tower kernel: [   55.022846] ACPI: (supports S0 S1 S3 S4 S5)
Mar 12 09:43:35 Tower kernel: [   55.023151] ACPI: Using PIC for interrupt routing
Mar 12 09:43:35 Tower kernel: [   55.037998] ACPI: PCI Root Bridge [PCI0] (0000:00)
Mar 12 09:43:35 Tower kernel: [   55.038101] PCI: Probing PCI hardware (bus 00)
Mar 12 09:43:35 Tower kernel: [   55.038516] PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
Mar 12 09:43:35 Tower kernel: [   55.038605] PCI quirk: region 0480-04bf claimed by ICH4 GPIO
Mar 12 09:43:35 Tower kernel: [   55.039068] PCI: Transparent bridge - 0000:00:1e.0
Mar 12 09:43:35 Tower kernel: [   55.039178] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Mar 12 09:43:35 Tower kernel: [   55.039381] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
Mar 12 09:43:35 Tower kernel: [   55.050416] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.051060] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.051700] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.052340] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.052978] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Mar 12 09:43:35 Tower kernel: [   55.053729] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.054370] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.055036] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Mar 12 09:43:35 Tower kernel: [   55.055605] Linux Plug and Play Support v0.97 (c) Adam Belay
Mar 12 09:43:35 Tower kernel: [   55.055698] pnp: PnP ACPI init
Mar 12 09:43:35 Tower kernel: [   55.055789] ACPI: bus type pnp registered
Mar 12 09:43:35 Tower kernel: [   55.063779] pnp: PnP ACPI: found 15 devices
Mar 12 09:43:35 Tower kernel: [   55.063866] ACPI: ACPI bus type pnp unregistered
Mar 12 09:43:35 Tower kernel: [   55.064050] SCSI subsystem initialized
Mar 12 09:43:35 Tower kernel: [   55.064188] usbcore: registered new interface driver usbfs
Mar 12 09:43:35 Tower kernel: [   55.064306] usbcore: registered new interface driver hub
Mar 12 09:43:35 Tower kernel: [   55.064425] usbcore: registered new device driver usb
Mar 12 09:43:35 Tower kernel: [   55.064555] PCI: Using ACPI for IRQ routing
Mar 12 09:43:35 Tower kernel: [   55.064641] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
Mar 12 09:43:35 Tower kernel: [   55.068580] pnp: 00:0b: ioport range 0x680-0x6ff has been reserved
Mar 12 09:43:35 Tower kernel: [   55.068668] pnp: 00:0b: ioport range 0x290-0x297 has been reserved
Mar 12 09:43:35 Tower kernel: [   55.068758] pnp: 00:0c: iomem range 0xfed20000-0xfed8ffff has been reserved
Mar 12 09:43:35 Tower kernel: [   55.068846] pnp: 00:0c: iomem range 0xffb00000-0xffbfffff could not be reserved
Mar 12 09:43:35 Tower kernel: [   55.068984] pnp: 00:0d: iomem range 0xfec00000-0xfec00fff has been reserved
Mar 12 09:43:35 Tower kernel: [   55.069072] pnp: 00:0d: iomem range 0xfee00000-0xfee00fff has been reserved
Mar 12 09:43:35 Tower kernel: [   55.069163] pnp: 00:0e: iomem range 0x0-0x9ffff could not be reserved
Mar 12 09:43:35 Tower kernel: [   55.069250] pnp: 00:0e: iomem range 0xc0000-0xdffff could not be reserved
Mar 12 09:43:35 Tower kernel: [   55.069338] pnp: 00:0e: iomem range 0xe0000-0xfffff could not be reserved
Mar 12 09:43:35 Tower kernel: [   55.069426] pnp: 00:0e: iomem range 0x100000-0x4ffeffff could not be reserved
Mar 12 09:43:35 Tower kernel: [   55.074433] Time: tsc clocksource has been installed.
Mar 12 09:43:35 Tower kernel: [   55.099729] PCI: Bridge: 0000:00:01.0
Mar 12 09:43:35 Tower kernel: [   55.099814]   IO window: c000-cfff
Mar 12 09:43:35 Tower kernel: [   55.099900]   MEM window: fe900000-fe9fffff
Mar 12 09:43:35 Tower kernel: [   55.099986]   PREFETCH window: e7f00000-f7efffff
Mar 12 09:43:35 Tower kernel: [   55.100074] PCI: Bridge: 0000:00:1e.0
Mar 12 09:43:35 Tower kernel: [   55.100159]   IO window: d000-dfff
Mar 12 09:43:35 Tower kernel: [   55.100246]   MEM window: fea00000-feafffff

  • Author

broken up because of 20000 character limitation

 

Mar 12 09:43:35 Tower kernel: [   55.100333]   PREFETCH window: 60000000-600fffff
Mar 12 09:43:35 Tower kernel: [   55.100432] PCI: Setting latency timer of device 0000:00:1e.0 to 64
Mar 12 09:43:35 Tower kernel: [   55.100448] NET: Registered protocol family 2
Mar 12 09:43:35 Tower kernel: [   55.194258] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Mar 12 09:43:35 Tower kernel: [   55.194469] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Mar 12 09:43:35 Tower kernel: [   55.195232] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
Mar 12 09:43:35 Tower kernel: [   55.195563] TCP: Hash tables configured (established 131072 bind 65536)
Mar 12 09:43:35 Tower kernel: [   55.195651] TCP reno registered
Mar 12 09:43:35 Tower kernel: [   55.224334] Unpacking initramfs... done
Mar 12 09:43:35 Tower kernel: [   56.445187] Freeing initrd memory: 28921k freed
Mar 12 09:43:35 Tower kernel: [   56.445482] Machine check exception polling timer started.
Mar 12 09:43:35 Tower kernel: [   56.445878] io scheduler noop registered (default)
Mar 12 09:43:35 Tower kernel: [   56.445964] io scheduler anticipatory registered
Mar 12 09:43:35 Tower kernel: [   56.446049] io scheduler deadline registered
Mar 12 09:43:35 Tower kernel: [   56.446139] io scheduler cfq registered
Mar 12 09:43:35 Tower kernel: [   66.425935] 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
Mar 12 09:43:35 Tower kernel: [   66.426136] Boot video device is 0000:01:00.0
Mar 12 09:43:35 Tower kernel: [   66.426360] input: Power Button (FF) as /class/input/input0
Mar 12 09:43:35 Tower kernel: [   66.426447] ACPI: Power Button (FF) [PWRF]
Mar 12 09:43:35 Tower kernel: [   66.426640] input: Power Button (CM) as /class/input/input1
Mar 12 09:43:35 Tower kernel: [   66.426726] ACPI: Power Button (CM) [PWRB]
Mar 12 09:43:35 Tower kernel: [   66.429604] Real Time Clock Driver v1.12ac
Mar 12 09:43:35 Tower kernel: [   66.429706] intel_rng: FWH not detected
Mar 12 09:43:35 Tower kernel: [   66.429796] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Mar 12 09:43:35 Tower kernel: [   66.429933] Hangcheck: Using get_cycles().
Mar 12 09:43:35 Tower kernel: [   66.430019] Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
Mar 12 09:43:35 Tower kernel: [   66.430234] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Mar 12 09:43:35 Tower kernel: [   66.430599] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Mar 12 09:43:35 Tower kernel: [   66.431076] [ACPI Debug]  String: [0x04] "RRIO"
Mar 12 09:43:35 Tower kernel: [   66.431507] pnp: Device 00:08 disabled.
Mar 12 09:43:35 Tower kernel: [   66.431679] Floppy drive(s): fd0 is 1.44M
Mar 12 09:43:35 Tower kernel: [   66.449628] FDC 0 is a post-1991 82077
Mar 12 09:43:35 Tower kernel: [   66.450908] loop: module loaded
Mar 12 09:43:35 Tower kernel: [   66.451427] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
Mar 12 09:43:35 Tower kernel: [   66.451515] PCI: setting IRQ 11 as level-triggered
Mar 12 09:43:35 Tower kernel: [   66.451519] ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
Mar 12 09:43:35 Tower kernel: [   66.453042] PCI: Setting latency timer of device 0000:00:1d.7 to 64
Mar 12 09:43:35 Tower kernel: [   66.453046] ehci_hcd 0000:00:1d.7: EHCI Host Controller
Mar 12 09:43:35 Tower kernel: [   66.453178] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
Mar 12 09:43:35 Tower kernel: [   66.453345] ehci_hcd 0000:00:1d.7: debug port 1
Mar 12 09:43:35 Tower kernel: [   66.453434] PCI: cache line size of 128 is not supported by device 0000:00:1d.7
Mar 12 09:43:35 Tower kernel: [   66.453442] ehci_hcd 0000:00:1d.7: irq 11, io mem 0xfebffc00
Mar 12 09:43:35 Tower kernel: [   66.457400] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Mar 12 09:43:35 Tower kernel: [   66.457649] usb usb1: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   66.457774] hub 1-0:1.0: USB hub found
Mar 12 09:43:35 Tower kernel: [   66.457864] hub 1-0:1.0: 8 ports detected
Mar 12 09:43:35 Tower kernel: [   66.565795] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
Mar 12 09:43:35 Tower kernel: [   66.565846] USB Universal Host Controller Interface driver v3.0
Mar 12 09:43:35 Tower kernel: [   66.566229] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
Mar 12 09:43:35 Tower kernel: [   66.566317] PCI: setting IRQ 10 as level-triggered
Mar 12 09:43:35 Tower kernel: [   66.566321] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
Mar 12 09:43:35 Tower kernel: [   66.566528] PCI: Setting latency timer of device 0000:00:1d.0 to 64
Mar 12 09:43:35 Tower kernel: [   66.566531] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Mar 12 09:43:35 Tower kernel: [   66.566649] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Mar 12 09:43:35 Tower kernel: [   66.566805] uhci_hcd 0000:00:1d.0: irq 10, io base 0x0000ef00
Mar 12 09:43:35 Tower kernel: [   66.567005] usb usb2: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   66.567129] hub 2-0:1.0: USB hub found
Mar 12 09:43:35 Tower kernel: [   66.567217] hub 2-0:1.0: 2 ports detected
Mar 12 09:43:35 Tower kernel: [   66.675855] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
Mar 12 09:43:35 Tower kernel: [   66.675942] ACPI: PCI Interrupt 0000:00:1d.1[b] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Mar 12 09:43:35 Tower kernel: [   66.676147] PCI: Setting latency timer of device 0000:00:1d.1 to 64
Mar 12 09:43:35 Tower kernel: [   66.676151] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Mar 12 09:43:35 Tower kernel: [   66.676269] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Mar 12 09:43:35 Tower kernel: [   66.676422] uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000ef20
Mar 12 09:43:35 Tower kernel: [   66.676619] usb usb3: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   66.676740] hub 3-0:1.0: USB hub found
Mar 12 09:43:35 Tower kernel: [   66.676828] hub 3-0:1.0: 2 ports detected
Mar 12 09:43:35 Tower kernel: [   66.785909] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
Mar 12 09:43:35 Tower kernel: [   66.785996] PCI: setting IRQ 5 as level-triggered
Mar 12 09:43:35 Tower kernel: [   66.786000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
Mar 12 09:43:35 Tower kernel: [   66.786205] PCI: Setting latency timer of device 0000:00:1d.2 to 64
Mar 12 09:43:35 Tower kernel: [   66.786208] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Mar 12 09:43:35 Tower kernel: [   66.786326] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Mar 12 09:43:35 Tower kernel: [   66.786481] uhci_hcd 0000:00:1d.2: irq 5, io base 0x0000ef40
Mar 12 09:43:35 Tower kernel: [   66.786682] usb usb4: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   66.786803] hub 4-0:1.0: USB hub found
Mar 12 09:43:35 Tower kernel: [   66.786892] hub 4-0:1.0: 2 ports detected
Mar 12 09:43:35 Tower kernel: [   66.845253] usb 1-8: new high speed USB device using ehci_hcd and address 2
Mar 12 09:43:35 Tower kernel: [   66.895253] ACPI: PCI Interrupt 0000:00:1d.3[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
Mar 12 09:43:35 Tower kernel: [   66.895458] PCI: Setting latency timer of device 0000:00:1d.3 to 64
Mar 12 09:43:35 Tower kernel: [   66.895462] uhci_hcd 0000:00:1d.3: UHCI Host Controller
Mar 12 09:43:35 Tower kernel: [   66.895580] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Mar 12 09:43:35 Tower kernel: [   66.895734] uhci_hcd 0000:00:1d.3: irq 10, io base 0x0000ef80
Mar 12 09:43:35 Tower kernel: [   66.895936] usb usb5: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   66.896056] hub 5-0:1.0: USB hub found
Mar 12 09:43:35 Tower kernel: [   66.896145] hub 5-0:1.0: 2 ports detected
Mar 12 09:43:35 Tower kernel: [   66.998032] usb 1-8: configuration #1 chosen from 1 choice
Mar 12 09:43:35 Tower kernel: [   67.005097] Initializing USB Mass Storage driver...
Mar 12 09:43:35 Tower kernel: [   67.005262] scsi0 : SCSI emulation for USB Mass Storage devices
Mar 12 09:43:35 Tower kernel: [   67.005393] usb-storage: device found at 2
Mar 12 09:43:35 Tower kernel: [   67.005395] usb-storage: waiting for device to settle before scanning
Mar 12 09:43:35 Tower kernel: [   67.164740] usbcore: registered new interface driver usb-storage
Mar 12 09:43:35 Tower kernel: [   67.164827] USB Mass Storage support registered.
Mar 12 09:43:35 Tower kernel: [   67.164981] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
Mar 12 09:43:35 Tower kernel: [   67.167142] serio: i8042 KBD port at 0x60,0x64 irq 1
Mar 12 09:43:35 Tower kernel: [   67.167230] serio: i8042 AUX port at 0x60,0x64 irq 12
Mar 12 09:43:35 Tower kernel: [   67.167364] mice: PS/2 mouse device common for all mice
Mar 12 09:43:35 Tower kernel: [   67.167605] usbcore: registered new interface driver usbhid
Mar 12 09:43:35 Tower kernel: [   67.167692] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Mar 12 09:43:35 Tower kernel: [   67.167796] TCP cubic registered
Mar 12 09:43:35 Tower kernel: [   67.167885] NET: Registered protocol family 1
Mar 12 09:43:35 Tower kernel: [   67.167971] NET: Registered protocol family 17
Mar 12 09:43:35 Tower kernel: [   67.168059] Using IPI Shortcut mode
Mar 12 09:43:35 Tower kernel: [   67.168378] Freeing unused kernel memory: 156k freed
Mar 12 09:43:35 Tower kernel: [   67.354940] input: AT Translated Set 2 keyboard as /class/input/input2
Mar 12 09:43:35 Tower kernel: [   67.467238] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Mar 12 09:43:35 Tower kernel: [   67.467333] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Mar 12 09:43:35 Tower kernel: [   67.475738] ICH5: IDE controller at PCI slot 0000:00:1f.1
Mar 12 09:43:35 Tower kernel: [   67.475836] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
Mar 12 09:43:35 Tower kernel: [   67.475931] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
Mar 12 09:43:35 Tower kernel: [   67.476141] ICH5: chipset revision 2
Mar 12 09:43:35 Tower kernel: [   67.476225] ICH5: not 100%% native mode: will probe irqs later
Mar 12 09:43:35 Tower kernel: [   67.476319]     ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
Mar 12 09:43:35 Tower kernel: [   67.476525]     ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
Mar 12 09:43:35 Tower kernel: [   67.476729] Probing IDE interface ide0...
Mar 12 09:43:35 Tower kernel: [   67.783877] hda: WDC WD2500JB-32EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   68.083372] hdb: Maxtor 7Y250P0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   68.144123] hda: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   68.145252] hdb: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   68.145395] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 12 09:43:35 Tower kernel: [   68.145561] Probing IDE interface ide1...
Mar 12 09:43:35 Tower kernel: [   68.452770] hdc: WDC WD2500JB-32EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   68.752282] hdd: WDC WD2500JB-00EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   68.813009] hdc: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   68.814986] hdd: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   68.816012] ide1 at 0x170-0x177,0x376 on irq 15
Mar 12 09:43:35 Tower kernel: [   68.822285] ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
Mar 12 09:43:35 Tower kernel: [   68.822377] ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10
Mar 12 09:43:35 Tower kernel: [   68.822609] skge 1.11 addr 0xfeafc000 irq 10 chip Yukon-Lite rev 7
Mar 12 09:43:35 Tower kernel: [   68.822809] skge eth0: addr 00:11:2f:da:bd:e8
Mar 12 09:43:35 Tower kernel: [   68.822990] PDC20269: IDE controller at PCI slot 0000:02:09.0
Mar 12 09:43:35 Tower kernel: [   68.823332] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
Mar 12 09:43:35 Tower kernel: [   68.823419] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKF] -> GSI 5 (level, low) -> IRQ 5
Mar 12 09:43:35 Tower kernel: [   68.823624] PDC20269: chipset revision 2
Mar 12 09:43:35 Tower kernel: [   68.823711] PDC20269: ROM enabled at 0x60020000
Mar 12 09:43:35 Tower kernel: [   68.833814] PDC20269: PLL input clock is 16692 kHz
Mar 12 09:43:35 Tower kernel: [   68.863871] PDC20269: 100%% native mode on irq 5
Mar 12 09:43:35 Tower kernel: [   68.863961]     ide2: BM-DMA at 0xdf90-0xdf97, BIOS settings: hde:pio, hdf:pio
Mar 12 09:43:35 Tower kernel: [   68.864169]     ide3: BM-DMA at 0xdf98-0xdf9f, BIOS settings: hdg:pio, hdh:pio
Mar 12 09:43:35 Tower kernel: [   68.864373] Probing IDE interface ide2...
Mar 12 09:43:35 Tower kernel: [   68.873457] libata version 2.21 loaded.
Mar 12 09:43:35 Tower kernel: [   69.171768] hde: WDC WD2500JB-00EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   69.891301] hde: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   69.892347] ide2 at 0xdff0-0xdff7,0xdfe6 on irq 5
Mar 12 09:43:35 Tower kernel: [   69.892503] Probing IDE interface ide3...
Mar 12 09:43:35 Tower kernel: [   70.200091] hdg: WDC WD2500JB-00EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   70.499603] hdh: WDC WD2500JB-32EVA0, ATA DISK drive
Mar 12 09:43:35 Tower kernel: [   70.560190] hdg: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   70.562183] hdh: selected mode 0x45
Mar 12 09:43:35 Tower kernel: [   70.563184] ide3 at 0xdfa8-0xdfaf,0xdfe2 on irq 5
Mar 12 09:43:35 Tower kernel: [   70.568414] hda: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.584466] hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.586358] hda: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.586481]  hda: hda1
Mar 12 09:43:35 Tower kernel: [   70.597592] hdb: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.603816] hdb: 488281250 sectors (250000 MB) w/7936KiB Cache, CHS=30394/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.604204] hdb: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.604311]  hdb: hdb1
Mar 12 09:43:35 Tower kernel: [   70.607404] hdc: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.623282] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.625200] hdc: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.625299]  hdc: hdc1
Mar 12 09:43:35 Tower kernel: [   70.641895] hdd: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.657665] hdd: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.659578] hdd: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.659679]  hdd: hdd1
Mar 12 09:43:35 Tower kernel: [   70.669187] hde: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.686075] hde: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.687940] hde: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.688039]  hde: hde1
Mar 12 09:43:35 Tower kernel: [   70.704491] hdg: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.720357] hdg: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.722195] hdg: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.722295]  hdg: hdg1
Mar 12 09:43:35 Tower kernel: [   70.732991] hdh: max request size: 512KiB
Mar 12 09:43:35 Tower kernel: [   70.748815] hdh: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
Mar 12 09:43:35 Tower kernel: [   70.750665] hdh: cache flushes supported
Mar 12 09:43:35 Tower kernel: [   70.750763]  hdh: hdh1
Mar 12 09:43:35 Tower kernel: [   71.998036] scsi 0:0:0:0: Direct-Access     LEXAR    JUMPDRIVE SPORT  3000 PQ: 0 ANSI: 0 CCS
Mar 12 09:43:35 Tower kernel: [   71.999145] sd 0:0:0:0: [sda] 506880 512-byte hardware sectors (260 MB)
Mar 12 09:43:35 Tower kernel: [   72.000015] sd 0:0:0:0: [sda] Write Protect is off
Mar 12 09:43:35 Tower kernel: [   72.000103] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Mar 12 09:43:35 Tower kernel: [   72.000105] sd 0:0:0:0: [sda] Assuming drive cache: write through
Mar 12 09:43:35 Tower kernel: [   72.002511] sd 0:0:0:0: [sda] 506880 512-byte hardware sectors (260 MB)
Mar 12 09:43:35 Tower kernel: [   72.003384] sd 0:0:0:0: [sda] Write Protect is off
Mar 12 09:43:35 Tower kernel: [   72.003470] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Mar 12 09:43:35 Tower kernel: [   72.003472] sd 0:0:0:0: [sda] Assuming drive cache: write through
Mar 12 09:43:35 Tower kernel: [   72.003559]  sda: sda1
Mar 12 09:43:35 Tower kernel: [   72.005160] sd 0:0:0:0: [sda] Attached SCSI removable disk
Mar 12 09:43:35 Tower kernel: [   72.005613] usb-storage: device scan complete
Mar 12 09:43:35 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1
Mar 12 09:43:35 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Mar 12 09:43:35 Tower logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -d -t 60 -h Tower eth0
Mar 12 09:43:35 Tower kernel: [   82.353150] skge eth0: enabling interface
Mar 12 09:43:35 Tower dhcpcd[1134]: broadcasting DHCP_DISCOVER 
Mar 12 09:43:36 Tower kernel: [   84.037185] skge eth0: Link is up at 100 Mbps, full duplex, flow control both
Mar 12 09:43:40 Tower dhcpcd[1134]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 12 09:43:40 Tower dhcpcd[1134]: DHCP_OFFER received from  (192.168.1.1) 
Mar 12 09:43:40 Tower dhcpcd[1134]: broadcasting DHCP_REQUEST for 192.168.1.108 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 12 09:43:40 Tower dhcpcd[1134]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 12 09:43:40 Tower dhcpcd[1134]: DHCP_ACK received from  (192.168.1.1) 
Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: ifplugd 0.28 initializing.
Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: Using interface eth0/00:11:2F:DA:BD:E8 with driver <skge> (version: 1.11)

  • Author

Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: Using detection mode: SIOCETHTOOL
Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: Initialization complete, link beat detected.
Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Mar 12 09:43:40 Tower ifplugd(eth0)[1224]: Program executed successfully.
Mar 12 09:43:40 Tower kernel: [   87.847381] fuse init (API version 7.
Mar 12 09:43:40 Tower emhttp[1265]: unRAID System Management Utility version 4.2.3
Mar 12 09:43:40 Tower emhttp[1265]: Copyright (C) 2005-2008, Lime Technology, LLC
Mar 12 09:43:40 Tower emhttp[1265]: Pro key detected, registered to: xxxxx
Mar 12 09:43:40 Tower emhttp[1265]: Device inventory:
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:00:1f.1-ide-0:0 (hda) ata-WDC_WD2500JB-32EVA0_WD-WMAEH1052712
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:00:1f.1-ide-0:1 (hdb) ata-Maxtor_7Y250P0_Y61HW0LE
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:00:1f.1-ide-1:0 (hdc) ata-WDC_WD2500JB-32EVA0_WD-WMAEH1054505
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:02:09.0-ide-1:1 (hdh) ata-WDC_WD2500JB-32EVA0_WD-WMAEH1033222
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:02:09.0-ide-1:0 (hdg) ata-WDC_WD2500JB-00EVA0_WD-WMAEH1008475
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:00:1f.1-ide-1:1 (hdd) ata-WDC_WD2500JB-00EVA0_WD-WMAEH1008211
Mar 12 09:43:40 Tower emhttp[1265]: pci-0000:02:09.0-ide-0:0 (hde) ata-WDC_WD2500JB-00EVA0_WD-WMAEH1194119
Mar 12 09:43:40 Tower emhttp[1265]: shcmd (1): rmmod md-mod >>/var/log/go 2>&1
Mar 12 09:43:40 Tower emhttp[1265]: shcmd (1): exit status: 1
Mar 12 09:43:40 Tower emhttp[1265]: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=3,0,3,64,22,0,22,64,33,0,0,0,34,0,34,64,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1
Mar 12 09:43:40 Tower kernel: [   87.879529] md: unRAID driver 0.92.0 installed
Mar 12 09:43:40 Tower kernel: [   88.220413] md: xor using function: pIII_sse (4718.000 MB/sec)
Mar 12 09:43:40 Tower emhttp[1265]: shcmd (3): /usr/sbin/hdparm -S242 /dev/hda >/dev/null
Mar 12 09:43:40 Tower emhttp[1265]: shcmd (4): /usr/sbin/hdparm -S242 /dev/hdb >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (5): /usr/sbin/hdparm -S242 /dev/hdc >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (6): /usr/sbin/hdparm -S242 /dev/hdd >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (7): /usr/sbin/hdparm -S242 /dev/hde >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (: /usr/sbin/hdparm -S242 /dev/hdg >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (9): /usr/sbin/hdparm -S242 /dev/hdh >/dev/null
Mar 12 09:43:41 Tower emhttp[1265]: shcmd (10): killall -w smbd nmbd
Mar 12 09:43:42 Tower emhttp[1265]: shcmd (11): /usr/sbin/nmbd -D
Mar 12 09:43:42 Tower emhttp[1265]: shcmd (12): /usr/sbin/smbd -D
Mar 12 09:43:42 Tower emhttp[1265]: driver cmd: start STOPPED
Mar 12 09:43:42 Tower kernel: [   89.993725] mdcmd (3): start
Mar 12 09:43:42 Tower kernel: [   90.101792] unraid: allocated 17270kB
Mar 12 09:43:42 Tower kernel: [   90.101950] md1: running, size: 244140592 blocks
Mar 12 09:43:42 Tower kernel: [   90.101969] md2: running, size: 244198552 blocks
Mar 12 09:43:42 Tower kernel: [   90.101984] md3: running, size: 244198552 blocks
Mar 12 09:43:42 Tower kernel: [   90.102005] md4: running, size: 244198552 blocks
Mar 12 09:43:42 Tower kernel: [   90.102019] md6: running, size: 244198552 blocks
Mar 12 09:43:42 Tower kernel: [   90.102033] md7: running, size: 244198552 blocks
Mar 12 09:43:43 Tower emhttp[1265]: driver cmd: check
Mar 12 09:43:43 Tower kernel: [   90.577615] mdcmd (5): check
Mar 12 09:43:43 Tower kernel: [   90.577626] md: recovery thread got woken up ...
Mar 12 09:43:43 Tower kernel: [   90.577628] md: recovery thread syncing parity disk...
Mar 12 09:43:43 Tower emhttp[1265]: shcmd (13): udevsettle
Mar 12 09:43:43 Tower kernel: [   90.688530] md: using 1152k window, over a total of 244198552 blocks.
Mar 12 09:43:44 Tower kernel: [   91.471939] spurious 8259A interrupt: IRQ7.
Mar 12 09:43:44 Tower emhttp[1337]: shcmd (14): mkdir -m 700 /mnt/disk1
Mar 12 09:43:44 Tower emhttp[1337]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1
Mar 12 09:43:44 Tower emhttp[1341]: shcmd (14): mkdir -m 700 /mnt/disk2
Mar 12 09:43:44 Tower emhttp[1341]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1
Mar 12 09:43:44 Tower emhttp[1345]: shcmd (14): mkdir -m 700 /mnt/disk3
Mar 12 09:43:44 Tower emhttp[1347]: shcmd (14): mkdir -m 700 /mnt/disk4
Mar 12 09:43:44 Tower emhttp[1349]: shcmd (14): mkdir -m 700 /mnt/disk6
Mar 12 09:43:44 Tower emhttp[1349]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md6 /mnt/disk6  >/dev/null 2>&1
Mar 12 09:43:44 Tower emhttp[1353]: shcmd (14): mkdir -m 700 /mnt/disk7
Mar 12 09:43:44 Tower emhttp[1353]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md7 /mnt/disk7  >/dev/null 2>&1
Mar 12 09:43:44 Tower emhttp[1345]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1
Mar 12 09:43:44 Tower emhttp[1347]: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1
Mar 12 09:43:44 Tower kernel: [   91.525230] ReiserFS: md4: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.525245] ReiserFS: md4: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.540242] ReiserFS: md4: journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.541025] ReiserFS: md4: checking transaction log (md4)
Mar 12 09:43:44 Tower kernel: [   91.587285] ReiserFS: md2: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.587304] ReiserFS: md2: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.587616] ReiserFS: md7: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.587629] ReiserFS: md7: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.587854] ReiserFS: md6: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.587866] ReiserFS: md6: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.612719] ReiserFS: md1: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.612738] ReiserFS: md1: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.612975] ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.613796] ReiserFS: md2: checking transaction log (md2)
Mar 12 09:43:44 Tower kernel: [   91.613977] ReiserFS: md3: found reiserfs format "3.6" with standard journal
Mar 12 09:43:44 Tower kernel: [   91.613994] ReiserFS: md3: using ordered data mode
Mar 12 09:43:44 Tower kernel: [   91.614248] ReiserFS: md6: journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.615242] ReiserFS: md6: checking transaction log (md6)
Mar 12 09:43:44 Tower kernel: [   91.615412] ReiserFS: md7: journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.616350] ReiserFS: md7: checking transaction log (md7)
Mar 12 09:43:44 Tower kernel: [   91.678581] ReiserFS: md1: journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.679358] ReiserFS: md1: checking transaction log (md1)
Mar 12 09:43:44 Tower kernel: [   91.679515] ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 12 09:43:44 Tower kernel: [   91.680611] ReiserFS: md3: checking transaction log (md3)
Mar 12 09:43:44 Tower kernel: [   91.696142] ReiserFS: md4: replayed 2 transactions in 0 seconds
Mar 12 09:43:44 Tower kernel: [   91.724296] ReiserFS: md4: Using r5 hash to sort names
Mar 12 09:43:44 Tower kernel: [   92.010756] ReiserFS: md6: replayed 2 transactions in 0 seconds
Mar 12 09:43:44 Tower kernel: [   92.010864] ReiserFS: md7: replayed 2 transactions in 0 seconds
Mar 12 09:43:44 Tower kernel: [   92.101433] can't shrink filesystem on-line
Mar 12 09:43:44 Tower kernel: [   92.131248] ReiserFS: md7: Using r5 hash to sort names
Mar 12 09:43:44 Tower kernel: [   92.131521] ReiserFS: md6: Using r5 hash to sort names
Mar 12 09:43:44 Tower kernel: [   92.177710] ReiserFS: md2: replayed 2 transactions in 0 seconds
Mar 12 09:43:44 Tower kernel: [   92.215144] ReiserFS: md1: replayed 2 transactions in 0 seconds
Mar 12 09:43:45 Tower kernel: [   92.240571] ReiserFS: md3: replayed 2 transactions in 0 seconds
Mar 12 09:43:45 Tower kernel: [   92.385537] ReiserFS: md3: Using r5 hash to sort names
Mar 12 09:43:45 Tower kernel: [   92.512709] ReiserFS: md1: Using r5 hash to sort names
Mar 12 09:43:45 Tower kernel: [   92.613609] can't shrink filesystem on-line
Mar 12 09:43:45 Tower kernel: [   92.613870] can't shrink filesystem on-line
Mar 12 09:43:45 Tower kernel: [   92.700884] ReiserFS: md2: Using r5 hash to sort names
Mar 12 09:43:45 Tower kernel: [   93.165895] ------------[ cut here ]------------
Mar 12 09:43:45 Tower kernel: [   93.166012] kernel BUG at fs/reiserfs/bitmap.c:1287!
Mar 12 09:43:45 Tower kernel: [   93.166119] invalid opcode: 0000 [#1]
Mar 12 09:43:45 Tower kernel: [   93.166224] Modules linked in: md_mod fuse ide_disk ata_piix libata pdc202xx_new skge piix ide_core
Mar 12 09:43:45 Tower kernel: [   93.166931] CPU:    0
Mar 12 09:43:45 Tower kernel: [   93.166932] EIP:    0060:[<c01774a7>]    Not tainted VLI
Mar 12 09:43:45 Tower kernel: [   93.166933] EFLAGS: 00210246   (2.6.22.5 #9)
Mar 12 09:43:45 Tower kernel: [   93.167260] EIP is at reiserfs_cache_bitmap_metadata+0x74/0x7c
Mar 12 09:43:45 Tower kernel: [   93.167370] eax: de41b000   ebx: f8a4fd1c   ecx: 00000000   edx: de41affc
Mar 12 09:43:45 Tower kernel: [   93.167481] esi: dfdac198   edi: 00000000   ebp: f8a4fd1c   esp: de4c9da4
Mar 12 09:43:45 Tower kernel: [   93.167593] ds: 007b   es: 007b   fs: 0000  gs: 0033  ss: 0068
Mar 12 09:43:45 Tower kernel: [   93.167704] Process emhttp (pid: 1345, ti=de4c8000 task=de3ae030 task.ti=de4c8000)
Mar 12 09:43:45 Tower kernel: [   93.167817] Stack: dfdac198 03a38000 f3bdea00 c017755f 00001000 c01945d6 00000000 00000000 
Mar 12 09:43:45 Tower kernel: [   93.168462]        03a38b20 f8a4fd1c de4c9e48 00000000 c0195e6c 00001000 00010000 00000000 
Mar 12 09:43:45 Tower kernel: [   93.168886]        c03028fe 00000000 dfc1fd40 00800000 03a38b20 00000b20 00000b26 00000748 
Mar 12 09:43:45 Tower kernel: [   93.169330] Call Trace:
Mar 12 09:43:45 Tower kernel: [   93.169498]  [<c017755f>] reiserfs_read_bitmap_block+0xb0/0xba
Mar 12 09:43:45 Tower kernel: [   93.169622]  [<c01945d6>] journal_begin+0x93/0xce
Mar 12 09:43:45 Tower kernel: [   93.169746]  [<c0195e6c>] reiserfs_resize+0x390/0x588
Mar 12 09:43:45 Tower kernel: [   93.169871]  [<c012f180>] wait_on_page_writeback_range+0xbc/0xfa
Mar 12 09:43:45 Tower kernel: [   93.169997]  [<c018749a>] reiserfs_remount+0xcf/0x267
Mar 12 09:43:45 Tower kernel: [   93.170122]  [<c0148612>] do_remount_sb+0x7b/0xa4
Mar 12 09:43:45 Tower kernel: [   93.170246]  [<c0157e91>] do_remount+0x62/0x84
Mar 12 09:43:45 Tower kernel: [   93.170369]  [<c015860a>] do_mount+0x120/0x199
Mar 12 09:43:45 Tower kernel: [   93.170492]  [<c0132e94>] __alloc_pages+0x49/0x295
Mar 12 09:43:45 Tower kernel: [   93.170617]  [<c01584a2>] copy_mount_options+0x4a/0x92
Mar 12 09:43:45 Tower kernel: [   93.170740]  [<c01588ab>] sys_mount+0x74/0xab
Mar 12 09:43:45 Tower kernel: [   93.170863]  [<c0103a62>] syscall_call+0x7/0xb
Mar 12 09:43:45 Tower kernel: [   93.170986]  [<c02b0000>] skb_icv_walk+0x1e2/0x206
Mar 12 09:43:45 Tower kernel: [   93.171111]  =======================
Mar 12 09:43:45 Tower kernel: [   93.171197] Code: 40 74 d2 b9 1f 00 00 00 0f a3 0a 19 c0 85 c0 75 0f 8d 04 0f 66 89 03 0f b7 43 02 40 66 89 43 02 49 79 e5 eb b0 66 83 3b 00 75 04 <0f> 0b eb fe 5b 5e 5f c3 55 89 d1 57 89 c7 56 53 83 ec 10 8b 58 
Mar 12 09:43:45 Tower kernel: [   93.173535] EIP: [<c01774a7>] reiserfs_cache_bitmap_metadata+0x74/0x7c SS:ESP 0068:de4c9da4
Mar 12 09:43:45 Tower kernel: [   93.173888] WARNING: at kernel/exit.c:869 do_exit()
Mar 12 09:43:45 Tower kernel: [   93.173995]  [<c011592c>] do_exit+0x41/0x300
Mar 12 09:43:45 Tower kernel: [   93.174159]  [<c010434b>] die+0x188/0x190
Mar 12 09:43:45 Tower kernel: [   93.174323]  [<c01045c5>] do_invalid_op+0x0/0x8a
Mar 12 09:43:45 Tower kernel: [   93.174492]  [<c0104646>] do_invalid_op+0x81/0x8a
Mar 12 09:43:45 Tower kernel: [   93.174659]  [<c01774a7>] reiserfs_cache_bitmap_metadata+0x74/0x7c
Mar 12 09:43:45 Tower kernel: [   93.174822]  [<c02b4c16>] io_schedule+0xe/0x16
Mar 12 09:43:45 Tower kernel: [   93.174946]  [<c02b4d3a>] __wait_on_bit+0x4a/0x51
Mar 12 09:43:45 Tower kernel: [   93.175069]  [<c02b4daf>] out_of_line_wait_on_bit+0x6e/0x76
Mar 12 09:43:45 Tower kernel: [   93.175194]  [<c015f04b>] sync_buffer+0x0/0x2e
Mar 12 09:43:45 Tower kernel: [   93.175317]  [<c01215e5>] wake_bit_function+0x0/0x3c
Mar 12 09:43:45 Tower kernel: [   93.175444]  [<c02b5532>] error_code+0x6a/0x70
Mar 12 09:43:45 Tower kernel: [   93.175567]  [<c01774a7>] reiserfs_cache_bitmap_metadata+0x74/0x7c
Mar 12 09:43:45 Tower kernel: [   93.175694]  [<c017755f>] reiserfs_read_bitmap_block+0xb0/0xba
Mar 12 09:43:45 Tower kernel: [   93.175818]  [<c01945d6>] journal_begin+0x93/0xce
Mar 12 09:43:45 Tower kernel: [   93.175942]  [<c0195e6c>] reiserfs_resize+0x390/0x588
Mar 12 09:43:45 Tower kernel: [   93.176069]  [<c012f180>] wait_on_page_writeback_range+0xbc/0xfa
Mar 12 09:43:45 Tower kernel: [   93.176194]  [<c018749a>] reiserfs_remount+0xcf/0x267
Mar 12 09:43:45 Tower kernel: [   93.176319]  [<c0148612>] do_remount_sb+0x7b/0xa4
Mar 12 09:43:45 Tower kernel: [   93.176443]  [<c0157e91>] do_remount+0x62/0x84
Mar 12 09:43:45 Tower kernel: [   93.176566]  [<c015860a>] do_mount+0x120/0x199
Mar 12 09:43:45 Tower kernel: [   93.176690]  [<c0132e94>] __alloc_pages+0x49/0x295
Mar 12 09:43:45 Tower kernel: [   93.176814]  [<c01584a2>] copy_mount_options+0x4a/0x92
Mar 12 09:43:45 Tower kernel: [   93.176939]  [<c01588ab>] sys_mount+0x74/0xab
Mar 12 09:43:45 Tower kernel: [   93.177061]  [<c0103a62>] syscall_call+0x7/0xb
Mar 12 09:43:45 Tower kernel: [   93.177184]  [<c02b0000>] skb_icv_walk+0x1e2/0x206
Mar 12 09:43:45 Tower kernel: [   93.177309]  =======================
Mar 12 09:43:45 Tower kernel: [   93.212716] can't shrink filesystem on-line
Mar 12 09:43:46 Tower kernel: [   93.435397] can't shrink filesystem on-line
Mar 12 09:43:46 Tower emhttp[1265]: shcmd (14): mkdir -m 700 /mnt/user
Mar 12 09:43:46 Tower emhttp[1265]: shcmd (15): shfs /mnt/user
Mar 12 09:43:47 Tower emhttp[1265]: shcmd (16): killall -HUP smbd
Mar 12 14:42:25 Tower kernel: [17984.507068] md: sync done. time=17922sec rate=13625K/sec
Mar 12 14:42:25 Tower kernel: [17984.573666] md: recovery thread sync completion status: 0
Mar 12 21:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 12 21:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 12 21:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 12 21:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 12 21:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 13 09:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 13 09:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 13 09:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 13 09:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 13 09:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 13 21:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 13 21:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 13 21:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 13 21:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 13 21:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 14 09:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 14 09:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 14 09:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 14 09:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 14 09:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 14 21:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 14 21:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 14 21:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 14 21:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 14 21:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 15 09:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 15 09:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 15 09:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 15 09:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 15 09:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 15 20:05:29 Tower emhttp[1265]: driver cmd: clear
Mar 15 20:05:29 Tower kernel: [296132.055531] mdcmd (44): clear
Mar 15 21:43:40 Tower dhcpcd[1136]: sending DHCP_REQUEST for 192.168.1.108 to 192.168.1.1 
Mar 15 21:43:40 Tower dhcpcd[1136]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 15 21:43:40 Tower dhcpcd[1136]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 15 21:43:40 Tower dhcpcd[1136]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 15 21:43:40 Tower dhcpcd[1136]: DHCP_ACK received from  (192.168.1.1) 
Mar 15 22:11:35 Tower emhttp[1265]: shcmd (17): mkdir -m 700 /mnt/user/Media1
Mar 15 22:40:54 Tower login[1266]: ROOT LOGIN  on `tty1'

 

Unfortunately, the log does not show any problems with the share of Media1.  Tom or another Linux expert will have to help you with that.

 

Your log does show problems with the Reiser file system.  I suggest you run reiserfsck on all of your data drives (not the parity drive), see this thread:  http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems.

 

  • Author

ok, i ran the reiserfsck on all drives except the parity and one other and it did not return any errors.

 

for some reason i am unable to unmount disk 3. it says device is busy. i have a feeling this may be related to my problem since i have data on disks1 and 2 and they have filled up enough to start spreading to 3. later tonight i will try to disconnect that disk and see if my problems go away, but in the mean time does anyone have any suggestions i can try before removing hardware?

 

thanks.

 

 

  • 2 weeks later...
  • Author

after removing the disk that i was unable to umount, everything is working fine now. There must be something wrong with that disk, i'm not sure.  It worked fine as NTFS in windows. Either way, so far so good.

ok, i ran the reiserfsck on all drives except the parity and one other and it did not return any errors.

 

for some reason i am unable to unmount disk 3. it says device is busy. i have a feeling this may be related to my problem since i have data on disks1 and 2 and they have filled up enough to start spreading to 3. later tonight i will try to disconnect that disk and see if my problems go away, but in the mean time does anyone have any suggestions i can try before removing hardware?

 

thanks.

 

 

Is it possible you had changed directory to /mnt/disk3 when you were unable to unmount it?

A disk is busy when any file on it is open for reading or writing, or when a folder on it is the current directory of somebody (or some process) on the system. 

 

Joe L.

  • Author

my pwd was / and nothing was accessing that disk. nothing was ever written to that disk either, so i'm not sure what the problem was.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.