December 19, 200718 yr I had to reinstall my pc os and now I can't connect to my raid server. I rebooted the server and now it stops on the following Kernel Panic - not synching. No init found. Try passing init=option to kernel. It just stops there. Now what?
December 19, 200718 yr Author Ok I rebooted and got to the login. I can access the server via Internet Explorer but I cannot seem to find the server when browsing the network. What do I need to do to see the server?? As far as I remember when I last reinstalled my pc OS it just automatically saw the server, I didn't have to do anything special. Here's my log ntrol 300) Dec 18 20:58:04 Tower kernel: [ 106.438947] scsi4 : sata_promise Dec 18 20:58:04 Tower kernel: [ 106.768264] ata4: SATA link down (SStatus 0 SCo ntrol 300) Dec 18 20:58:04 Tower kernel: [ 106.768401] scsi5 : sata_promise Dec 18 20:58:04 Tower kernel: [ 107.097716] ata5: SATA link down (SStatus 0 SCo ntrol 300) Dec 18 20:58:04 Tower kernel: [ 107.097848] scsi6 : sata_promise Dec 18 20:58:04 Tower kernel: [ 107.586925] ata6: SATA link up 1.5 Gbps (SStatu s 113 SControl 300) Dec 18 20:58:04 Tower kernel: [ 107.607192] ata6.00: ATA-7, max UDMA/133, 97677 3168 sectors: LBA48 NCQ (depth 0/32) Dec 18 20:58:04 Tower kernel: [ 107.627155] ata6.00: configured for UDMA/133 Dec 18 20:58:04 Tower kernel: [ 107.627365] scsi 6:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 Dec 18 20:58:04 Tower kernel: [ 107.628465] SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB) Dec 18 20:58:04 Tower kernel: [ 107.628592] sde: Write Protect is off Dec 18 20:58:04 Tower kernel: [ 107.628701] sde: Mode Sense: 00 3a 00 00 Dec 18 20:58:04 Tower kernel: [ 107.628718] SCSI device sde: write cache: enabl ed, read cache: enabled, doesn't support DPO or FUA Dec 18 20:58:04 Tower kernel: [ 107.628952] SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB) Dec 18 20:58:04 Tower kernel: [ 107.629073] sde: Write Protect is off Dec 18 20:58:04 Tower kernel: [ 107.629181] sde: Mode Sense: 00 3a 00 00 Dec 18 20:58:04 Tower kernel: [ 107.629197] SCSI device sde: write cache: enabl ed, read cache: enabled, doesn't support DPO or FUA Dec 18 20:58:04 Tower kernel: [ 107.629382] sde: sde1 Dec 18 20:58:04 Tower kernel: [ 107.637919] sd 6:0:0:0: Attached scsi disk sde Dec 18 20:58:04 Tower kernel: [ 108.590080] scsi 0:0:0:0: Direct-Access San Disk Cruzer Mini 0.4 PQ: 0 ANSI: 2 Dec 18 20:58:04 Tower kernel: [ 108.595056] SCSI device sdf: 1000944 512-byte h dwr sectors (512 MB) Dec 18 20:58:04 Tower kernel: [ 108.598048] sdf: Write Protect is off Dec 18 20:58:04 Tower kernel: [ 108.598163] sdf: Mode Sense: 03 00 00 00 Dec 18 20:58:04 Tower kernel: [ 108.598166] sdf: assuming drive cache: write th rough Dec 18 20:58:04 Tower kernel: [ 108.610028] SCSI device sdf: 1000944 512-byte h dwr sectors (512 MB) Dec 18 20:58:04 Tower kernel: [ 108.613022] sdf: Write Protect is off Dec 18 20:58:04 Tower kernel: [ 108.613137] sdf: Mode Sense: 03 00 00 00 Dec 18 20:58:04 Tower kernel: [ 108.613139] sdf: assuming drive cache: write th rough Dec 18 20:58:04 Tower kernel: [ 108.613254] sdf: sdf1 Dec 18 20:58:04 Tower kernel: [ 108.619219] sd 0:0:0:0: Attached scsi removable disk sdf Dec 18 20:58:04 Tower kernel: [ 108.630180] usb-storage: device scan complete Dec 18 20:58:04 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Dec 18 20:58:04 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0. 0 netmask 255.0.0.0 lo Dec 18 20:58:04 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 60 -h Towe r eth0 Dec 18 20:58:04 Tower dhcpcd[880]: broadcasting DHCP_DISCOVER Dec 18 20:58:05 Tower dhcpcd[880]: broadcastAddr option is missing in DHCP serve r response. Assuming 192.168.15.255 Dec 18 20:58:05 Tower dhcpcd[880]: dhcpIPaddrLeaseTime=86400 in DHCP server resp onse. Dec 18 20:58:05 Tower dhcpcd[880]: dhcpT1value is missing in DHCP server respons e. Assuming 43200 sec Dec 18 20:58:05 Tower dhcpcd[880]: dhcpT2value is missing in DHCP server respons e. Assuming 75600 sec Dec 18 20:58:05 Tower dhcpcd[880]: DHCP_OFFER received from (192.168.15.1) Dec 18 20:58:05 Tower dhcpcd[880]: broadcasting DHCP_REQUEST for 192.168.15.101 Dec 18 20:58:05 Tower dhcpcd[880]: dhcpIPaddrLeaseTime=86400 in DHCP server resp onse. Dec 18 20:58:05 Tower dhcpcd[880]: dhcpT1value is missing in DHCP server respons e. Assuming 43200 sec Dec 18 20:58:05 Tower dhcpcd[880]: dhcpT2value is missing in DHCP server respons e. Assuming 75600 sec Dec 18 20:58:05 Tower dhcpcd[880]: DHCP_ACK received from (192.168.15.1) Dec 18 20:58:05 Tower ifplugd(eth0)[970]: ifplugd 0.28 initializing. Dec 18 20:58:05 Tower ifplugd(eth0)[970]: Using interface eth0/00:15:F2:08:16:4F with driver <r1000> (version: 1.05) Dec 18 20:58:05 Tower ifplugd(eth0)[970]: Using detection mode: SIOCETHTOOL Dec 18 20:58:05 Tower ifplugd(eth0)[970]: Initialization complete, link beat det ected. Dec 18 20:58:05 Tower ifplugd(eth0)[970]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Dec 18 20:58:05 Tower ifplugd(eth0)[970]: Program executed successfully. Dec 18 20:58:05 Tower emhttp[1002]: unRAID System Management Utility version 4.0 Dec 18 20:58:05 Tower emhttp[1002]: Copyright © 2005-2007, Lime Technology, LL C Dec 18 20:58:05 Tower emhttp[1002]: Device inventory: Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:01:02.0-scsi-3:0:0:0 (sde) scsi-SAT A_ST3500630AS_6QG07FCL Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.2-scsi-0:0:1:0 (sdb) scsi-SAT A_ST3320620AS_3QF0M37V Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.2-scsi-0:0:0:0 (sda) scsi-SAT A_ST3320620AS_3QF0M8SG Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.2-scsi-1:0:1:0 (sdd) scsi-SAT A_Maxtor_7H500F0_H81AX7RH Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.2-scsi-1:0:0:0 (sdc) scsi-SAT A_ST3300622AS_5NF1L2F8 Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.1-ide-0:0 (hda) ata-ST3500630 A_3QG04V5R Dec 18 20:58:05 Tower emhttp[1002]: pci-0000:00:1f.1-ide-0:1 (hdb) ata-ST3802110 A_5LS0SRSZ Dec 18 20:58:05 Tower emhttp[1002]: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 Dec 18 20:58:05 Tower emhttp[1002]: shcmd (2): modprobe md-mod super=/boot/confi g/super.dat slots=8,48,8,16,8,32,3,0,3,64,8,0,8,64,0,0,0,0,0,0,0,0,0,0,0,0,0,0 > >/var/log/go 2>&1 Dec 18 20:58:06 Tower kernel: [ 121.162767] md: unRAID driver 0.92.0 installed Dec 18 20:58:06 Tower kernel: [ 121.503749] md: xor using function: pIII_sse (4 314.400 MB/sec) Dec 18 20:58:06 Tower kernel: [ 121.505388] md: reading superblock from /boot/c onfig/super.dat Dec 18 20:58:06 Tower kernel: [ 121.512391] md: superblock events: 95 Dec 18 20:58:06 Tower kernel: [ 121.512793] md0: import [8,48] (sdd) Maxtor 7H5 00F0 H81AX7RH offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.512918] md1: import [8,16] (sdb) ST3320620A S 3QF0M37V offset: 63 size: 312571192 Dec 18 20:58:06 Tower kernel: [ 121.513010] md2: import [8,32] (sdc) ST3300622A S 5NF1L2F8 offset: 63 size: 293036152 Dec 18 20:58:06 Tower kernel: [ 121.513026] md3: import [3,0] (hda) ST3500630A 3QG04V5R offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.513181] md4: import [3,64] (hdb) ST3802110A 5LS0SRSZ offset: 63 size: 78150712 Dec 18 20:58:06 Tower kernel: [ 121.513329] md5: import [8,0] (sda) ST3320620AS 3QF0M8SG offset: 63 size: 312571192 Dec 18 20:58:06 Tower kernel: [ 121.513432] md6: import [8,64] (sde) ST3500630A S 6QG07FCL offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.513439] md7: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513441] md8: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513443] md9: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513444] md10: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513446] md11: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513448] md12: import: no device Dec 18 20:58:06 Tower kernel: [ 121.513449] md13: import: no device Dec 18 20:58:06 Tower kernel: [ 121.519517] md0: import [8,48] (sdd) Maxtor 7H5 00F0 H81AX7RH offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.519643] md1: import [8,16] (sdb) ST3320620A S 3QF0M37V offset: 63 size: 312571192 Dec 18 20:58:06 Tower kernel: [ 121.519737] md2: import [8,32] (sdc) ST3300622A S 5NF1L2F8 offset: 63 size: 293036152 Dec 18 20:58:06 Tower kernel: [ 121.519753] md3: import [3,0] (hda) ST3500630A 3QG04V5R offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.519905] md4: import [3,64] (hdb) ST3802110A 5LS0SRSZ offset: 63 size: 78150712 Dec 18 20:58:06 Tower kernel: [ 121.520050] md5: import [8,0] (sda) ST3320620AS 3QF0M8SG offset: 63 size: 312571192 Dec 18 20:58:06 Tower kernel: [ 121.520141] md6: import [8,64] (sde) ST3500630A S 6QG07FCL offset: 63 size: 488386552 Dec 18 20:58:06 Tower kernel: [ 121.520148] md7: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520150] md8: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520152] md9: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520154] md10: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520155] md11: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520157] md12: import: no device Dec 18 20:58:06 Tower kernel: [ 121.520159] md13: import: no device Dec 18 20:58:06 Tower emhttp[1002]: shcmd (3): killall -w smbd nmbd Dec 18 20:58:07 Tower emhttp[1002]: Scanning user shares... Dec 18 20:58:07 Tower emhttp[1002]: shcmd (4): rm -r /mnt/user/* 2>/dev/null Dec 18 20:58:07 Tower emhttp[1002]: shcmd (5): /usr/sbin/nmbd -D Dec 18 20:58:07 Tower emhttp[1002]: shcmd (6): /usr/sbin/smbd -D Dec 18 20:58:07 Tower emhttp[1002]: driver cmd: start STOPPED Dec 18 20:58:07 Tower kernel: [ 122.782077] mdcmd (3): start Dec 18 20:58:07 Tower kernel: [ 122.782210] md0: import [8,48] (sdd) Maxtor 7H5 00F0 H81AX7RH offset: 63 size: 488386552 Dec 18 20:58:07 Tower kernel: [ 122.782305] md1: import [8,16] (sdb) ST3320620A S 3QF0M37V offset: 63 size: 312571192 Dec 18 20:58:07 Tower kernel: [ 122.782394] md2: import [8,32] (sdc) ST3300622A S 5NF1L2F8 offset: 63 size: 293036152 Dec 18 20:58:07 Tower kernel: [ 122.782409] md3: import [3,0] (hda) ST3500630A 3QG04V5R offset: 63 size: 488386552 Dec 18 20:58:07 Tower kernel: [ 122.782551] md4: import [3,64] (hdb) ST3802110A 5LS0SRSZ offset: 63 size: 78150712 Dec 18 20:58:07 Tower kernel: [ 122.789829] md5: import [8,0] (sda) ST3320620AS 3QF0M8SG offset: 63 size: 312571192 Dec 18 20:58:07 Tower kernel: [ 122.789958] md6: import [8,64] (sde) ST3500630A S 6QG07FCL offset: 63 size: 488386552 Dec 18 20:58:07 Tower kernel: [ 122.789965] md7: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789967] md8: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789969] md9: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789971] md10: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789972] md11: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789974] md12: import: no device Dec 18 20:58:07 Tower kernel: [ 122.789976] md13: import: no device Dec 18 20:58:07 Tower kernel: [ 122.791181] unraid: allocated 15114kB Dec 18 20:58:07 Tower kernel: [ 122.791477] md1: running, size: 312571192 block s Dec 18 20:58:07 Tower kernel: [ 122.791495] md2: running, size: 293036152 block s Dec 18 20:58:07 Tower kernel: [ 122.791510] md3: running, size: 488386552 block s Dec 18 20:58:07 Tower kernel: [ 122.791529] md4: running, size: 78150712 blocks Dec 18 20:58:07 Tower kernel: [ 122.791544] md5: running, size: 312571192 block s Dec 18 20:58:07 Tower kernel: [ 122.791558] md6: running, size: 488386552 block s Dec 18 20:58:07 Tower emhttp[1002]: driver cmd: check Dec 18 20:58:07 Tower kernel: [ 122.959400] mdcmd (5): check Dec 18 20:58:07 Tower kernel: [ 122.959410] md: recovery thread got woken up .. . Dec 18 20:58:07 Tower kernel: [ 122.959417] md: writing superblock to /boot/con fig/super.dat Dec 18 20:58:07 Tower emhttp[1002]: shcmd (7): udevsettle Dec 18 20:58:07 Tower kernel: [ 122.973927] md: recovery thread has nothing to resync Dec 18 20:58:07 Tower emhttp[1063]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Dec 18 20:58:07 Tower kernel: [ 123.144625] ReiserFS: md1: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.144641] ReiserFS: md1: using ordered data m ode Dec 18 20:58:07 Tower emhttp[1066]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 Dec 18 20:58:07 Tower emhttp[1069]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md3 /mnt/disk3 >/dev/null 2>&1 Dec 18 20:58:07 Tower kernel: [ 123.148943] ReiserFS: md2: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.148960] ReiserFS: md2: using ordered data m ode Dec 18 20:58:07 Tower emhttp[1071]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md4 /mnt/disk4 >/dev/null 2>&1 Dec 18 20:58:07 Tower emhttp[1073]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 Dec 18 20:58:07 Tower kernel: [ 123.154919] ReiserFS: md5: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.154937] ReiserFS: md5: using ordered data m ode Dec 18 20:58:07 Tower emhttp[1076]: shcmd (: mount -t reiserfs -o noatime,nodi ratime /dev/md6 /mnt/disk6 >/dev/null 2>&1 Dec 18 20:58:07 Tower kernel: [ 123.158745] ReiserFS: md6: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.158765] ReiserFS: md6: using ordered data m ode Dec 18 20:58:07 Tower kernel: [ 123.160616] ReiserFS: md3: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.160636] ReiserFS: md3: using ordered data m ode Dec 18 20:58:07 Tower kernel: [ 123.161131] ReiserFS: md1: journal params: devi ce md1, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.161872] ReiserFS: md1: checking transaction log (md1) Dec 18 20:58:07 Tower kernel: [ 123.165389] ReiserFS: md4: found reiserfs forma t "3.6" with standard journal Dec 18 20:58:07 Tower kernel: [ 123.165400] ReiserFS: md4: using ordered data m ode Dec 18 20:58:07 Tower kernel: [ 123.165697] ReiserFS: md6: journal params: devi ce md6, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.166440] ReiserFS: md6: checking transaction log (md6) Dec 18 20:58:07 Tower kernel: [ 123.166605] ReiserFS: md5: journal params: devi ce md5, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.167367] ReiserFS: md5: checking transaction log (md5) Dec 18 20:58:07 Tower kernel: [ 123.167526] ReiserFS: md3: journal params: devi ce md3, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.168294] ReiserFS: md3: checking transaction log (md3) Dec 18 20:58:07 Tower kernel: [ 123.168454] ReiserFS: md2: journal params: devi ce md2, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.169230] ReiserFS: md2: checking transaction log (md2) Dec 18 20:58:07 Tower kernel: [ 123.186030] ReiserFS: md4: journal params: devi ce md4, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Dec 18 20:58:07 Tower kernel: [ 123.186778] ReiserFS: md4: checking transaction log (md4) Dec 18 20:58:07 Tower kernel: [ 123.280992] ReiserFS: md2: Using r5 hash to sor t names Dec 18 20:58:07 Tower kernel: [ 123.303830] ReiserFS: md6: Using r5 hash to sor t names Dec 18 20:58:07 Tower kernel: [ 123.303926] ReiserFS: md4: Using r5 hash to sor t names Dec 18 20:58:07 Tower kernel: [ 123.337378] ReiserFS: md3: Using r5 hash to sor t names Dec 18 20:58:07 Tower emhttp[1076]: remount: /dev/md6 Dec 18 20:58:07 Tower kernel: [ 123.352688] ReiserFS: md5: Using r5 hash to sor t names Dec 18 20:58:07 Tower emhttp[1071]: remount: /dev/md4 Dec 18 20:58:07 Tower kernel: [ 123.360892] ReiserFS: md1: Using r5 hash to sor t names Dec 18 20:58:07 Tower emhttp[1066]: remount: /dev/md2 Dec 18 20:58:07 Tower emhttp[1069]: remount: /dev/md3 Dec 18 20:58:08 Tower emhttp[1073]: remount: /dev/md5 Dec 18 20:58:08 Tower emhttp[1063]: remount: /dev/md1 Dec 18 20:58:08 Tower kernel: [ 123.648966] can't shrink filesystem on-line Dec 18 20:58:08 Tower kernel: [ 123.649206] can't shrink filesystem on-line Dec 18 20:58:08 Tower kernel: [ 123.649410] can't shrink filesystem on-line Dec 18 20:58:08 Tower kernel: [ 123.659990] can't shrink filesystem on-line Dec 18 20:58:08 Tower kernel: [ 123.681960] can't shrink filesystem on-line Dec 18 20:58:08 Tower kernel: [ 123.682178] can't shrink filesystem on-line Dec 18 20:58:08 Tower emhttp[1002]: shcmd (: killall -w smbd nmbd Dec 18 20:58:09 Tower emhttp[1002]: Scanning user shares... Dec 18 20:58:09 Tower emhttp[1002]: shcmd (9): rm -r /mnt/user/* 2>/dev/null Dec 18 20:58:09 Tower emhttp[1002]: user share: Music Dec 18 20:58:09 Tower emhttp[1002]: user share: Pictures Dec 18 20:58:09 Tower emhttp[1002]: user share: Movies Dec 18 20:58:09 Tower emhttp[1002]: shcmd (10): /usr/sbin/nmbd -D Dec 18 20:58:09 Tower emhttp[1002]: shcmd (11): /usr/sbin/smbd -D Dec 18 21:08:12 Tower in.telnetd[1111]: connect from 192.168.15.100 (192.168.15. 100) Dec 18 21:08:14 Tower login[1112]: ROOT LOGIN on `pts/0' from `192.168.15.100' root@Tower:~#
December 19, 200718 yr Author Nevermind figured it ou! I had changed the name of my workgroup. Once I changed that in the server...POW! Back in business. I'd say thanks to everyone who helped but well...you know...
Archived
This topic is now archived and is closed to further replies.